2/ Make state changes transnational and in one place as opposed to one off changes spread out all over the place. Remove as many conditionals as possible, and generally depending on checking null by client code is an antipattern for the same general reasons.
-
-
Show this thread
-
3/ The goal first and foremost is to make this stuff fit in your head! If it doesn't, you're just going to be reduced to a combination of frustration and endless trial/error resulting in lots of bugs.
Show this thread
End of conversation
New conversation -
-
-
Is there any book etc on thinking abstractly about code?
-
I think of all the books I've read, Refactoring by Martin Fowler might be the best one to pair up with what I just talked about here. Pragmatic Programmer and Code Complete are my other favorites.
- Show replies
New conversation -
-
-
This sounds a lot like what Functional Programming languages do for you (or force you to do it). Do you have any opinions on FP?
-
I've only dabbled in them so I can't give you a worthwhile opinion on them. But yeah I know at least that they're building these basic concepts that they're building into the language. I can say I think languages like C# (that incorporate some elements) are the most practical.
End of conversation
New conversation -
-
-
This saved my life once lmao
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.