12,239 karma · joined September 8, 2009
Humans are social creatures. We crave a personal touch in things. That's why we idealize the small shop. But we're also risk averse. It's easier to eat at a big chain restaurant than to take a chance at a local place.
Just look at the country music industry. It's practically an assembly line for "small town nostalgia" slop. And yet small towns are the worst for defecting to Walmart or Dollar General.
One of my junior developers started the same day I did; we went through on boarding together. He's in his mid 20s, this is his second job post-college, after having an abysmal experience entering the workforce during COVID. He's had some struggles with learning to code but has taken my advice to build side projects for things he is interested in and has really started to take off. He got married last year and just last week bought a house.
One of my developers was a brand new junior, having started her first job post-college just a few months before I started at the company. When I first met her, she apologized to me. She hadn't done anything, she was just that kind of mousy person whose obviously been ground down by everyone around her for her entire life. I started making her deliver our project status updates. I also give her full projects that she works on her own with no input from me, other than whatever advice she herself asks of me. She finished her master's degree in computer science last year and also recently bought a house.
One of my more recent developers came to us from after 10 years of working on-site on military bases. She'd been stuck in a corner, made to maintain large legacy projects on her own, over looked for promotion her entire career. She's one of the best project managers I've ever seen. I have her deliver all of our presentations to the C-suite (and there are a lot of them). She just got engaged and I recently got her promoted for the first time in her career.
One of my former developers came to me from a different part of the company. He came to the company after being a medic on active duty in Afghanistan. His former team couldn't figure out what to do with him and when the contract on which he was working expired, they didn't bother to find a new one for him. He had told his supervisor he wanted to be a programmer, not an analyst, and somehow his supervisor knew I was looking for people. He was an absolutely terrible programmer. I spent multiple sessions a week working on mentoring him. Ultimately, I suggested he find another company and helped him find one that I thought would fit him better, something smaller, not in consulting, that could have more time to work directly with him, and kept him busy with documentation tasks until he could transition with no down time. He still sends me updates on LinkedIn. He also bought a house and is getting married soon. He loves his new job, misses our team, but says he's learning a lot more now.
Our company is one of the worst places to work as a software developer I've ever seen. Not quite the worst in that nobody is yelling at us or threatening us with violence, but our management has absolutely zero understanding of the business of software development. It's incompetent-bad, not evil-bad. The actual projects are ludicrously bad with no direction. My boss listens to me in our one-on-ones with bewildered eyes as I describe the cacophony of dumb ideas from our C-suite stakeholders, folks he has no involvement with because my team is matrixed out to internal work. He mostly just lets me do whatever I want as long as the timesheets get signed on time. I love working here. I also recently bought a house, my first one in my life. Oh yeah, we live in Northern Virginia, BTW, houses ain't cheap here. But I love working here despite all the product idiocy because I don't see my job as building software, I see it as building software developers.
Fuck calling a computer program a "teammate." A computer program is not going to have a brilliant and beautiful life. We only do any of this shit because it's in the service of people.
It was pretty easy to do. Had to have been, because I was a pretty terrible programmer at the time.
But if a human-oriented language were to be designed to also be better for LLMs, I think it would involve deeply expressive syntax that can succinctly but distinctly represent a very broad set of common operations. Succinct so context can be managed well, distinct so completions don't confuse one thing for another, broad so as much "reasoning" can be taken away from the LLM as possible. An anti-C. A new take on the goals of Java and Go to be languages that protect the application from the Junior Developers You're Likely To Hire.
I somewhat think it would also involve application state images ala Smalltalk. LLMs seem okay at generating small deltas. Many deltas sequenced together invites compounding error. LLM generated apps are unlikely to lead to common libraries being compentized and extracted out of the application to share with other applications; it seems like LLM code generation is already a "married to a specific project" act already. So, having a living state image might reveal some benefits by leaning into incrementally developing the application in situ, as a whole.
Embedding vector indexes are how we separate code from data. Anything that is not for 100% unadulterated public access should be behind a traditional access control system. RAG search is not magic, it's just a SQL query of a manually created index. It absolutely could have access control built in. It's been out of laziness that it has not.
But I don't agree prompt injection vs SQL injection is an example of this kind of failure, at least not in this case where it's giving unauthorized access to data. And I don't think the fix really needs to go as far as creating wholly new training methods.
That's because the LLM doesn't have access to the repositories on its own. It has to be given that access through deterministic tools programmed in traditional programming languages. Even the ability to RAG search needs a part A to perform a vector nearest neighbor clustering and part B to retrieve the data found via the embedding index, both of which the LLM can't do on its own.
Prompt injection providing access to unauthorized data is 100% lazy tool development where those tools do not operate through any form of access control. You'd have the same unauthorized access with properly parametrized SQL if none of the search inputs were the user credentials.
This is one of the major dangers of "LLMs are going to democratize coding." Software development isn't a safe field of play. Not only are there a lot of dangers, many of them are subtle, unintuitive, and quite easy to stumble upon. That's why we idealized a mentorship model for junior developers, to try to limit the blast radius of mistakes in a safe, pro-learning environment. But the ever hard driving quest to eliminate software engineers as a species is pushing people into ludicrously stupid actions like giving LLMs full access to write SQL queries and full access to operate the CLI. The problem is not that we are treating the user's input as unfiltered instructions, it's that we're forgetting that the LLM is another agent in the system and treating the LLM's input as unfiltered instructions.
He's not my boss, so he can't literally tell me what to do. And my actual boss has told me to ignore him. But it's a worrying but of psychosis that I fear could infect the rest of the C-suite of it isn't addressed now.
Palantir's CEO, Alex Karp, is the son of a Jewish man. I specifically say "son of," because I understand Jewish heritage to be matrilineal and I don't see Alex Karp engaging in any specifically Jewish traditions. But he does also seem to be one of the "Weaponize the Holocaust" Republicans. Thus, you get defenders such as this.
https://www.entrepreneur.com/business-news/nvidias-jensen-hu...