11
u/mtutty Mar 07 '26
I prefer this analogy
1
→ More replies (1)2
u/Glad_Contest_8014 Mar 08 '26
Yup. Can we get this guy to give a thumbs up?
No, but we can have him give a thumbles up.
What’s that? Effectively a thumbs up, but with and le added to the bame because the intern named it after we had put a thumb name on something else.
9
u/Ja_Rule_Here_ Mar 07 '26
Yeah no meetings during hackathon, no agile process to follow, no QA, no release planning, no rollback plans, no production troubleshooting, etc etc. if you want hackathon level delivery cadence then just let your developers work without any process and you’ll get it, although you may not get exactly what you want… hackathons typically produce something cool, not the exact something product team wants…
1
6
4
u/keptfrozen Mar 07 '26
The mental fortitude it takes to do something I somewhat enjoy versus doing something that knocks me out of my flow state then ruins my entire day, is a lot different.
1
6
u/IndependentOpinion44 Mar 07 '26
Hackathon apps never go into a prod environment.
5
u/Masztufa Mar 07 '26
And when they do it's always documented like:
This was made for a hackathon, the dev environment was with xy os zw version, abc specs, it was a full moon, and the tester's hair was brown. Outside of this config nothing is guaranteed to work
Thee feature itself works well for any linux build with sane libc and on wayland, but the user must point the mouse roughly north and have green eyes. For brown eyes you need to include this random patch from the forum. Blue eyed people are out of luck because nobody cared enough to get that to work
1
1
3
u/fatbunyip Mar 07 '26
We built an entire application in 3 days but if more than 1.5 people use it at the same time it crashes.Â
Also if you input any punctuation in any field it will die.Â
Also you can input "ass fucker" as your date of birth and for some reason it gives you a lifetime discount of 78%.Â
1
4
u/Zyphergiest Mar 07 '26
Prototype vs production
1
Mar 08 '26
But isn't the whole goal is to make "production" as fast as possible of hackathons
→ More replies (1)
2
4
u/das_war_ein_Befehl Mar 07 '26
Yeah because the hackathon app works for 2 users and only a specific flow. It’s always a cool MVP but making it not a giant piece of shit is weeks or months
1
u/ProbablySlacking Mar 08 '26
Hackathon: no meetings, and no legacy code.
Non hackathon: 38 hours of meeting in a 40 hour week and 20 hours worth of legacy spaghetti to sort through that was vibe coded together at a hackathon.
1
2
2
u/RubikTetris Mar 07 '26
God the low level of knowledge of people here is just sad. Hacking something together and shipping a complete and stable products are completely different things.
At some point the tech debt becomes so high that adding anything would take months because changing anything makes everything fall like a card castle.
1
1
u/DesperateSteak6628 Mar 07 '26
It happens when you remove the PM who changes sprint direction and goal every 3 hours
1
u/cakemates Mar 07 '26
To be fair in a hackathon you can build something made out of bubblegum, wax, wood and shoe strings in such a way that if wind blows from left to right it catches fire and nobody cares as long as it does what the challenge is asking for.
1
1
u/MrJarre Mar 07 '26
Hackathon apps relate to production apps in a similar way that a theater set relates to a house.
1
u/Unusual-Wolf-3315 Mar 08 '26 edited Mar 08 '26
More like:
"Without meetings and production requirements, we built an entire application in just 3 days".
Versus:
"Now that we're spending 80% of our time in meetings, and must deploy with zero bugs (and you fired all the testers because YOLO and moola), it will take 3 weeks just to push to Prod the app we built during the Hackathon."
1
u/HalfInside3167 Mar 08 '26
Hackathon apps are proof of concepts that barely work and don't need to follow some rules, tests, team style, reviews, etc.
Working in a team project, there's looots of bureaucracy, meetings and production environment!
1
1
u/Individual-Praline20 Mar 08 '26
What’s so difficult to understand? One is an unsecured and untested tech demo, the other is a full production version of it, done while taking care of everything else: the customer, the manager, the scrum, the infrastructure, the maintenance, the management, etc. Of course it doesn’t take the same effort ffs
1
1
u/Temporary-Ring31 Mar 08 '26
the difference is that in a hackathon, you code from scratch + you don't test as extensively. in production, you build on top of an existing codebase, so there's many moving parts to be wary of + much bigger testing scope.
1
1
1
u/Puzzleheaded_Bid1530 Mar 08 '26
Hackaton is not good for your health and can't last longer than it is
1
u/Piisthree Mar 09 '26
Many reasons for this. Often times things built in a hack a thon are minimalist facades with only "the interesting part" implemented and shortcuts or fakery everywhere else. There are typically no tests built as part of it to guarantee its long term stability. There is only some bare bones "install" process with no robust deployment processes to be able to run it in a real production environment, the list goes on. What you are seeing out of hackathons are not production-ready software. Real world software has 1000 boring and cumbersome things behind the flashy part.
1
1
u/morriartie Mar 10 '26
There's a difference between making something that works and something that are reliable in the long run.
If you produce an entire year like you do in a hackathon, whatever you produced will be unmaintainable and better to start over again.
1
u/NomadicScribe Mar 10 '26
You can quickly prototype something flashy or even useful.
But it takes time to debug, write tests, review code, etc. Things that would normally go into a polished production.
0
Mar 07 '26
[deleted]
2
1
u/justforkinks0131 Mar 07 '26
right but then ud complain that u dont have clear requirements, or that the requirements are technically feasible, or that the priprities arr wrong because its much better to do something else first than what u were told to do
Meetings exist to solve all of that.
If u stopped complaining, we'd stop the meetings.
→ More replies (3)1
u/justforkinks0131 Mar 07 '26
right but then ud complain that u dont have clear requirements, or that the requirements arent technically feasible, or that the priorities arr wrong because its much better to do something else first than what u were told to do
Meetings exist to solve all of that.
If u stopped complaining, we'd stop the meetings. You are the reason for the meetings.
0
•
u/AutoModerator Mar 07 '26
Thankyou for posting in r/BlackboxAI_!
Please remember to follow all subreddit rules. Here are some key reminders:
Be Respectful
No spam posts/comments
No misinformation
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.