ianmarcinkowski

What if the "inflection point" is just all of the low-hanging fruit that can be detected by agentic vulnerability scanning? If the low-hanging CVEs get patched we might not see a tsunami.

The CEO sounds like .. a loser. :) I'm kidding! He sounds very smart!

If the company isn't going to hit revenue targets they might actually need to fire people and this can be a good way to provide cover that devs aren't meeting requirements so they can be fired with cause.

A past company CEO sounded very similar to this internally before they fired 30% of the staff because they didn't have enough money.

My current vibe reading on CEOs who think every job can be done with AI today is the athlete who starts celebrating before crossing the finish line, to be passed bysomeone who takes the win. My guys, it's not that good yet!

Most of the effort I put into writing is modeling the reader's mind. I never would have known this if someone hadn't invented a soulless writing machine that faked this process!

We had a funny chat at work. Two of us were light-heartedly joking about how you never paste the AI at people.

A third team mate uses a voice dictation tool to get down the basic ideas and then massages it with AI, but these two guys rib each other about it.

Another my other team mates (team mate 4 in this story) sheepishly turns around and asks if people can tell when he does it? (It's EXTREMELY OBVIOUS that he isn't writing anything) I confirmed it, in a friendly way. He defensively said he tries to get the AI to use his own voice.

I casually mentioned that "writing is thinking" or something like that and how I would prefer to think the thoughts. He didn't say much.

I hate AI writing. So much.

Once everyone is using these tools, the rat race will have caught up and we'll have no choice but to race with the other rats. The punishment will resume.

Back in my early 20s starting a company with friends we had boom and bust cycles, and our boom cycles were so extreme that we would work 100+ hours for 3-6 weeks at a time, towards the climax of that given cycle.

We didn't do drugs other than redbull and some of the other guys smoked tobacco. I am really glad there wasn't a hustle culture of taking amphetamines.

My teammate insists that prompt and "context" engineering solve this. You just have to tell the agent "don't make any mistakes" and "keep it simple" and "don't add fixes on top of already broken code"

Wild! I don't actually do a lot of gaming, but the idea of having a small android device running desktop linux is what I've wanted for a long time!

Everyone can easily identify when people they don't like are captured in bubbles, but can rarely notice it when people they do like are trapped.

Probably all hot-button topics work like this. Probably we should downplay any time a small homogenous group of people sings a song of doom together. More dissonance please!

Basically how I feel, but I use the low-powered API models like Sonnet. I feel more energized and focused on the bigger picture than getting stuck on stupid implementation of micro-problems.

I think the muscle memory of doing those tiny problems is good for our minds, but solving larger-scale issues is also challenging.

I'm on vacation right now and getting claude to build a mostly-throwaway e2e testing harness (admittedly not small-prompt-review-repeat) for a backend API to speed up our existing e2e test suites which do click-ops to set up tests 8-10 years ago, we had a team who spent 3-4 months every year maintaining our E2E suite and people would do rotations on there to spread the knowledge.

I basically want an industry standard practice implemented on my team of 4 devs who are too busy doing other things.

I would pay a few actors (mostly Star Trek TNG cast) money for a license to their voice.

I don't know how the next generation of beloved actors comes about and how we don't descend into a pit of neverending photocopies of things people once loved in the 1990s/2000s.

The AI-maximalist on my team does a lot of work to setup fancy loops and burn tokens like crazy. It feels a lot like guitar players who get all these fancy pedals and forget that they can plug a nice guitar into a nice amp and it actually sounds better.

I guess that is taste?

I'm also stubborn. I clone multiple copies of the repo. I'm currently at two at my job right now, because I was trying to vibe-code an E2E test suite.

I'm probably missing something that people see as a huge advantage of having multiple streams of work large enough to require a long-running branch. I just finish working on the current branch and then switching to another branch. If work can't be accomplished and merged into `main` within a small amount of time, I'm almost certainly doing something wrong.

My ai-maximalist coworker spent a day last week getting Claude setup with work trees. He asked me how I did it and I said "I just clone the repo a second time and run claude's CLI in a new terminal window."

His mind was blown that there was .... a simple way ........ to ..... do this...?

Is there a personality type that's like "i will invent a new way of not needing to use my hands to drink soup directly from the hot pot on the stove!!!" ... "you mean a spoon?" .... "yes.... a spoon... how quaint!"