sockgrant

7 ms·

1.
by sockgrant 5mo ago
LLM evals are well established, are these not applicable here?
2.
by sockgrant 6mo ago
if you work on platforms, frameworks, tools that are public knowledge, then yeah. If there’s nothing unique to your project or how to write code in it, build it, deploy it, operate it, yeah. But for some projects there will be things Claude
3.
by sockgrant 6mo ago
The only way Claude can help improve your code cleanliness is if you write poor code? Code coverage means nothing if you didn't carefully check every test? "and if everything was tested" do you know what code coverage is? not
4.
by sockgrant 6mo ago
Heck yeah! Love that way of putting it. Agree. Now there’s more time to focus on making the right architecture and carrying it out. It’s no longer a days long task to do a big refactor to remove code smells.
5.
by sockgrant 6mo ago
I agree some people go to work to work, and claude is find / good for them, but I feel that characterization of us who are loving claude is disingenuous. I’m a creative, while I loved coding and honed my craft, it was creating that alw
6.
by sockgrant 10mo ago
“As a designer…” IMHO the bleeding edge of what’s working well with LLMs is within software engineering because we’re building for ourselves, first. Claude code is incredible. Where I work, there are an incredible number of custom agents th
7.
by sockgrant 3y ago
It’s also a description of why native wasn’t chosen from the get go. This thread is people who ship products vs people who ship engineering.
8.
by sockgrant 3y ago
The companies do pay a cost — lost users and revenue due to the downsides. But they’ve determined that this cost isn’t meaningful enough to write performant native platform specific versions.
9.
by sockgrant 3y ago
Yeah but if something stays in Electron 10 years later then either it’s not successful enough to warrant the cost of a rewrite or the payoff of the rewrite isn’t a good trade off. In both cases if originally building in Electron was a subst
10.
by sockgrant 3y ago
Gotta love engineers. 45 minutes of reading 12 years of someone’s work and the first thing they say is “yeah I’d rewrite it”. Every. Dang. Engineer. It’s crazy. I try to work in a codebase for 3-6 months before coming to any wild conclusion
11.
by sockgrant 4y ago
Was on a team this happened on and a lot of the l4 l5 Eng gossiped about how little our L7 knew
12.
by sockgrant 4y ago
I don’t agree because not all interviews work that way, especially for teams that write cpp and c — they don’t let candidates interview in JS for instance. I had a high level eng join a domain specific team I was on and he didn’t do well be
13.
by sockgrant 4y ago
You get massive DoS attacks pretty regularly? State sponsored hackers?
14.
by sockgrant 5y ago
While I see your point, a lot of invention happened when someone ignored conventional wisdom and others’ failures.
15.
by sockgrant 5y ago
Got any links to reading on this? You piqued my interest. > Personally, I find his thinking savagely brutally straight to the point and cuts through cultural rust we've built up in our thinking process.
16.
by sockgrant 5y ago
I believe there are good losers who are winners, but Brady is not a good loser.
17.
by sockgrant 5y ago
Facebook and Google don’t expect 80 weeks and they do leet code interviews. I’d think most people do 40 hour weeks there.
18.
by sockgrant 5y ago
There’s probably better code writing interviews to be conducted, but I think writing code in an interview is important. I’ve conducted many interviews in C where the candidate has years of C but doesn’t know the stack from the heap. So I du
19.
by sockgrant 5y ago
Yeah FAANG have those type of interviews too.
20.
by sockgrant 5y ago
Spoiler: it’s not top tier.
21.
by sockgrant 5y ago
What’s the pay for someone with 10-15 years experience and is “the best people”?
22.
by sockgrant 5y ago
Hi, I’ve worked for two of FAANG, it’s super duper easy to work outside of SV. The reason you sound salty is because you evaluate candidates based on whatever perception you have about who they are instead of trying to understand who they a
23.
by sockgrant 5y ago
If you’re struggling I don’t think you should try to memorize leet code problems, you should try to understand how to apply algorithms.
24.
by sockgrant 5y ago
High wages won’t impact a housing market with infinite supply but that’s not reality. When there’s a lack of supply then the top earners set the market. When top earners make more then prices are higher.
25.
by sockgrant 5y ago
Would a housing supply shortage in Mississippi produce equally priced housing as a housing shortage in San Francisco?
26.
by sockgrant 5y ago
I’ve heard plenty of horror stories about someone being hired that couldn’t write simple code. It’s easy to study leet code, and it’s relevant because it shows the interviewer you can write code. I’ve had non-leet code interviews, like writ
27.
by sockgrant 5y ago
They’re both issues contributing to rising housing costs.
28.
by sockgrant 5y ago
I mean there’s two camps. One camp can do them easily or with practice, another camp can’t. The first camp is pretty “meh” about leet code interviews because for them you just study a bit and get a high paying job. The second camp is pretty
29.
by sockgrant 5y ago
Crazy! I was gonna come here to say this reminds me of Total Annihilation. So it sounds like you recommend it? I'll have to check it out!
30.
by sockgrant 6y ago
Good to know but this is pretty small deal, easily fixed, also there's probably quite a few Go backend frameworks and I doubt all of them have this issue

More ›