The most obvious way to improve your coding is to write more code. This is a bit too simple: writing more of the same, in the same style, usually won't cut it and unfortunately I've seen people being stuck like that for years: always producing more code, without any improvement whatsoever and instead just repeating the same mistakes. Once those mistakes become a habit they are extra hard to get rid of. So actually wr…
One Way to Improve Your Coding
111–120 of 121 posts
Re: One Way to Improve Your Coding
#112The most obvious way to improve your coding is to write more code. This is a bit too simple: writing more of the same, in the same style, usually won't cut it and unfortunately I've seen people being stuck like that for years: always producing more code, without any improvement whatsoever and instead just repeating the same mistakes. Once those mistakes become a habit they are extra hard to get rid of. So actually wr…
I want to recommend everyone who sit infront of a screen for several hours per day to invest a few hundred dollars extra on the monitor. The extra contrast makes a huge difference.
Re: One Way to Improve Your Coding
#113One point not covered by the article is how reading real world code will also help set realistic expectations, especially if you are a relative newbie. The truth is that there is a lot of code in the world, even in popular frameworks and libraries, which does its job but which does so in clunky or unreadable ways. I don't blame this on the developers, on the contrary it's my experience that any codebase will develop…
Good point. I'm always thinking my code is crap (it is) and inferior. But reading other code has made me realize that others code often has its warts too. The key is seeing others code warts (or lack of them) makes you identify your own warts.
So I often just wish I had someone to talk to about what i probably fucked up, or why it was a bad idea. For now my code is just littered with "I did x because y but I'm not sure if z was better or if there's another option I couldn't see".
Re: One Way to Improve Your Coding
#114Earlier quoted context omitted.
Good point. I'm always thinking my code is crap (it is) and inferior. But reading other code has made me realize that others code often has its warts too. The key is seeing others code warts (or lack of them) makes you identify your own warts.
As a self taught "make things that do what I want" sort of a coder, I am eternally worried about the things I don't know. Each solution is the best I could come up with - but I'm confident it's still probably shit. So I often just wish I had someone to talk to about what i probably fucked up, or why it was a bad idea. For now my code is just littered with "I did x because y but I'm not sure if z was better or if ther…
Re: One Way to Improve Your Coding
#115So this is a good place to list really nice codebases. sqlite is a fantastic piece of source code, totally worth reading.
https://www.amazon.com/Computers-Typesetting-B-TeX-Program/d...
Re: One Way to Improve Your Coding
#116So this is a good place to list really nice codebases. sqlite is a fantastic piece of source code, totally worth reading.
Re: One Way to Improve Your Coding
#117Earlier quoted context omitted.
Depends what you are wanting to achieve, to be honest. Writing the same code can help make you faster at writing that code. This can be annoying to people who are higher level coders, but the reality is that intrinsic quality of code is easy to complain about, but hard to model the importance of. In large because its importance is quite low. That is, if what they are writing works, despite having what could be seen a…
That is, if what they are writing works, You make a good point, but imo in real life there is more nuance to it than just works/doesn't work. Which again I've seen with the same collegues: the software works, sort of, yes. Despite some annoyances and known bugs and corresponding workarounds it does what it's supposed to do. But it's oh so brittle. So while you could argue that it works so there is no problem, in fact…
Still, fun to think about. If you know of any studies, I'm interested.
Re: One Way to Improve Your Coding
#118Earlier quoted context omitted.
Good point. I'm always thinking my code is crap (it is) and inferior. But reading other code has made me realize that others code often has its warts too. The key is seeing others code warts (or lack of them) makes you identify your own warts.
As a self taught "make things that do what I want" sort of a coder, I am eternally worried about the things I don't know. Each solution is the best I could come up with - but I'm confident it's still probably shit. So I often just wish I had someone to talk to about what i probably fucked up, or why it was a bad idea. For now my code is just littered with "I did x because y but I'm not sure if z was better or if ther…
Re: One Way to Improve Your Coding
#119Earlier quoted context omitted.
As a self taught "make things that do what I want" sort of a coder, I am eternally worried about the things I don't know. Each solution is the best I could come up with - but I'm confident it's still probably shit. So I often just wish I had someone to talk to about what i probably fucked up, or why it was a bad idea. For now my code is just littered with "I did x because y but I'm not sure if z was better or if ther…
Find someone to trade code review with?
Re: One Way to Improve Your Coding
#120Earlier quoted context omitted.
Find someone to trade code review with?
Turns out all the real devs are kinda busy and don't have a couple hours a week to help all of us people who make their lives miserable..