fitnessrunner

As a 42-year old who has been at this 20 years or so... and who got into tech back in the early 2000s for the love of computer science, I keep thinking to myself... maybe I could become a:

* Physical therapist (5+ years of training)

* Nurse (5+ years of training)

* Pharmacist (Out of the picture at this point)

* Plumber (5+ years of training (to actually get to a point

* where I would be pulling in good money))

* Electrician (same)

* Carpenter (same)

Or... continue to languish here. It really sucks right now. I've been doing 9x9x6 for the past several months because my company fired most of the US staff and are left with a skeleton contingent picking up the pieces, and of course now everything is on fire and everything is an emergency. Lunch meetings, 7AM, 9PM, weekend meetings aren't even blinked at in terms of being abnormal.

I can't stand AI and what it has "done" for society.

:-(

Not only that, but even if I *do* know about it, I still won't want to use it. I already know the old mainstream thing. 10% efficiency gains isn't enough for me to invest my limited time in learning a new tool, platform, data model, etc. 70%, 80%? Maybe then, but I'd still be suspicious.

What usually does cause me to adopt something new is 2+ co-worker / colleague recommendations. For example, I would never have started using k9s until 2+ colleagues started to hound me to stop typing out kubectl commands and to switch to k9s ASAP.

These are very wise words that I needed to hear today; thank you.

Thanks - I've been starting to work through this book. I see you are in programming / software engineering - would you say that working through it helped you in your engineering skills (not necessarily day-day, but perhaps your ability to reason about problems)?

Have you read it? I recently purchased a copy, and the exercises look fun/useful.

This isn't just Adobe. Unity3d does this too. While I like the Unity product, I was trialing others too (Unreal) and didn't realize I was being locked into an annual contract. They don't even have an early cancellation fee; you are on the hook for the entire year, no way around it. Be careful.

Wanted to clarify on this, as my comment may have come across as antagonistic... I think what they are trying to do is a good idea and has promise. That said, I stand by my statement - there are no shortcusts - so I would market it differently. Rather than say "Learn Software Engineering 30x Faster..." change it to something like, "An Alternative Resource to Software Engineering via a Visual Approach," or something like that. It is the "30x faster" that didn't sit well with me.

No. Designing products, architecting systems, writing code, testing code, documenting systems and releasing and maintaining software all takes time and most importantly, dedicated practice.

There are no shortcuts with learning computer science, similar to how there are no shortcuts learning piano, drawing, organic chemistry, etc.

Type 1 for 30ish years... I wish there was some way to move this comment to the top of this thread. You pretty much hit the nail on the head. Yeah, injections suck, but the real sinister issue is the constant attention it requires, and if you don't pay attention, you can get in trouble (hospital, death) real fast. Longer term, lose limbs, eyesight, etc.

I've done on-call in a fairly severe fashion, similar to a lot of folks here - one one night, off the next, one one, off the next. I didn't get compensated for it. It took a tremendous toll on my mental and physical health. Fixing issues at 2AM is something you have to experience for yourself before you have any clout passing judgement on whether "everyone should do on call".

The interesting thing is that the majority of issues that came up were not necessarily bugs per-say, but rather, the hundreds of input sources our app consumed (algorithmic trading) frequently had bad data, so it was always a scramble to add fixes and stay on top of it, till the next bad input stream came in. It never ends!

I'm not sure if I've seen it proposed yet, but a better strategy IMHO is to have folks be "on call" while they are at the office. Then rotate to the next global office when they leave. If devs want to stay and go above and beyond, great. If your company needs to be 24/7, you need to staff it properly 24/7. Or be very upfront about the sleep deprivation requirements when hiring for it.