5
eloy
4y

There is a side project that they've been working on. The CEO laid out the details to the Product Owner and Tech Lead. Now what he wants to happen is beyond the scope of the business core itself and it would take months to do the changes just to make the side project work. Now both of them ask the timeline for this, CEO said 1 week. 1 fucking week (he's a dev in his glory days which is why the short timeline). He know proceeds to suggest to us how we should do it (like he normally does). But Tech Lead knows better. So with the help of one of the junior devs, they proceed with the Tech Lead's plan. Now come for updates, they presented that its working and such. The CEO became furious as to why they decided to design it that way (of course you dingus, you gave them 1 week and expect quality). Now what triggered me was 2 things, first is his comment on the way they designed it. Its "flawed design". WTF ARE YOU EXPECTING? YOU ARE A FORMER DEV. YOU SHOULD KNOW BETTER. Second, is the junior dev is asking me about the project. WHY IS HE ASKING ME. I always tell him that ask Tech Lead. Some of his questions should have been answered by Tech Lead. He even questions the design itself(why they designed it the way they did). I DON'T EVEN KNOW WTF Y'ALL BEEN TALKING ABOUT THIS PROJECT AND YOU'RE ASKING ME. Flawed design, more like flawed communication.

Comments
  • 0
    @jennytengsonM 00s were 10 years ago already, someone who was a dev in early 90s or in 80s has likely retired by now...

    Anyway, throwing security, scalability, and code maintainability out the window like they did with most software back in 00s, a week is plenty to make something work.
Add Comment