comprev

AI allows juniors to magically fix the mistakes or suggest an alternative solution without needing to _think_ themselves. It will cook up a script in seconds to approach the problem from a completely different angle.

I only use AI when I'm really stuck on something and enjoy learning new ways I had never even thought of before. This provides me another avenue to explore before asking AI to help again.

If they were serious about aiming for "carbon neutral" the plane would never take off in the first place!

I admit this is a very simplistic view and likely I just don't understand the bigger picture about economics of carbon offsetting.

Many moons ago I was a sysadmin at a company and first heard about their licensing strategy when sizing up some new multi-socket Opteron servers. First time I learned about per-CPU licensing.

Look at the construction industry. Many buildings on this planet were built hundreds, sometimes a thousand or more years ago. They still stand today as the quality of their build quality was excellent.

A house built today of cheap materials (i.e poor quality software engineers) as quickly as possible (i.e urgent business timelines) will fall apart in 30 years while older properties will continue to stand tall long after the "modern" house has crumbled.

These days software is often about being first to market with quality (and cough security) being a distant second priority.

However occasionally software does emerge as high quality and becomes a foundation for further software. Take Linux, FreeBSD and curl as examples of this. Their quality control is very high priority and time has proven this to be beneficial - for every user.

Ironically, the same thing will happen in future Israeli generations when they look back at the current genocide - "No, my grandfather wasn't involved in the Gaza war"

Perhaps Israel could take a radically different path and aim to call their neighbours "friends" instead, or at minimum a healthy but neutral relationship?

Only a small number of bordering countries worldwide are sworn enemies and the world would be a better place for everyone if this fell to zero.

There will always be someone willing to do the work if the pay is good enough.

STOOR did a live multi-artist techno performance between two studios in Netherlands and Germany.

They might have used something like JackTrip to synchronise their instruments.

At $DAY_JOB we need approvals from peers due to industry regulation.

Anybody can build a pipeline to get a task done (thousands of quick & shallow howto blog posts) but doing this efficiently so it becomes a flywheel rather than a blocker for teams is the hard part.

Not just caching but optimising job execution order and downstream dependencies too.

The faster it fails, the faster the developer feedback, and the faster a fix can be introduced.

I quite enjoy the work and always learning new techniques to squeeze extra performance or save time.

When possible I'll ask to be either continue to be involved or kept in the loop until a solution is found.

By reaching these boundaries at work it provides me avenues of exploration in personal time to understand where my knowledge gaps are - and quite often find new interesting subjects along the journey.

She could read eBooks & emails, listen to audio books, view photos and call her family by herself (iPhone use extends to many uncles/aunties/cousins).

Every few months I would help her recalibrate her iPad as it was a vital life line.

I've been in Ops for 20+ years now and started on 1st line support for an ISP, although I had very few options without a degree (or much of an academic background really).

An entry level role might be a stepping stone to other positions within the company - and an opportunity to network with colleagues in other departments.

Over the years I built professional relationships and moved up to 2nd line and then 3rd line (sysadmin). This provided industry experience, certifications and sufficient domain knowledge to move elsewhere.

A few peers from 1st line moved over to development after they helped provide direct feedback to the devs as users of their software.

The vast knowledge in the collective HN community never fails to amaze me.

They had only used cheap plastic or laptop keyboards until then and never saw a keyboard as a tool to invest in for their profession (which often required plenty of typing).

Most devs are probably in the top 20-30% band making tech a relatively "normal" (but good) salary in the local region.

I could be entirely wrong though :)

Only now are their roles morphing to include programming and, understandably, it's occasionally a daunting steep learning curve for them.

I enjoy researching, building and solving interesting problems out of personal curiosity. There has never been any pressure on me to find a solution - many of the challenges are sometimes years old and teams just lived with the discomfort.

Sharing a possible way to remove this discomfort is often welcomed by the long-timer engineers out of curiosity to learn more - it's been a thorn in their side for ages!

This of course all relative geographically but we're certainly very well compensated compared to other industries.

A surprising number of Ops colleagues have almost zero exposure to IaC and the short-lived certificates on the horizon has been the necessary catalyst to change this.