Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
bmurphy1976
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
61.
▲
by
bmurphy1976
6mo ago
There's another piece of the puzzle. Dario has very clearly stated they are not taking the OpenAI approach of spending $trillion to scale right now and assume the money comes later. They are spending significantly less and working to
62.
▲
by
bmurphy1976
6mo ago
I'm a director and one of our teams just spent 8 months doing just that and it was totally justified. They're finally coming up for air and the foundation is significantly improved. There's nuance here. Every project/te
63.
▲
by
bmurphy1976
7mo ago
You kind of missed my point but that's OK. You can agree with or disagree with the action OP took, I'm not making a judgement call on that. What I'm responding to the the notion that "no action you can take matters.&quo
64.
▲
by
bmurphy1976
7mo ago
Eh, it has an impact. It's not always obvious but it adds up over time. Use your analogy of choice: slowly building up pressure until it boils over or a small pebble starting an avalanche or whatever works for you. I don't neces
65.
▲
by
bmurphy1976
7mo ago
Hell, the tech savvy senior lawyers are already using LLMs to do the work that army's of juniors and other assistants did for them. Just like what is happening with software engineers. Anybody who thinks this isn't going to have
66.
▲
by
bmurphy1976
7mo ago
I worked briefly with an idvidual who had this extreme bureaucratic mentality. I just can't even imagine how you can talk to another person and have no empathy at all for their situation and only care about the process. I also know p
67.
▲
by
bmurphy1976
7mo ago
For now. They're about to get hit by the AI wave as bad as us software devs. Who knows what's on the other side of this.
68.
▲
by
bmurphy1976
7mo ago
I've forced myself to git gud with FreeCAD. It's better. Way better than it used to be. It's also still a very complex and user unfriendly application with a long road ahead of it. You can make it work. You can also save your
69.
▲
by
bmurphy1976
7mo ago
Can't upvote you enough. This is the way. You aren't vibe coding slop you have built an engineering process that works even if the tools aren't always reliable. This is the same way you build out a functioning and highly ef
70.
▲
by
bmurphy1976
7mo ago
Which is fine and all but repos with such sparse README's are not doing themselves any favors.
71.
▲
by
bmurphy1976
7mo ago
Agreed but that's also a documentation problem. Every time I have to make a tricky decision that I know will trip me up later or some kind of compromise, I now ask the AI to document it and the reasons why. That information has defin
72.
▲
by
bmurphy1976
7mo ago
See my other comment. Logs are just one small symptom of a larger problem of poorly integrated very complex services where the complexity is pushed onto the users and not properly managed by Amazon. Which sounds very much like the problems
73.
▲
by
bmurphy1976
7mo ago
That's great but that's not really the problem. The real problem is Amazon likes to release services that depend on other services, but leave the integration work to us. I'm convinced Amazon has many teams crapping out new fe
74.
▲
by
bmurphy1976
7mo ago
How is this different than Amazon? Same problem there. Oh, you're using this new service? Need to view the logs? Want a nice friendly UI to do that? Fuck you here's Cloudwatch. Good luck. Just to be clear, I'm respondin
75.
▲
by
bmurphy1976
7mo ago
That's kind of the point. These things don't just happen, people start talking about it at a high level (this doc, conversations like this) and then dig in and solve the problems over time.
76.
▲
by
bmurphy1976
7mo ago
Sigh. Nobody is ever going to be happy. Would saying it came from a rando Reddit user be better? They at least put the effort into having the retreat and putting this together. Would other consultancies (who we know little about) have of
77.
▲
by
bmurphy1976
7mo ago
@dang this is a very interesting and relevant doc. I think it needs another chance at making it to the front page. This is a fairly easy to read doc discussing some of the challenges with using AI tooling in a forward thinking and discipli
78.
▲
by
bmurphy1976
7mo ago
This. I only ask LLMs to summarize non-critical stuff, i.e. just give me a general summary of all the work done over the past week. If I were in need of hard analytics you can be damn sure I'd have it build a tool with a solid suite o
79.
▲
by
bmurphy1976
7mo ago
Well, things are changing so fast those studies are going to be out of date. And I have no doubt some people are experiencing a net loss while others are not. We need to pry apart why some people are having success with it and others aren
80.
▲
by
bmurphy1976
7mo ago
> Now corporate has mandated AI usage and is asking people to do 10k LOC PRs every day. That's a big red flag if I ever saw one. Corporate should be empowering the engineering team to use AI tooling to improve their own process orga
81.
▲
by
bmurphy1976
7mo ago
Agreed, but I find that astro-turfing far more obvious.
82.
▲
by
bmurphy1976
7mo ago
I can't speak to your experience. I can only speak to mine. We've spent years reducing old debt and modernizing our application and processes. The places where we've made that investment are where we are currently seeing th
83.
▲
by
bmurphy1976
7mo ago
I can't speak for you specifically, it's just a trend I'm seeing and unfortunately your 2 day old account falls into that bucket. There's a lot of people who have a lot to lose or who are very afraid of what LLMs will d
84.
▲
by
bmurphy1976
7mo ago
I don't know what to think about comments like this. So many of them come from accounts that are days or at most weeks old. I don't know if this is astroturfing, or you really are just a new account and this is your experience. As
85.
▲
by
bmurphy1976
7mo ago
This is how all software projects play out. The difference is when it's people we call it tech debt or bad desing and then start a project to refactor. Apparently LLMs break some devs brains though. Because it's not one shot perfe
86.
▲
by
bmurphy1976
7mo ago
Good thinking. That seems to have worked. I'll have to use it in anger to see how well it holds up but so far it's working! First Edit: it works for the CLI but may not be working for the VS Code plugin. Second Edit: I asked Cla
87.
▲
by
bmurphy1976
7mo ago
That's a good suggestion. I'll try it next time. That said, it's really easy to start small things in planning mode and it's still an annoyance for them. This feels like a workflow that should be native.
88.
▲
by
bmurphy1976
7mo ago
This drives me crazy. This is seriously my #1 complaint with Claude. I spend a LOT of time in planning mode. Sometimes hours with multiple iterations. I've had plans take multiple days to define. Asking me every time if I want to a
89.
▲
by
bmurphy1976
7mo ago
This is interesting. I'd be curious to see a bunch more working examples. Personally I like the chat model because I iterate heavily on planning specs and have a lot of back and forth before implementation. I could see using this onc
90.
▲
by
bmurphy1976
7mo ago
Everyone is NOT making that tradeoff. Maybe we will be forced into it someday, but my team is leveraging AI to increase the quality of code far beyond what we would have done without it. Some of us are using it to engineer better solution
More ›