Working with old people...
Have other people experienced how arrogant some of these baby boomers can be at the office. Some companies just have a collection of these senior engineers who have stayed at one company for their entire career. Just had a discussion with this senior engineer (in his 50s) who thinks that it's fine to test the software in debug mode, then recompile in release mode and ship it, untested. Just completely boggles my mind. He even thinks that if we were to do testing on release, performing unit tests on release is not necessary. That debug is for unit testing and release is for higher level testing. Do you even try to convince or argue at this point? How do you handle these type of scenarios where you know they are completely wrong but you are junior to them? Update: My team lead went up to him and convinced him. Seniority at it's best.
In same situation as you. In my case, the young guys knows nothing and acts entitled. What to do?
don't think of their age when you're having an argument. try to show examples why this is bad, like "well what if the release build introduces a bug?" and try to think of a scenario under which this could happen, etc. and last but not least, if you really think it's not salvageable, and their managers allow this to happen, maybe it's time to change companies?
Yes, I'm the type that pokes holes in everyone's argument. But this one just doesn't get it.
Everyone’s arguments? Hmm. Now I see where the problem is.
i fucking hate working with boomers. they need to hurry up and get out of the workforce already.
one day, you're going to be old too...
Your parents must be proud of you
This
Wrong. Baby boomers have a generationally distinct style. Denying this speaks to your ignorance/idealism.
I m in exactly same situation . In my case old guy is just chilling. He is on retirement mode. No worry. He spend hours taking about some history or travel. But no idea about design
If this particular old dude has been working with this code base for 10+ years already, has a history of not releasing defects using his existing method, and you are new, then you should STFU and realize that he knows WTF he's doing and is just being efficient. One size does not fit all and the best practices industry wide don't actually apply to all situations believe it or not.
What happens when he is no longer there to support the program? The CI process will take over where he left off if the tests were performed.
If you take it over, then do it your own way. The most important thing here would be the current bug count per release. If it's really low, first try to figure out and learn how that is done. Otherwise yeah you should improve it.
I find arrogance and incompetence at every age. It’s called arrogance and incompetence. End of story. Now get get back to work you whiny know-it-all millennial. 😉
Are you missing some nuance here? I suspect they're saying sanity tests are good enough. If it's an old hw/sw build environment, they may have never found any bug in non-debug that would be missed in debug testing. Sanity tests are necessary. More testing than that is a business decision depending on the cost of full testing. (Don't do this if you use VMs for builds. They increase the risk and incur higher test costs.)
I believe he was eluding the fact that there was extra behavior that happens in debug that doesn't happen in release mode. That release mode is a subset of debug.
Yes, in some sense, that's correct. It depends on how elaborate and robust your tests and build verification are.
This has helped me a lot. The Schmuck in My Office: How to Deal Effectively with Difficult People at Work https://www.amazon.com/dp/125007567X/ref=cm_sw_r_cp_apa_i_uLFTCb48XRBTD
Yea millennials are known for being entitled but I actually have found older folks are more so