The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I found this video in my recommended video feed on YouTube and I actually clicked it and was quite impressed and entertained. I have watched a few more videos by Practical Engineering channel and all were great.
As I was watching this, I could not help but draw various comparisons between Civil/Infrastructure Engineering and software engineering and program/system design and testing. Granted, most of our applications and systems to do not impact people's lives in a "life and death" situation, but crap happens when we don't plan well enough, or test well enough, and even then, with the best planning, bad things will still happen.
I could not help but draw various comparisons between Civil/Infrastructure Engineering and software engineering and program/system design and testing.
Yes, indeed! "Periodic design reviews over the lifetime of the project"? "600 pages postmortem reports"? I've never seen that in our field where some people still resist informal code reviews and hate unit testing. It's true that civil engineering has had more time to develop these methods from the roman aqueducts to the Oroville Dam, but it is still sobering to see how true engineers solve serious problems.
Maybe we should just stop calling what we do "software engineering" and call it for what it is: just hacking.
"When you are dead, you won't even know that you are dead. It's a pain only felt by others; same thing when you are stupid."
Ignorant - An individual without knowledge, but is willing to learn. Stupid - An individual without knowledge and is incapable of learning. Idiot - An individual without knowledge and allows social media to do the thinking for them.
Responsibility for human safety is a scary thing. In the mid-1980's I worked for a defense contractor. Our main project was building an emulation of the flight control system to be used in an experimental version of the F-16. The purpose of the emulation was to validate the design of the actual flight control system. I'll always remember something our aerospace engineer told us during one of our status reviews:
"This program is of vital importance to the safety of the pilot. The flight controls can operate the plane in an unstable state for performance. If those flight controls fail, the pilot dies 2-3 seconds later."
I could screw up a few lines of code, we would fail to find a design flaw, and someone could die. Scared the piss out of me, and was a factor in my decision to get out of defense work.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
This is using nearest color matching to convert 24-bit color jpeg (Y'CbCr) to a 3-color device (indexed pixel format - 0:black/1:red/2:white)
I don't have an 8-color display yet, but when I get one and add dithering support to GFX it's going to be fun to load photos into it.
Anyway, the work that went into this, and the thought behind it is why I'm proud of it. It makes a super complicated thing simple - so simple that it's hard to appreciate it unless you had to make it. I think most of the people that have seen it in the ESP32 forum I haunt don't understand why it's a big deal for color e-ink support.
On the other hand, my graphics library overall has garnered more interest than I ever anticipated so I can't complain.