duttish
duttish on Hacker News
Hm. To me there's a difference between handling the bus factor: make sure several people on the team knows about things, and fungible engineers: can move engineers between products.
To semi-quote a higher up at $dayJob, at BigTech, talking to his directors: "If your engineers aren't fungible you're bad at your jobs".
Everyone should just be a small cog in a big machine.
I like it :) Could you make the channel icon/text clickable into a filter for videos from that channel?
We got those giant books here too.
Around me everything is at least hybrid, with nobody complaining if you want full time on-site. More and more companies are moving back to on-site full time.
50% office politics
30% stakeholder and expectations management
10% design/development
30% is surprising, did you dig into it at all? Sounds like a bunch of active polling or something?
They mentioned this on the podcast, the problem is that since they're development tools the networking stack is still scaled for a full rack with pretty beefy switches.
Either they need to support a whole second network stack with firmware etc which they don't want to do now, or a racklette would cost way too much and almost nobody would pay the price.
Hm, that doesn't make sense to me.
The difference between intent and implementation seems like a very common source of bugs?
If intent and implementation was the same thing programmers as a profession would have been left behind 20 years ago.
"Hi, this is AWS Support. Your backup disk usage is over limit. Please remove all backups or we'll need to close your account.
Feel free to reach out if you have any questions."
Hm, what guard rails are needed for agents that aren't needed for humans if you want to handle insider risk properly?
Yea this.
Agents doesn't cause new problems, they reveal existing weaknesses.
Proper working backups. Proper IAM setup. With agents things can go wrong so much faster, the margins for allowed systemic/tech debt are shrinking.
This has become my approach as well. Create a work tree per larger thing / batch of things and manually review everything in small commits, then squash merge the whole tree to keep the history manageable and clean.
Every time I stop reviewing the code from Claude I later find janky crap. Not every review finds janky crap, but often enough that I can't stop reviewing everything.
This is my disconnect with this kind of speed, how are they avoiding the janky crap? Or are they just accepting it and hoping it won't be too crappy or be found soon enough?
I don't have any insight into Anthropic but it seems like that's the case which is just depressing.
I have no clue where the author is working but...
We've lost 75% of the team over the last year.
We write code faster. It's not getting merged faster because we usually find something janky.
Decisions aren't made faster.
Understanding doesn't come faster.
Code doesn't have value. A well working system has value, the bottleneck is now between having code and having a working system, rather than producing the code.
Whenever I've tried skipping code review I've later found janky crap or weird decisions made.
Agents allow me to build cool stuff but atm they're far from good enough to not review the code.
Whenever I stop reviewing code I later find yanky shit or a small but important misunderstanding in the plan or...
Claude has let me build really cool things but so far I'm not letting it run on it's own.
Those people are what "Unfollow <name>" under the 3 dots on the posts are for.
I actually see posts from maybe 5-10% of my connections on LI, one strike for being boring or bland or performative and they're out of my feed.
Iirc he was one of the founders :)
I've been a happy customer of Tresorit for several years now. Give them a try if you're fed up with Dropbox.
At first I was selective in what folders I synced but after a few months I decided to just sync my entire workspace folder with everything in it.
Incredibly convenient, everything is automatically synced between my desktop and laptop.
If you go this route look into filters, it's not a very advertised feature but works great for excluding build output, venvs and other stuff.
I've never looked into LSP, how would you design it?
Oh wow, I didn't know it had things like that.
Especially the CPU functionality is really interesting. I'm pondering similar problems and the current solutions just aren't good enough.
I don't quite know why but something in the realisation that something is made with AI removes all the joy from reading/listening to/viewing/watching it. It was interesting reading your take on it, I'm not sure it's why I don't like it but I also don't have a better explanation.
It's not about skill either, I'm quite sure I'd react the same if AI writing surpassed Hemingway, it's still not art.
Do you mean $8-12 per day? Otherwise I'm confused how it's cheaper.
OPs post made me curious about jumping in, how often do they release updates? If I'm going to wait for this and the next one.
I built a product on Cognito in 2017-18 or when it was, and already back then it felt semi-abandonded. Thankfully that particular product never really took off and we didn't have to spend too much time on wrangling Cognito.
It's been working quite well so far and I don't know of any way of hooking custom linters into cargo so they run after compilation.
But that's a pretty good idea, wonder if there is a way...
The cost of custom linters has like any other code dropped through the floor. I'm sprinkling all kinds of linters over my latest projects. It seems some people are still sleeping on this, expecting great code from the agents.
They're fast and deterministic and I run them in git pre-commit.
It seems they're conflating two different risks? Read-only connection is a solution to Integrity risk, while they straight away start talking about Confidentiality risk instead.
They're also problematic, but different kinds of problematic and I don't see how this is different from managing employees database access.
Then there's no mention of handling Availability risk management. An employee or agent querying the entire order table joined with... and the entire db cluster is choked for two hours.