3,217 karma · joined February 20, 2017
If you need to contact me my e-mail is {{ .FirstName }}@{{ .FirstName}}{{ .LastName }}.org.
[ my public key: https://keybase.io/alexjplant; my proof: https://keybase.io/alexjplant/sigs/muR_HOs5kz4fAIHpvSaBdxGhYFj73TzlOFGL82WlKBQ ]
meet.hn/city/32.7174202,-117.162772/San-Diego
> “Some people doom scroll social media. I've been doom scrolling GitHub issues since before that was a word,” he admitted. “On vacations I'd have bookmarks of different projects on GitHub I wanted to study. Not just source code, but OSS processes, how other maintainers react to difficult situations. Etc. Believe it or not, I like this.”
> “I've been angry about it. I've hurt people's feelings. I've been lashing out. Because GitHub is failing me, every single day, and it is personal. It is irrationally personal,” he wrote.
He is a passionate person whose identity is heavily invested in community and technical achievement. He's upset about his world being disrupted, not that GitHub as a product is failing him. This is how high-performing people are - they care deeply about their work. Could you imagine leveling these charges at a visual artist when they complain about a company messing with their favorite pencil? Or a saxophonist when their reed of choice is discontinued? It's petty and reductionist.
I didn't see a single bike locked up when I visited Japan. I was told that this is because of the high conviction rate and mandatory bike registration process that they have. Was I just in especially low-crime areas? Do most Japanese cyclists lock theirs up?
If you're doing work on a cost-plus-fixed-fee contract (which many software development efforts are) then you have to count hours anyway because you get paid based on what you bill. The fact that nothing substantial gets done in the additional 1-2 hours a day is immaterial because these arrangements are really just fringe benefits in the form of additional time off for employees. As a practical example: people working "9 hour days" with mid-afternoon on-site customer meetings and a half Friday from home certainly aren't fitting 40 hours of productivity into their week and nobody cares - everybody gets paid, the job gets done (for some value thereof), and millions of Americans stay employed. One might even argue that this is a feature since working less efficiently means more billable hours to the government and a larger economy.
> Goodbyes are always hard, especially when I am the one saying goodbye. Today, effective immediately, I, Gavin Belson, founder and CEO of Hooli, am forced to officially say goodbye...to the entire Nucleus division.
> But make no mistake, though they are the ones leaving, it is I who must remain and bear the heavy burden of their failure. It is my fault, I trusted them to get the job done, but that is the price of leadership.
Mike Judge is a masterful satirist.
You are far more likely to get it from undercooked beef or shellfish than from a cat. Less than 1% of cats broadly are shedding it at any given time and that number is even lower for indoor cats. If, like me, you have a penchant for rare steak and beef tartare then there's a decent chance that you have it.
- Not an "Apple Faithful"
[1] VHS vs Beta, Doom vs Marathon, Zergling vs human, etc
At this rate I fully anticipate being able to run a comparable stack on a 128GB Mac Studio using quants of newer-generation distilled OSS models in a year or two. Being able to ramble to a computer for an hour about features and technical philosophy then have it build a nearly-working app for $50 is an exciting feeling. There's still a long tail of productionization and fixing what the model didn't adhere to but it's still incredible.
It should be to the greatest extent possible. Strive to write literate code before writing a comment. Comments should be how and why, not what.
> - ergo: We don't write any comments, ever"
Indeed this does not logically follow. Writing fluent, idiomatic code with real names for symbols and obvious control flow beats writing brain teasers riddled with comments that are necessary because of the difficulty in parsing a 15-line statement with triply-nested closures and single-letter variable names. There's a wide middle ground where comments are leveraged, not made out of necessity.
> Someone once said that SF is a town of extremely high sincerity, and all of its modern and historical weirdness — the AI doomerism, the cults, the hippies, the drug use, the polycules — is downstream of people saying things and other people taking them extremely seriously.
This is a perfectly reasonable usage - perhaps not the Hallmark greeting card one but it's certainly valid.
> the difference between the east coast and the west coast.
Having lived in and visited places on both sides of the US I can safely say that there is no single "difference" between them and that treating both as culturally monolithic (or their constituent places as broadly similar) is a massive category error. Boston is not Miami is not Atlanta just as San Francisco is not San Diego no matter how many people confuse them because they both start with "San".
I think in all cases it's the sheer novelty of doing something with a different ISA and form factor. Having built and racked my share of servers I see no reason to build a miniature datacenter in my home but, hey, to each their own.
I do still write stuff manually frequently - I often spend 5 minutes writing structs or function signatures to make sure that the LLM won't misunderstand or make something up. Maybe that's why I haven't lost it.
I'd like to give the new GLM models a try for personal stuff.
Interestingly enough I can't recall a single instance of a working-class person acting like this in a similar situation. A friendly ribbing and wise crack here and there, sure, but never as seething as somebody who feels like they should be making more than they do because they went to school for this, damnit!
Open two windows, ask it the same thing from starkly opposite perspectives, then see what it comes back with. If nothing else this exercise forces you to think deeply about what you're considering before you even see what the giant blob of matrix multiplication says about your situation.
> if my job was CRUD apps and thats it,
I'm not sure whether you intended this but your post reads as presumptuous and disdainful. The whole point of these tools is to free people from having to do these parts of their job so that they can focus on the ones of greater substance. At no point did I say that was my entire job or that I was afraid of it disappearing - if that was your takeaway then I don't know what to say.
[1] https://en.wikipedia.org/wiki/Automatic_Certificate_Manageme...
I agree but you'd be surprised at how many people will argue against static typing with a straight face. It's happened to me on at least three occasions that I can count and each time the usual suspects were trotted out: "it's quicker", "you should have tests to validate anyhow", "YOLO polymorphism is amazing", "Google writes Python so it's OK", etc.
It must be cultural as it always seems to be a specific subset of Python and ECMAScript devs making these arguments. I'm glad that type hints and Typescript are gaining traction as I fall firmly on the other side of this debate. The proliferation of LLM coding workflows has likely accelerated adoption since types provide such valuable local context to the models.
As an example PHP still powers something like 75% of web sites and I've never once used it professionally. If I didn't know better I might think it dead.
Because it does.
> I still don't see ANY proof that it doesn't generate a total unmaintainable unsecure mess, that since you didn't develop, you don't know how to fix.
I wouldn't know since it's been years since I've tried but I'd imagine that Claude Code would indeed generate a half-baked Next.js monstrosity if one-shot and left to its own devices. Being the learned software engineer I am, however, I provide it plenty of context about architecture and conventions in a bootstrapped codebase and it (mostly) obeys them. It still makes mistakes frequently but it's not an exaggeration to say that I can give it a list of fields with validation rules and query patterns and it'll build me CRUD pages in a fraction of the time it'd take me to do so.
I can also give it a list of sundry small improvements to make and it'll do the same, e.g. I can iterate on domain stuff while it fixes a bunch of tiny UX bugs. It's great.
When ChatGPT first came onto the scene I actually started using it to write something in this vein - a techno-thriller starring a former fashion model trained in Krav Maga working as a nuclear physicist who discovers a sinister government conspiracy to alter the foundations of quantum mechanics and enslave humanity with assistance from extraterrestrials. And, of course, only she can stop them with the help of a gruff-but-sensitive retired Marine who has since opened a ranch where he teaches orphaned puppies calculus. I only got 20 pages (so one gunfight and a car chase) in but it was as riveting as anything. Context limit cut my efforts short. Perhaps I'll revisit it soon.
I say all this to say that if words themselves are distantly secondary to narrative then I don't see anything particularly wrong with leveraging an LLM to help crank something out.
No idea whether this is still the case as I haven't been in a Sheetz in years.
Then again I'm typing this from a Thinkpad - maybe that says something about my aesthetic preferences for computers.
The technology exists to "just talk" in high-definition audio and video. If somebody isn't asking for help when they're stuck that's a people problem, not a remote work problem. There are several possible reasons for their avoidance; if multiple people are exhibiting the same behavior it could be cultural (specific to your workplace, not the person's upbringing). Using physical presence to force their hand is curing the symptom, not the underlying cause.