he/him 
JS show idea: developer is given requirements for a modern interactive webapp but they’re only allowed to use tools from five years ago (before front-end became complicated).
Show this thread
-
Also not just “build it once” but maintain it with changes in requirements every week. On a team of five people.
Show this thread
You’ve turned this from an interesting exercise to something with very unrealistic requirements.
-
-
Plenty of people seem to think it’s realistic tbh
-
I mean, your first two tweets is something someone could do at a hackathon. The third tweet makes it seem like some sort of product commitment/experiment that nobody will actually do. It’s like trying out being Amish when you run a car factory.
- 1 more reply
New conversation -
-
-
Eh. I don’t see this as unrealistic at all. I would build this routinely with those requirements at that time. It just sucked.
-
The requirements are oddly specific techniques though. You ended up with similar solutions but nobody’s business requirement was “splitting code per route”. You just ended using with similar solutions to solve load problems.
- 1 more reply
New conversation -
-
-
It wouldn't be a real project without unrealistic requirements
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Isn't that the point?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.