← Back to context

Comment by eastbound

4 months ago

Oh yes[1]

Then remember when we said tests should be the specs?

Then we said the end users are the specs?

All of them can be construed as a joke in our erratic search for the correct way to write software without those $150k developers that seem to be the only ones getting the job done, assuming they have a competent management hierarchy and stock options incentives.

[1] We have a waterfall software and I wonder whether Crockford’s license “JSON should be used for good, not evil” was meant for me

I think this erratic manner of trying to find the correct way is the issue. I am currently nearing my 2nd year at a company A in my industry, and while I did know they all kinda suck in their own special way, I honestly had no idea it was this bad until I had to try to make this craziness somehow work for us. Even if there are standards, I do not see people following them. Last year, the one girl, who did seem to try to follow some common sense approach, got fired for effectively using common sense against big boss wishes.

What I am saying it is a mess from beginning to end and I am honestly not sure if there is one factor that could solve it..

  • > Last year, the one girl, who did seem to try to follow some common sense approach, got fired for effectively using common sense against big boss wishes.

    What did your manager say when you said this to them?

    • Sigh, sadly, I didn't, because I found out largely after the fact and, more amusingly, after record profit year at the company with the project in question clearly being a major part of everyone's goals ( not mine, I was kinda roped in at the last stages ).

  • Agree it is a mess. I wonder if we would all be better off accepting this and learning to laugh out loud more often.