HN user

bad_username

954 karma
Posts1
Comments379
View on HN

Microservices solve a real problem too, and it is mostly organisational rather than technical. When you have enough engineers that they are stepping on each other in one codebase, and enough teams that release schedules collide, splitting the system along team boundaries buys independence.

grug wonder why big brain take hardest problem, factoring system correctly, and introduce network call too

seem very confusing to grug

Most new product launches are an exercise in figuring out what the product requirements should be through trial and error

Sure, but these have to be well-defined trials. In other words, yes, you will test several hypotheses, but your hypotheses have to be hypotheses, not hand waving.

Yes the code (sorta) writes itself, but the human reviewing, directing, and course-correcting feels worse, not better.

I noticed the opposite. When reviewing and directing a colleague or subordinate, I spend probably 30% of my brain cycles, and 70% of my activation energy, to weigh the technical merit of my feedback against the human impact it will make: bruised egos, differing architectural convictions, correct and polite tone of comments, additional workload for the colleague. The dread of potentially seeing that the code is not good at all, and needing to decide _what to do in that situatuon_, trading off technical debt in the future vs team dynamics and psychological impact right now.

LLM does not care about any of that. It is so much easier.

Tech companies possess immense resources and huge potential to shape public discourse. Activists (that often includes journalists today) wish to exert power over tech companies for that reason. In the era of social media, weaponized complaining and astroturfed rage/hate is a very effective method of exerting actual power and inluence. When you see sentences like "Why do people hate X?", understand that this may be a statement pursuing a goal (we need you to believe that people hate X, so you should too), not a genuine quesion.

I am not a fan of tech companies _at all_, BTW. But the enemy of an enemy is not always a friend.

In the culture of automation, we wiggle and iterate among four overlapping phases: (1) document the steps; (2) create automation equivalents; (3) create automation; and (4) create self-service and autonomous systems.

Notably missing is the most important, difficult and time-consuming (thus potentially defeating the whole purpose) phase: _maintain_ automation. The code will break, it will make incorrect assumptions, it will fail in rare edge cases, it will have unintended side effects, people will use it wrong, etc. "It works right here right now" is like 10% of the whole journey.

Not only maintenance of automation can cause more work than it saves. It has the potential to cause unpredictable, burst-like work in the worst possible times (for the maintainer or the users), which is a problem in itself. A steady background level of predictable, simple manual workload may be preferable to sudden bursts of complex troubleshooting.

I do not say "never automate", I say "life has a surprising amount of detail" so be smart about when to automate.

Between the Apple Watch kind of watches on one side, and Pebble kind of watches on another side, there's the whole Garmin ecosystem, a mention of which is notably absent from the article. They are a nice technological middle ground (though maybe not always a price middle ground), especially the classic models with non-OLED transflective screens. Granted, they are more sports/fitness oriented, but that's hardly a drawback honestly.

The debate between these who don't squash and these who do is the debate between these who use the history for bugfixing and those who don't. And I think not using it is throwing away a super valuable tool that can reduce the fix ETA by an order of magnitude.

I was uncomfortable with git until I read (the first 3 chapters of) the pro git book ( free here : https://git-scm.com/book/en/v2 ). It provides a great mental model of how git works under the hood. The UI of git - for better or worse - directly reflects its internals. And when I understood them, everything clicked into place.

I think Anubis is meant to stop dumb automated hyperscale scraping bots, not smart singular human-driven AI agents.

that support the agenda of the current ruling party and failing to include any counterarguments

This is what's going on, with varying intensity, with social media algorithms.

Moreover, they capture all the smalltalk perfectly, but tend to plausibly mishear the parts that matter most - terminology, abbreviations, names of people. There's no mystery why this happens, of course, but the only transcript I trust is a transcript I personally checked by listening to the audio and fixing mistakes (doable at 1.75x speed, so not that bad). I catch outrageous mistakes sometimes, mistakes that completely change the meaning of what's being said (up to capturing the opposite of what's being said). So, all in all, even though modern speech2text models are really impressive, I am not sure the utility of _completely_ automated transcribers outweighs their dangers today.

The speed of air exchange through openings in your room (windows, gaps etc) is proportional to the difference of temperature between your room and outside. The more different the temperatures are, the more intensive convection is, and convection is very effective at moving/exchanging air. In summer the difference in temperatures of your room and the outdoor space is much smaller than in winter, which subdues convection, and the stale air tends to stay.

Just some recent case studies.

1) A stakeholder voiced a wish 1 year ago that I forgot about because it was far fetched and not my area. It went to die in a transcript. Today the AI found and resurfaced it in a context where it was actionable and I was in a position to implement it. I did not ask AI to dig it out specifically, like I said, I did not even remember about it, but it just brought it up. Stakeholder ecstatic.

2) I was able to recreate a huge piece of enterprise architecture without access to docs - from 20 meeting transcripts of people just blathering about other topics. From bits and pieces - word here, sentence there - the AI pieced together the big picture for me. Unfeasible manually, especially because the LLM used its training data to infer things that I wouldn't be able to infer myself.

3) I was added to a project as a consulting/observing party, did not pay MUCH attention, but recorded meetings just in case. Suddenly, plans change, and I end up in charge of the project architecture. Nobody bothered to keep any serious records. I throw transcripts, along with emails and chats, into a context window, and I get an excellent self-onboarding doc. I am ready to talk to clients competently next morning.

4) a vendor is failing us, meeting after meeting they defer, delay, gaslight, pretend to forget or misunderstand or not to have heard what they'd been told. I need to escalate, boss asks "give me details to work with". I throw in the transcripts, and in 1 minute I get the timeline of what was going on, with references. Re-tracing this manually would be hopeless.

5) I can talk to a person and ask their opinion virtually, by loading a corpus of meeting transcripts into AI and asking to pretend it's that person. Having 100k tokens of transcripts allows for a pretty high fidelity replica of that colleague!

what are you gonna do with all those notes?

Dump them in Obsidian with an LLM agent bolted on. This note may never be consciously re-read, but it will become silent part of the context for conversations with the agent in the future. It is _ridiculous_ how useful this approach is.

That pertains to work meetings, though. I would never bring a recorder to a coffee shop.

Ever wondered what NPR's code of journalistic ethics involves for the newsroom?

I have been thinking a lot through the years about the choice between joirnalistic ethics and journalistic activism in the ranks of organizations like NPR. This is an extremely important topic because today's media are as impactful politically as the "regular" political process.

My point is, such discussion would not make me sleepy, the opposite would happen.

People who like squirrels should get degus. Degus are not propely squirrels, but close cousins, and they are brilliant pets. Their intelligence is outstanding.

Honestly to me it seems that the objectively unprecedented migration levels in the UK of the last decade (caused explicitly by government policy) are better suited to be called "extreme" or "far" than the demands to roll them back