4 ms·
My experience with professional software development looks like this, in a loop: Let's add a new button! How many story points is the button? (Insert 2-hour di
by gurkendoktor 6y ago
My experience with professional software development looks like this, in a loop:
Let's add a new button! How many story points is the button? (Insert 2-hour discussion about what a story point is) Okay, "Uncle Bob says" we need at least seven layers of code around it. Someone insists on doing it "TDD", even though the UI framework is not testable. Oops, the Agile Consultant broke Jira, it will be back up in two days. The PR gets stuck for days because of trailing whitespace violations. The button doesn't actually work, but the outsourced developer complains loudly until someone gives in and merges it. Review time!
The code that results from this madness is not better than Hackathon code, just bad in a different way. If anything, my last Hackathon has made me aware of how much I want to work for an effective company at some point in my life, so I guess it was worthwhile.
- deleted 6y ago[deleted]
- xinsight 6y agoI feel your pain. But ideally, once the PR code is merged, the end result should be solid code. Anything you write at a hackathon is fake/barely-functional throwaway code that only exists for the demo at the end. There's no architecture, no error checking, and just no time for anything elegant or any real insight into your problem space.
- marcus_holmes 6y agoTotally agree that half the fun of hackathons is throwing away all that shit and just fucking building something :) But I never have to go back to hackathon code 3 months later and fix it. Bitter experience has taught me that at least some of that stuff (like the unit tests) is not optional if I want to stay sane.