loading words...

Jul 25, 2019 13:11:59

When a 2 Minute Jobs Takes 2 Hours

by @jacklyons PATRON | 216 words | 🐣 | 128💌

Jack Lyons

Current day streak: 0🐣
Total posts: 128💌
Total words: 42382 (169 pages 📄)

I hate it as a developer when you think a task will just take a couple of minutes but ends up taking hours, if not days. It's so incredibly frustrating when you know the task should be simple, and yet it turns out to be a monster. When this happens I get incredibly stressed out.

This happened to me last night and again this morning. Yesterday all I had to do was swap out an image on a page, but because the server configuration had multiple layers of caching from various plugins competing with each other, I was never able to see the changes. What should have taken 2 minutes ended up taking a large chunk of my evening.

This morning it was a little different because my client and our API provider are in talks about how to properly handle errors and edge cases when requesting data. This has already lead to a couple of rewrites  to the API service as well as the front end UI. Every time we think we  are close there is always another case that crops up and ruins my life.

I know I will learn from this and it should "hopefully" make me a wiser developer on future projects, however at this moment in time, it sucks!

From Jack Lyons's collection:

  • 1

    @jacklyons - aren't you getting paid by the hour?

    Brian Ball avatar Brian Ball | Jul 25, 2019 13:49:44
    • 1

      @brianball I'd rather get paid for the 2 minutes than the two hours! This shit annoys me so much!

      Jack Lyons avatar Jack Lyons | Jul 25, 2019 15:47:21
    • 1

      @jacklyons - cacheing was invented by Satan!

      Brian Ball avatar Brian Ball | Jul 25, 2019 15:16:45
contact: email - twitter / Terms / Privacy