One Way to Improve Your Coding
changelog.com
One Way to Improve Your Coding
1–10 of 121 posts
Re: One Way to Improve Your Coding
#2This is a great recommendation, at least for middling programmers like myself. Every time I've been forced to dive into a third party library to understand how a certain case is handled or how a poorly documented feature works I've come out more knowledgable about the language, what I'm working on, and programming in general. The key of course is to really try to understand what's happening, not just peruse casually.
Re: One Way to Improve Your Coding
#3I'm going to be "that guy" in the comments section this time, largely because I feel like I've been seeing this more recently and I've had to fix it myself:
I don't really get why it seems to be a "thing" recently for websites to have low-contrast text colors. This is at least the second time in a week I've seen light gray text on white background, and to not strain my eyes I went into the CSS for the website and fixed it myself by just making the text black. Another website was even lighter gray than this one, and it was very difficult to actually read the words. I'm honestly curious as to what it is designers see about the light gray text on white which is appealing to them. It feels like they should be straining to read it just as much as myself, but it still makes it onto the production website. If the person/people who have control over this end up reading this, I implore you to just change your "ol, p, ul" color CSS attribute to "color: black" or some such.
Otherwise: I like the idea of asking developers to read code. It is actually a wonderful way to learn good habits. I still have (good, hopefully) coding habits that I can attribute back to reading Half-Life 2's Source engine code a long time ago.
Re: One Way to Improve Your Coding
#4So 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
#5I'm going to be "that guy" in the comments section this time, largely because I feel like I've been seeing this more recently and I've had to fix it myself: I don't really get why it seems to be a "thing" recently for websites to have low-contrast text colors. This is at least the second time in a week I've seen light gray text on white background, and to not strain my eyes I went into the CSS for the website and fix…
Their text to background colour ratio is 4.6 which is really not that bad with their 18px font-size.
That being said, I'm not a fan of grey on white either.
Re: One Way to Improve Your Coding
#6If you read GPL code you cannot use anything you learn for a company. I feel sorry if a 14-year old learns linked lists from GPL. He cannot ever use linked lists. That's what GPL protects, right?
Re: One Way to Improve Your Coding
#7I'm going to be "that guy" in the comments section this time, largely because I feel like I've been seeing this more recently and I've had to fix it myself: I don't really get why it seems to be a "thing" recently for websites to have low-contrast text colors. This is at least the second time in a week I've seen light gray text on white background, and to not strain my eyes I went into the CSS for the website and fix…
Who knows? Maybe the contrast on their monitor hasn't been set correctly.
Re: One Way to Improve Your Coding
#8So this is a good place to list really nice codebases. sqlite is a fantastic piece of source code, totally worth reading.
Quake 3 is my favorite, to go look for inspiration when stuck. And I'm pretty far removed from game development.
Re: One Way to Improve Your Coding
#9An important thing to remember about reading code is that it does not read like prose. More often than naught, reading raw code, even in the most logical sequence possible (say, UI - View - Controller - Model - Migration), will still be deeply confusing.
If you can get a local version of what you are trying to read running with easily modifiable source code (good luck), then you'll be able to execute and watch for changes. In my experience, the two most helpful ways to "read" code are using the tests first and documenting functionality second, both of which the author mentions.
Re: One Way to Improve Your Coding
#10Any recommendations for an open-source Java codebase to read that makes good use of the Java 8 concurrency features? Currently in a new job and struggling with an undocumented, uncommented codebase containing streams, rxjava, executors and futures. Could do with a different, hopefully documented, take on Java concurrency.