[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: IMG_5896.jpg (75 KB, 1000x1322)
75 KB JPG
I’m halfway through chapter one of this book and I’m doing the exercises.
My programs work as far as I can tell but they don’t look like the ones in the answer book.
What can I do to intuit the right way to write these programs?
>>
learn by doing and by seeing what works and what doesn't
>>
Find the solution manual and look at the difference between your implementation and theirs
>but I can’t find the solution manual
Then ask jeetGPT or Claude to be your TA and look over your solution to a given problem
>>
>>109886866
I have the book
>>
>>109886854
>What can I do to intuit the right way to write these programs?
only experience will teach you that

good code needs to be legible, modular, efficient
the rest is personal preferences
>>
>>109886854
>they don’t look like the ones in the answer book.
just assuming from the way youre analysing your results its probably best if you choose a different language as your first where you can easily focus on turning your ideas to code and see your changes happen quickly. c was designed alongside an operating system so some of features the book might demonstrate to you may not make sense to you or might be too verbose for the kind of software youre looking to create, you could try something like python or lua maybe?



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.