Skip to main content

learn vascular surgery in 24 hours

Ok - it's a bit profane but I couldn't resist after I read the line:

"when was the last time you were meandering through the bookstore and you spied learn vascular surgery in 24 hours?"

Where is THAT book? Sounds like an idea for the dummy line:

"Neurosurgery for Complete Dummies" by Dr. V. Frankstein

- Learn how to find the right donors for your subjects
- Circumvent the hydro company with your own power generation
- Learn why corks make the best necklaces around
- How to find the right girl for your new best friend

On a more serious note, caustic has some major issues with things that are 100% valuable. If I buy a book and get at least 5 good ideas from it, it's worth it. I don't care if they are in the form of tips or do's and don't. The fact is that people who buy books want to enjoy reading - just because caustic likes reading dictionaries doesn't mean that everyone else should have to.

Look at Dynamics of Software Development - that was a great read as was Code Complete. Were there sections that were, um, dry? Yes - but the real benefit were the core concepts that people got out of it.

If I want to learn something, I'm going to learn it - but I would at least like to make the experience enjoyable. Just like attending classes or conferences - I want a teacher who engages, not one who makes me read right out of the textbook.

Caustic reminds me of Eddie Murphy or any one of those other comics who feel the obligation to swear to get his point across - it actually diminishes the point he is making. Once is fine - hell even twice is okay - but when every 5 words is crossed with crap, he starts to sound exactly like those blithering idiots he feels are wasting his computer library choices.
causticTech: learn blithering idiocy in 21 days

Comments

Popular posts from this blog

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Respect

Respect is something humans give to each other through personal connection. It’s the bond that forms when we recognize something—or someone—as significant, relatable, or worthy of care. This connection doesn’t have to be limited to people. There was an  article  recently that described the differing attitudes towards AI tools such as ChatGPT and Google Gemini (formerly Bard). Some people treat them like a standard search while others form a sort of personal relationship — being courteous, saying “please” and “thank you”. Occasionally, people share extra details unrelated to their question, like, ‘I’m going to a wedding. What flower goes well with a tuxedo?’ Does an AI “care” how you respond to it? Of course not — it reflects the patterns it’s trained on. Yet our interaction shapes how these tools evolve, and that influence is something we should take seriously. Most of us have all expressed frustration when an AI “hallucinates”. Real or not, the larger issue is that we have hi...

I’m Supposed to Know

https://programmingzen.com/im-supposed-to-know/ Great post for developers who are struggling with unrealistic expectations of what they should know and what they shouldn't. Thirty-forty years ago, it was possible to know a lot about a certain environment - that environment was MS-DOS (for non Mac/UNIX systems). . There was pretty much only a handful of ways to get things going. Enter networking. That added a new wrinkle to how systems worked. Networks back then were finicky. One of my first jobs was working on a 3COM + LAN and it then migrated to LAN Manager. Enter Windows or the graphical user interface. The best depiction of the complexity Windows (OS/2, Windows NT, etc) introduced that I recall was by Charles Petzold (if memory serves) at a local user group meeting. He invited a bunch of people on the stage and then acted as the Windows "Colonel", a nice play on kernel. Each person had a role but to complete their job they always had to pass things back to h...