Learn More
Resend Email
4
CaptainRant
179d

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.

rant

deployment

debugging

inefficiency
Favorite
Ranter
Comments
  • 2
    179d
    um... hot-reloading on anything but a dev-server is pretty dumb.

    and if you deploy to prod _that_ often that the application start time matters in any significant way, then your whole infrastructure is screwed up in soooo many ways
  • 3
    179d
    Train yourself to deliver more code instead of ctrl+f5 every few lines. I keep on coding until finished and thus keep focussed and then test. Not much reload required.
  • 2
    179d
    Unfortunately currently suffering from 2 but not 1
  • 0
    179d
    start using IIS and asp.net. Problem solved.
  • 0
    179d
    @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.
  • 0
    178d
    @Grumm "problem solved" in the same way that jumping off a bridge does.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment