Readit NewsDon’t let Karen and her buddies run the meetings.
People nagging about HOA seems like are not owners or not knowing how HOA works o r supposed to work.
This is the talk on real software engineering: https://www.youtube.com/watch?v=RhdlBHHimeM
This is the talk on real software engineering: https://www.youtube.com/watch?v=RhdlBHHimeM
No, it really isn't. I don't know which amateur operation you've been involved with, but that is really not how things work in the real world.
In companies that are not entirely dysfunctional, each significant change to the system's involve a design phase, which often includes reviews from stakeholders and involved parties such as security reviews and data protection reviews. These tend to happen before any code is even written. This doesn't rule out spikes, but their role is to verify and validate requirements and approaches, and allow new requirements to emerge to provide feedback to the actual design process.
The only place where cowboy coding has a place is in small refactoring, features and code fixes.
Operation that delivers features instead of burning budget on discussions.
Operation that uses test/acceptance environments where you deploy and validate the design so people actually see the outcome.
Obviously you have to write down the requirements - but writing down requirements is not design phase.
Design starts with idea, is written down to couple sentences or paragraphs then turned into code and while it is still on test/acceptance it still is design phase. Once feature goes to production in a release "design phase" is done, implementation and changes are part of design and finding out issues, limitations.
I disagree. The design phase of a substantial change should be done beforehand with the help of a design doc. That forces you to put in writing (and in a way that is understandable by others) what you are envisioning. This exercise is really helpful in forcing you to think about alternatives, pitfalls, pros & cons, ... . This way, once stakeholders (your TL, other team members) agreed then the reviews related to that change become only code related (style, use this standard library function that does it, ... ) but the core idea is there.
Because in the software engineering world there is very little engineering involved.
That being said, I also think that the industry is unwilling to accept the slowliness of the proper engineering process for various reasons, including non criticality of most software and the possibility to amend bugs and errors on the fly.
Other engineering fields enjoy no such luxuries, the bridge either holds the train or it doesn't, you either nailed the manufacturing plant or there's little room for fixing, the plane's engine either works or not
Different stakes and patching opportunities lend to different practices.
Writing code is the design phase.
You don’t need design phase for doing design.
Will drop link to relevant video later.
The difficulty of modifying the body, is mostly a financial decision I think. The body is by-and-large optimized for assembly rather than repair and modifications - that's why body shops charge an arm and a leg.
> Crumple zones are model specific you can’t just change those without making new car.
Yep, and I think that's the problem. Cars should be designed in a way that you can make this kind of safety upgrades. There's little technical reason why with a more modular body and platform, the manufacturer can't design a new crumple zone for retrofit, run finite element analysis, and crash test it.
They may need to rethink fundamentally how mass-market cars are made, like using more fasteners instead of welding in the body and frame, or using plastic instead of sheet metal when they are not necessary, like for the body panels.
That old malfunctioning airbags should be able to be replaced easily.
But then it would incentivize the customers to keep their old cars instead of buying new ones.
My guess is you know nothing about it based on malfunctioning airbags that should be possible to be replaced easily.
Airbags are one action components so until they fire up you don’t have certainty. You might check electrical connections or replace them „just in case”. Yes airbags might not be good after 15 years and I don’t think anyone who is driving 15yo car has money or is willing to spend money on replacing them.
Well put.
The fundamental flaw is in trying to employ nondeterministic content generation based on statistical relevance defined by an unknown training data set, which is what commercial LLM offerings are, in an effort to repeatably produce content satisfying a strict mathematical model (program source code).
It kind of extends to my house as well, like I have intercom disconnected most of times and I connect it back when I expect visitors or delivery.
I was a teenager like 20 years ago.