4 ms·
Learn to be a "programmer" not a "X programmer". I recently sat down to learn Python a bit. Inside of a week I had useful code up and running. I'm sure it was
by bane 12y ago
Learn to be a "programmer" not a "X programmer".
I recently sat down to learn Python a bit. Inside of a week I had useful code up and running. I'm sure it was non-idiomatic and I'll laugh from embarrassment a year from now, but screw it, it works, and real people ship.
The last code I wrote before that was in Java. I had to relearn it after a decade of non-use. Real people ship.
More recently I wrote some more Python code, it's all hacky and terrible, I can feel it, but you know what, it shipped and has kept a half-dozen people employed for another few months. Real people ship.
Most recently I had an issue to solve, not wanting to fight Python's 2.x's stupid typing issues, I hacked it out in Perl. The solution shipped. Real people ship.
GSD (get shit done) and move on. It doesn't really much matter what it's written in. It's all bits and bytes, 1s and 0s in the end.
Real people ship.
(also, don't work for free)
- SwellJoe 12y agoI think chromatic has more than earned the right to call himself a "real programmer". He may not be a real business person...but, he's demonstrably a real programmer.
- gaius 12y agoDomain knowledge trumps language in the real world. It's funny, we mock MBAs who believe they have the generic skill of managing anything, but how many programmers think that they can write programs in any company or industry?
- douche 12y agoOn GSD: You do this for long enough without ever cleaning up after yourself, and you're left with a massive, steaming pile of garbage that you have to then support and maintain. Maybe you're lucky enough to be able to write fire-and-forget code, but in my experience, writing hacky terrible code to ship something just means that I'll have to spend 3-5x time on the phone troubleshooting with a customer, analyzing logfiles and then writing the code the right way in the end, than if I had just done things right to start with.
- vinceguidry 12y agoIt depends on the setting. If you're working in corporate world where the amounts of money flying around dwarf your considerable hourly rate/salary, then what they're paying you for isn't the quality of your code, and what you've written will probably just be thrown out after it's served its purpose. If you're having to maintain your own code long-term, absolutely. But that's not every job. It's good to get a feel for what's required from your boss and to keep in mind that the requirements can change from project to project.
- bane 12y agoThat is absolutely a fair point.