Re: Docker

 I think we are very like minded courtesy of the training.
Whenever I bring up the C compiler bug and people go.... why in the heck would i++ and i=i+1 execute differently?  They wouldn't.Ahh.... but yes they did.  It was due to the person who interpreted the meaning of one versus the meaning of the other.... in assembler....
Having to go through stor(es) and inc(rement) into registers versus storing the values of i and 1 and getting the result and storing it in the new value of i.... extra steps that cost a lot in the end.
I think K&R C was in use for at least 10 years before it was discovered.
I remember trying to do simple digital logic circuits with Karnaugh maps etc. and trying to optimize logic down to just a few logic gates on integrated circuit chips of NANDs, ANDs, XOR, OR, NOR.
Trying to keep costs down by optimally lowering the amount of chips required to get full functionality.
VAXen and PDPs with REMOVABLE DISK pack of 20 MB.... that weighed 20-30 lbs. :)  Platters that were the size of vinyl records.... Running BSD 4.x
I was pretty crotchety when people started with containers and virtualization and... MICROSERVICES....  I was like:  you do understand what a scheduler and time sharing are all about right?  You know about UNIX, right?  You do know about "nice"  why would I want to put limits on some simulated machine and expect it will work better than the job control and scheduler of the kernel?
Yeah... boomer mentality....  But we continue to work on this stuff.... Honestly, I can't wait to fully retire.... I have a lot of cycles I want to donate to BSD.
Paul

    On Monday, April 17, 2023 at 11:29:56 AM PDT, Tim Daneliuk <tundra@tundraware.com> wrote:  
 
 On 4/17/23 12:34, Paul Pathiakis wrote:
> Personally, I haven't see it yet. Again, I hated getting a CS degree.  It was hell on wheels and kept running me over.  The incredible amount of math, automata theory, etc, etc.
> Then, I got out in the 'real world'.  I was thoroughly shocked at how people casually threw aside critical thinking, design, implementation, project planning, software engineering paradigms, and started to 'program' 10 years after I got out.


I have a Masters in CS, and an uncompleted Ph.D. (I guess that makes me a college dropout.)
Both were in the strongly theoretical end of CS, with a focus on computational
theory, as well as the design of computer languages.

I have found the theory to be very useful in understanding problems and
reasoning about how algorithms and data structures and so forth can
foster better design.  As you suggest, these encourage critical thinking.

What you see today is people screaming for "agile" when you ask for
time to do careful requirements gathering.  Young "coders" come out
of bootcamps that teach them one language and an IDE with absolutely
no understanding of the overatching environments in which they are
coding, let along a firm grasp of algorithmics and data structures.

I feel I am far afield and showing too many Boomer feathers.

"In my day, we didn't have 1s and 0s, we had Ohs and Ells and we LIKED it .."