3 ms·
"and then build a crappy, I-hope-nobody-sees-this-code prototype." And it'll end up being 'production' code because "we already have it and they already paid f
by mgkimsal 16y ago
"and then build a crappy, I-hope-nobody-sees-this-code prototype."
And it'll end up being 'production' code because "we already have it and they already paid for it!". And the crappier it is, the longer it will remain in production and the harder everyone will fight against rebuilding it to be not crappy.
- preek 16y agoThat's why I quit my job at a big corporation (not a classic IT behemoth, though) and will start working at a startup in two weeks. The code there sucked - and most coders did, too.
- j_baker 16y agoI hope you aren't expecting startup code to be a lot better. Not only will startup code tend to be crappy, but you run into a ton of people (managers and coders alike) who will all but insist that your code be a certain level of crappy. In other words, if you write good code, then you've spent too much time on it and should have moved on to the next project. I don't mean to give you the impression that your new job is going to suck. If you chose the right startup, you're going to have an awesome time. But I also think it's important to be realistic.
- danenania 16y agoIs this such a bad thing? Engineers often have a tendency to to focus too much on writing 'good code', and forget the bigger picture of what they're working on. Technical debt is a real issue, but it's something to manage, not eliminate. I'd much rather be in a place where most engineers have at least half a pragmatic eye on products, features, and ux rather than only caring about code quality and the elegance of their algorithms. Yeah, it can also be good to have a few of those code quality sticklers around to keep everyone honest, but they shouldn't be running things or setting the tone. I think a big part of the reason a management tier is needed at all in a lot of smaller companies is the general unwillingness of engineers to sacrifice code purity for expediency.
- j_baker 16y agoAnd I think the need for engineers in smaller companies is the unwillingness of management to sacrifice expediency for purity. :-) Regardless, that's beside my point. It sounded like the person I responded to wanted to work on better code, so I was just pointing out that startups aren't necessarily any better in that respect. I'll leave it to him to determine how good or bad that is as I'd really rather not get involved in this old debate again.
- cicero 16y agoWhen I went from a big company to a startup, I saw a significant increase in engineering talent. There were some good people at the big company, but there was also a lot of dead weight. It was easy to just coast through a project there. At the startup, you had to be sharp, or you were out. I won't say the code was always pretty at the startup, but due to the higher level of skill among the developers, I think the code there was superior to what was produced at the big company. Although the startup went under after I was there 2 years, I learned 10 times the stuff in 2 years of the startup than I did the previous 5 years at the big company. The skills I learned at the startup allowed me to get into a much better job at another big company that I stayed at for 11 years.
- j_baker 16y agoThat's the position I'm in right now. I'm not saying there aren't startups with good code out there. I'm just trying to say that it's not startup_code == good && bigco_code == bad
- Devilboy 16y agoAt a startup the code will still be bad but there won't be anyone to blame.
- rmc00 16y agoVery true. I recently inherited an application at work that has a dark corner where a past co-worker wrote a crappy, I-hope-nobody-sees-this-code prototype. While the code does produce correct results, it's very messy. Most of the people who really understood how it works have left over the years since it was built too. I've been trying to understand exactly how the application works, and it's way more effort than it should be. The point is this: build your software right. At the very least, only take reasonable shortcuts, and make sure you come back around to fix your crappy design at some point. The longer it festers, the worse it will get.