Scubabear68

We found this out the hard way in a small startup. The per query and I/O expense was through the roof.

It is amazing how much of basic science is rooted in simple geometry.

As a tangent, the author says Tesseract based OCR didn’t work very well. Sadly this matches my experience too.

What products (open source or closed) have higher accuracy for vanilla English documents?

Simplicity can be taken too far. Take this to its logical close cousin and you would have Forth or Basic.

Also, we have been doing computer language design for quite awhile now. This isn’t a new frontier. The deficiencies in Go aren’t in areas of “oh, we never thought of that!”, but are in very well known areas with known solutions.

I find Go code is obscured with house keeping code that isn’t necessary in better languages.

It has always been surprising to me how primitive Go really is, for no really good reason.

I understand the evolution of C, it made perfect sense back when it was invented. And the limitations were necessary due to the wide array of architectures and extremely limited computers of the time in every dimension (CPU speed, IO speed, RAM size, disk size, etc).

Many of those dimensions have been improved by several orders of magnitude, and both compilers and runtimes can afford to be comprehensive. Yet we get this ham-strung language out of the gate.

Very disappointing.

They all do.

The “rip everything out” step is not recommended. You will break things you don’t understand, invoke Chesterson’s Fence, and create enormous amounts of unnecessary work for yourself.

Make it compile, automate what you can, try not to poke the bear as much as you can, pray you can start strangling it by porting pieces to something else over time.

I agree with the consensus here that the cost issues are a cloud problem, not serverless. Ironically, something like AWS lambda has a default 1,000 simultaneously activated lambda limit, so the platform defaults to throttling.

Not that serverless is perfect.

The “micro” moniker is very unfortunate. I have seen architectures where endless strings of lambdas are strung together like function calls, with the developer not realizing or caring that each is a process, and each call is a network call. Literally one service per function, with the completely expected result of horrible performance and high error rates.

They should’ve been called domain services or something.

One thing that stood out to me - based on the narrative here the tail hook never could work in real world conditions. The blog mentions that the computer model used by the manufacturer was wrong.

Does that mean that manufacturers don’t field test the hardware? If so, that is scary.

I’m surprised they don’t already have digital menu boards at all locations, they are really good at driving promotions.

The difference is if Monty has a chance to accidentally open the door with the car.

Ah the C pre-processor, the gift that keeps on giving after all these years :-(

“His academical record”.

I dropped out of college young, for complicated reasons. It has never, to my knowledge, been an issue with any potential employer.

And I also disagree with wanti g someone with a “good work ethic”, as you say. People with a good work ethic will grind out mediocre code year after year. I want a creative lazy coder who will find a smart solution or piece of automation to save himself work down the road.

No, I don’t ask them to show me any code or artifacts, but to simply describe the architecture, how it’s put together. Any novel code or algorithms they are proud of. Areas of the code that were problematic, and how they would fix them if they had the chance. Talk about non functional requirements and if the architecture addressed them or not.

Basically see if they could communicate how the system worked, it’s good points and bad points, and how deep they could go. This quickly separates the good developers from the cargo culters and pretenders. It also is a good gauge of how much real experience they have had.

Generally, if someone can’t describe at least the rough outline of the architecture of an application they have worked on, that’s a strong signal they are going to struggle as a developer

The problem is that Uncle Bob made up SOLID and other ideas more or less by cobbling random ideas from other people and selling them on the market as his own. As many others have mentioned here, pieces of SOLID kinda-sorta make sense, but it doesn't hang together cohesively because it was never created in a cohesive manner.

ALWAYS look behind the curtain at what software consultants are selling to what they have actually built, and then you can ascertain if they are selling you hard won engineering knowledge or a bunch of marketing BS.

Back in the 1800's and early 1900's medicine was a very new science (in a modern sense), and snake oil salesmen abounded. Laymen had very little information to discern legitimate medical advice from quacks hocking piss and ink as a cure all.

We have the same problem now with software systems, although at the least we are advancing beyond the primitive stages and the charlatans are becoming more apparent.

Take a look at Uncle Bob’s code some day. You will then realize that all of his writing was synthesized solely to make him consulting money. His actual code is rubbish. This has been true all the way back to the 90’s with his inane questions to the OOP Usenet groups.

I have been interviewing technical candidates for decades. I have found the most effective approach is to deep dive into systems the interviewee has built. This puts them comfortably in areas they should know, and very quickly how shallow or deep their knowledge is.

Asking random questions about technology mostly tests their ability to memorize facts. I want people who know how to build things in the real world, not those who excel at adding certifications to their LinkedIn.

A parting word - if you are leaning towards Uncle Bob for wisdom, you are heading in the wrong direction.

The amazing thing to me about dogs is the tremendous range of variability we have bred into them. Size, shape, color, intelligence, basic body makeup, senses, hunting instincts, even average life span vary by an astonishing amount.

And sadly, of course, the selective breeding has also caused systematic weaknesses in some breeds (prone to bad hips, knee injuries, relatively short life span, etc).

The genie is out of the bottle but I wish we could breed healthier animals.

You don’t need a prep course to do well in the SAT. I did quite well with no work at all beyond school work, and I know kids today where it’s the same.

As others have indicated, you can just buy a prep book if you want and be done with it. The prep courses are just separating parents from their money.

I worked with an energy company who has a huge custom accounting package written in Delphi. They got a lot of bang for the buck out of it over the years but is causing obvious problems now with all the logic embedded in the client.

Maybe not perfectly level, but more so when colleges did not look at standardized test scores.

I know the PSAT and SAT can be taken multiple times, and often starts with PSAT as a sophomore. Very common to take SAT as a junior, and then again as a senior if you weren’t happy with your junior score.

Have not heard of traveling outside your district for SAT’s, I’m not sure why that would happen.

Yep. Universities tried to track relative strength of GPA to school districts, but ultimately that is a hopeless task. Our own district has been guilty of severe grade inflation and teaching 2-3 grades behind grade level to the point where a “B” here would be a D or F in a college prep private school.

Standardized tests are imperfect, but they are not entirely flawed the way high school grades are.

This will also re level the playing field for poor families with smart kids who can’t afford all the extra-curricular wealthy families lean heavily into.

A huge number. I do a lot of due diligence of companies, and the over engineering on the cloud and costs have to be seen to believed. A common theme now is people use lambdas and step functions in replace of function calls. So a page load or transaction may involve two dozen serial lambda invocations. It is madness.

By way of contrast, a payments provider we explored had four moderate sized boxes running everything. They were about six years old and fully depreciated, but more than adequate to run millions of transactions through a month.

My family tried home care in the terminal stage, but it was too much for my mom and sister. My mom also had some serious mental illnesses, compounding the difficulty we had as a family. The trauma was so great I did not really hit a normal state of emotional and mental stability until I was about 30.

I was the only one there as he took his last breath, and it still brings tears when I think about it.

I really am shocked that GCC took K&R, pre-ANSI C for this long. For Pete’s sake, I was ANSI-fying Aztec C libraries in the late 1980’s!

Same with my dad in the 80s. His descent was horrible to witness, in my case at the age of 21. I’ll never know the truth, but I think his doctor took pity on him, dad died very shortly after a push of morphine.

She leads with fonts being the most important aspect of beautiful slides?

Sorry, that is very backward thinking. And not very helpful at all if you have to follow a style guide (like for your company).

Content is the most important thing for any slides. “Beauty” means keeping slides simple and to the point. Very simple graphical composition can go a long way.

I also am not a fan but personally of overly cartoony kind of presentations. It fits in some contexts, but when I see it in engineering or development it rankles me. Maybe I’m just old.