HN user

kaidon

197 karma
Posts0
Comments70
View on HN
No posts found.

Just lost my father to pancreatic cancer as well a couple weeks ago. They caught it very early with a CT scan, performed a significant surgery followed by radiation and chemo. The chemo nearly killed him. Had a couple ok months after chemo, but then it spread and the last couple weeks were awful. Even catching this stupid cancer really early often isn't enough - I hate it.

practically nothing more injurious to good technique and nothing more likely to induce tension than this.

Oh my goodness yes. I started playing on January and followed the Hanon instructions with the sheets. I have been trying to release tension, especially around my flying pinky… and realized that this way of playing Hanon was making it worse. I am in the process of fixing this now, and am enjoying less tension.

About 35 years ago. Found a commodore PET in the trash along the roadside. It came with a tape drive and a book of games written in BASIC. I took it home, tidied it up and then started learning from the book.

The TIE Fighter animated intro sequence is forever etched into my memory. I watched the whole thing at least 50% of the times I fired up the game before playing. What an absolute beast of a game. Plus the dynamic music (iMuse) was just so damn cool. With LucasArts, you always knew you were going to have an amazing ~game~ experience.

I have felt very much like this in the past, but no so much any more. .. my thinking is:

Some things are just part of the responsibility of being a grown up. Home maintenance, driver for children, doing taxes, etc. These are your baseline priorities that you don't get to choose.

Some of these sound like they occupy a rotating priority slot. House and car purchases do take a big commitment and require prioritization (especially if you build) but they are temporarily a priority. It is usually your choice to make these a priority, and they are rare.

Keeping a smaller priority list means saying 'no' to more things too, like being 'tech support geek for wifi and computer issues' or vehicle maintenance. These priorities are fully under your control.

What an interesting concept! The Generalist and Backend roles sound interesting to me.

I have 20+ yrs experience as a polygot developing products from IDE integration, cybersecurity, economics, project planning, market analysis and more.

I know applications can get lost easily in the shuffle these days, with high volume of candidates applying. Is there any way to get a specific resume noticed?

Keycloak is fairly easy to maintain. I run a deploy in AWS/ECS, and nearly never needs to be touched... except when an upgrade is required. Every upgrade has been challenging, starting with change to Quarkus, followed by removing dependencies from the docker images.

But when it's not being upgrade, it's fantastic. Many thanks to Red Hat.

Are you me? I agree and have experienced every single thing here.

I believe that it is a mistake to believe that merely working harder will earn that respect.

<bingo>

You must be a principal level developer -- it is a role driven with the highest degree of cynicism and empathy, which you comment is gushing with.

deteriorate productivity in ways that will be difficult to understand

Exactly! This can be very difficult to quantify; as this kind of debt is undetectable by standard gates (linter, static analysis, etc.). Instead, it is more nefarious... introducing coupling, where none was needed, or long-winded tests; that test very little, and make the code hard to refactor. I don't have a measure for this beyond my intuition of working with code for decades.

What makes it all worse, is when the features are 'delivered' and marked as 'complete' by these folks, they are difficult to take back! Especially if their delivery was identified as a key objective to a quarter.

Absolutely. On a small team, we had 2 underperforming devs.

One was doing absolutely nothing at all for months on end.

One was doing negative work - every line of code made things worse, every document was unintelligible, and they would approve every PR from other devs the second it was opened.

Suffice it to say, the dev that did nothing at all was the most productive of the two.

Aging programmer 4 years ago

"they person that can't let the smallest mistake go un-punished"

Did you mean 'the' instead of 'they'? Did you do this on porpoise?

jsonapi solves some problems, and introduces so many more. As a standard intended to reduce bike shedding, I have never had as many bike-shedding discussions as I have with jsonapi. Include syntax, plural vs single resource naming. sorting syntax... the list goes on. And worst of all... you cannot represent an API backed by jsonapi with swagger/openapi... a more common standard.

If you want jsonapi, you probably really want graphql...

laying off anyone

Laying off 23% of staff is _literally_ how he will make the stock go up enough to get a good % of his compensation, if not 100%.