|
This!
We're currently replacing an application that mixes application and ERP database tables in a single database.
The ERP has an API, so we want to use that and create our own database so it's completely seperated from the ERP.
Of course, we also have an API we use for our applications.
Now I was on vacation and one employee said to the other "we're going to migrate those ERP tables to the API" and the other employee spent a whole day incorporating the ERP tables into our own API 
When I got back from vacation and I heard that, I had to muffle a scream, as this is a sharp priced fixed price project 
I briefed them about this before my vacation and I left comments in our API code saying "This will be migrated to the ERP API.", but he forgot and didn't read the comments...
Now I, a good "boss", took a mental note "brief even better next time this situation occurs."
A bad boss may have scolded the guy.
But sh*t like this happens, scoldings or no.
When you scold them they'll simply stay quiet next time, be afraid to take initiative, or leave altogether.
That said, I may not always been as nice when stuff like this happened in the past, and I will lose my temper again in the future 
|
|
|
|
|
Sander Rossel wrote: That said, I may not always been as nice when stuff like this happened in the past, and I will lose my temper again in the future 
That's exactly it man. Two or three times and we're all human. Even if it cost money. Lord knows I've boo-booed enough to not hold it against others.
But, the analogy I give is imagine going to a mechanic when your car has a problem but instead of fixing it he goes for a joy ride and charges you anyway. That's what it feels like... if you're lucky. If you're not lucky the mechanic makes the car worse and still charges you.
So, a good employer is really a gem as it takes a good level of maturity. But if it becomes a habitual pattern that goes on for a year or so... time to rethink that employee. Which, I could be wrong, but given the OP... wouldn't surprise me if he fits the bill.
Side note, I know in my experience, a lot of devs just "check out" in meetings and pretend they don't. Or they don't understand something and will never speak up. Nobody wants to be that guy who says "dunno", so a lot just pretend to know when they don't. So, if it's talked about you still need to be very, very explicit in a story, etc. with some devs regardless.
Jeremy Falcon
|
|
|
|
|
Jeremy Falcon wrote: Or they don't understand something and will never speak up. Nobody wants to be that guy who says "dunno", so a lot just pretend to know when they don't.
Two answers to that:
- It is better to shut up and look stupid, that to open your mouth and confirm it.
and / versus
- It is better to ask and look stupid, but learn about it, than to not open your mouth and do the dumbest and most avoidable error confirming your lack of knowledge.
The art is to know when you are in which situation.  
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
That's no way to talk to an 80 y/o! 
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
“if I want your opinion, I’ll ask for it”.
It gets better.
If I want your opinion, I’ll give it to you,😁
|
|
|
|
|
You would still complain if hit with a golden hammer.
|
|
|
|
|
I've heard,
Boss: "Well, if I wanted it tomorrow, I'd ask for it tomorrow."
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Less than an hour after the Boeing/ULA rep made the (provably false) statement on live NASA TV that Starliner was riding on top of the most reliable rocket ever built, the launch was scrubbed due to an oxygen valve failure in the 2nd stage.
The slogan used to be "If it ain't Boeing, I ain't going". They lost this when they removed engineers from the C-Suite.
|
|
|
|
|
Nothing wrong here.
How many nasa launches were scrubbed because of a sensor glitch ?
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
While I agree that the launch scrub was the right call, the disconnect between the ULA spokesperson's statement about the Atlas V being the most reliable launch system ever, the scrub, and the fact that SpaceX's Falcon 9 now has more successful launches and booster recoveries than Atlas V has launches just screams propaganda.
|
|
|
|
|
obermd wrote: the launch was scrubbed due to an oxygen valve failure in the 2nd stage
A lot more honest then say, Morton Thiokol.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Morton Thiokol told NASA not to launch the Challenger that day. NASA overruled them because President Reagan was visiting.
|
|
|
|
|
Morton Thiokol ultimately approved the launch, against engineers recommendations.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Morton Thiokol only approved the launch after NASA threatened to blacklist them for future contracts.
|
|
|
|
|
Agreed, it's a tough spot for them, nevertheless they bowed to the pressure.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
|
obermd wrote: They lost this when they removed engineers from the C-Suite.
Entirely correct. Of the three major defense companies I worked for in the past, none still exist. The end was clear once the MBAs and other unqualified suits took over management from the engineers who successfully ran the companies for decades.
Will Rogers never met me.
|
|
|
|
|
Case in point:
the 3 top level people at SOuthwest airlines are all accountants. They gave out over $5 Billion US dollars in stock dividends. They ignore the 1908s' level tech running their IT operations. IT cost them fines and passengers back in 2022(?) when they cancelled thousand of flights do to issues with their IT. Their IT is admittedly underfunded.
Cegarman
document code? If it's not intuitive, you're in the wrong field
Welcome to my Chaos and Confusion!
|
|
|
|
|
and outsourced their software to people who don't know planes.
Understanding the domain of where your code is going to work is critical, especially so in things that can go boom.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
I can clearly recall the years when I worked for Ace Hardware for lack of a "real" job. The software they used was top of the line - a proprietary multi-tasking version of DOS called SuperDOS - and it was crap. One IBM PC ran three stores, two in our area and one in Reno, NV - using RS232 serial ports. It was easily the least reliable system I've ever seen, but it worked. The problem was, the software didn't do the things that a hardware store and lumber yard need it to do. I decided then and there that any programmer who intends to work on an industry-specific software product should be required to work in the target industry for 2 - 5 years before being allowed to code a single line.
Will Rogers never met me.
|
|
|
|
|
Maybe any other rocket would've had at least two oxygen valve failures 
|
|
|
|
|
Perhaps, for the first time in this millennium, FORTRAN comes in the Top 10 TIOBE Index - TIOBE [^]
As a side note, my 'mother-tongue' is FORTRAN, being the first computer language i learnt in 1987.
Hope this news isn't a repeat.
|
|
|
|
|
The joy of fixed column coding.
|
|
|
|
|
Not to forget the now infamous GOTO, which was indeed a saviour in those days.
|
|
|
|
|
Amarnath S wrote: GOTO, which was indeed a saviour in those days
Not in 1987! Maybe it was true in 1967, although we had had Algol since 1960 (or 1958 for early blomers).
In 1968, we had the first major revision of Algol. Pascal arrived in 1970, Modula in 1975, C++ in 1985.
Dijkstra's "Go to statement considered harmful" is dated 1968.
If you considered GOTO 'a saviour' in 1987, you were either badly uninformed or extremely slow in adopting modern programming trends.
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
