3

A typical situation in some badly-configured projects...:

1) Having to restart an entire webserver every time you make any change to the code. Hot reload? Unheard of. lol. Then there's also no time to research things because it's push push push.

2) Other ugliness: frameworks so proprietary and locked that you can't hook into anything, so you have to debug using println() everywhere.

I don't suffer from 2) but sadly still from 1).

We live in a world where things are better than this. Come on.

Comments
  • 1
    Unfortunately currently suffering from 2 but not 1
  • 0
    start using IIS and asp.net. Problem solved.
  • 0
    @tosensei dev server is the main environment I work in. I don't want to have to keep redeploying to my dev server for a single change in the code. Great time loss.
Add Comment