It just makes my job harder when others use it, because everyone uses it in the lazy way that OpenAI sold them on. And now there's just a lot of inaccurate shit, bad code and nonsense comments everywhere. Even the CVs we get now seem to be AI, which means I can't trust anything that's written there and need to double check rather than just a quick question to the interviewee.

There is a good way and a bad way to use LLMs and good 70% of what people do in practice is bad, which means the entire tech is fucking up everything and the bubble just can't pop fast enough. The hype cycle needs to run It's course so that we can finally settle in the plateau of productivity and ideally all those scamming lying thiefs would lose all their money and power, buy that's unlikely

@afaIk Oh I see, you have never worked with a computer in your life and you accidentally ended up on devrant rather then reddit. It's ok, it happens to many of you

Lensflare is right though. No one uses a double backslash, that's just an escape character, like in \r and \n

The path looks like this on windows
C:\Some\Path

Or like this everywhere else/*nix
/Some/Path

But Since \ is an escape character in most string/print specifications, for that path to be saved verbatim it needs to be escaped first. So to escape the \ character you use another \, so you get \\ in the escaped form.

So e.g.
\n -> new line
\r -> carriege return
\\ -> literal backslash

This doesn't show up for directories in *nix because they use / but it does show up for path with special characters, like spaces:

"/home/username/My\ Projects" the space needs to be escaped if you don't want the application (for example terminal input) to misinterpret the space as a delimeter rather than a literal space in the path

Anyway, there's a whole lot of history and detials and the short version is that working with strings isnt always safe and simple, thus escaping rules exist

No company in the entire world understands the concept of "if it ain't broken, don't fix it" so instead we get constant change and price hikes

@jestdotty I often think that people tried to tell us, but young us didnt listen.

I think this, because Im trying to warn those around me and they don't seem to appreciate it.

I also vaguely remember a lot of thing I was warned about as a kid and I ignored most of it because young me felt invincible :D no problem too big to overcome... Well my mortgage thinks differently and the job market is absolutely awful (not my problem exactly, but people around me have issues)

It's a container, It's job is separation from the system.

A) dockers set up their own environment with their own dependencies, so compatibility is ensure on all computers and in most cases architectures too
B) your own system doesn't get bloated, riddled with multiple competing dependencies, and you can remove the software by deleting the container
C) docker can set up and configure multiple systems (like server, database, ui) either in a single container or via composition, so you don't have to set up all these systems locally

The advantages are clear, it was never about space or anything, It's about neatly separated blocks (containers)

I hate calls, and not just because I hate people. Just write it, so I can get to it when ready, there's a record of what you wanted, you can easily correct yourself, and writing makes you think twice, which results in better specs.

If you want to just chat or discuss and brainstorm a problem then yes, but for transfer of knowledge It's awful... I also dislike demos

But, Nails are still used and in high use? So your analogy is not great

Yeah, but what I think is that a senior Im not there to do the task for the junior. They shouldnt push just any llm code and call it done and then have me do all the research to make sure the code makes sense. The dev is responsible for the llm slop and they should be the first filter, not the guy that fixes it after I already left 30 comments on code that needs to be removed or code that doesn't follow our style Guide, or code that duplicates solutions we already have done and are part of the code base or architecture... If the dev can't even do that then why do we need him? I can run a bullshit generator on my own just fine, but thats not useful

Money, they want money. You cost money, so they don't want you, unless you seem like you can make more money than you cost vs other solutions.

Yeah, but if I get interviewed or answered by an LLM *Im* going to flip out and tell you to fuck off with that noise.

I much prefer an annoying human to a broken piece or crap with massive CO2 Footprint

Tbh clean code is "clean code" by definition. You can't expect to follow a bunch of best practices blindly and magically get clean code and then complain that "clean code is bullshit". That's an oxymoron. Clean code isnt some symbolic depiction of DRY and SOLID and other principles. Clean code is what you get when you both: know what you're doing and keep maintaining it during development. In my years of experience I find that being willing to refactor code as you go is the path to clean code. Write simple first, verify function, then refactor and organize and finally maintain (which also means, make sure the design you started out with is also kept or updated during PRs). That also goes for other peoples code. Before you implement something in a new codebase at least skim over it so you underatand where the author intended things to go. You will often find design gems in code that looks messy at first

I like my company alot, but my fiance had a similar issue in her last job. The solution is exactly what you think it is. Leave the job and find another one. It's a struggle to find employment recently, so you might end up unemployed for quite some time, but if you have at least 6 months worth of saving and don't splurge on useless stuff like streaming subscriptions and eating out often, you should be fine. Being unemployed for some time does give you some health benefits though. It can take a month or a few to get your Motivation back if It's bad or you have other mental problems, like depression. It can be totally worth it in the long run though

If you are strapped for cash then you could look for another job while working this one, but that alone can be exhausting sometimes (or not, maybe you find one fast)

@Wisecrack Man, I hope it's gonna work. One of the worst parts about this whole LLM hype is the amount of resources it requires. The second worst part is that big tech firms are using it to monopolize the market with subpar products that require even more resources and are literally making life miserable for people while also objectively hurting the environment without a second thought.

I really think we fucked up big way with LLMs. The capabilities it have are nowhere near what they need to be to justify the cost. This is literally a kids toy that tech giants can't stop playing with and everyone is paying the price. I'm confident these models can be way more memory and power efficient and we need to democratize this before we're all running GPU farms at home...

@Wisecrack When I was stuck as a young dev, I would often find a solution on SO and deliberately copy it by hand because I wanted to *learn* the solution better. Surprisingly enough, this actually differs from just copy-pasting it because as you write it, you think more about it. It happens often that when I start rewriting it code that looked good at first sight I will actually discover things about it that could be done better in my case, or things that are really clever tricks I didn't know about before that didn't jump out immediately upon just reading, but they did during careful copying.

I think this is another skill that LLMs will take away from devs, making them objectively worse as a result if they are not careful :D

nothing merged into master should break master. That's the only real requirement. All other requirements are fluid and change based on if the deadline is in literally 10 minutes or in 5 months. But the code has to compile and must work once in master.

Everything you were forced to ignore in that request becomes Tech Debt and will be fixed in the next release, or more likely never ;)

I know this one! The answer is Windows XP on a 2001 machine with an HDD.

I timed mine back then and it took anywhere from 8-13 minutes to boot completely.

Man, glad those days are over. Booting from an SSD is less than 30 seconds and it would take a special kind or idiot to fuck that up on an OS level

@whimsical I like to think of myself as somewhat of an educator. Give a man a correct answer, and you helped him with one problem, but teach a man how to get their own answers and you have to answer less questions, or something... :D

Ofc in practice rarely anyone cares, but oh well.

Game theory in action

If everyone had the "fuck you" mentality. Companies would be forced to update their hiring proceses, otherwise they would have no workers.

But since you can't be sure that everyone will adopt that mentality (e.g. a snitch). You are risking by adopting it, even though you'd all be objectively better by not working at these companies, you can't risk not having a job due to snitches.

Game Theory tells you what is objectively the best option for everyone, but it also tells you why It's the worst choice for you.

Long story short, you should adapt the fuck you mentality only if you can afford not having a job (e.g. if you already have some sort or income)

Otherwise the best option is to play the game as is, unfortunately.

Is this why my team reported github being down yesterday?!

wat, you can create tables using API calls? why? what? how is that secured? can anyone? what? what about migrations in the future? I never heard anything this dumb before... Is he a vibe coder?

"vibe coders" tend to forget that sofrware engineering is an "engineering" job. The code itself isnt as important as the decisions made, the tools used, the flow executed, systems inpacted, users helped... There's a whole lot to our job than just writing code that works. Vibe coding is the antithesis to good design. Code that works isnt always the best code for It's purpose, deployment site, user interface etc...

That being said. If you find exactly the perfect code on stack overflow, or if you bash it out of a text generator, or hell, if you find it scribbled on a toilet stall and rewrite it character by character to your codebase, It's not going to change anything, because as I just said, the code itself is secondary to It's purpose and design. No one can stop you from copying a solution to save time if you would've writen the same one. Works smart, not hard always applies. Just make sure you know exactly what you're making

The only important thing is that you understand every line of code and the decision behind it.

The problem is blind usage of SO and AI, which you just copy. Even if you understand what it does. That doesn't mean it makes sense to code something that way, or that it fits the rest of the project, or that it's even functional code.

We had this requirement too. This was before AI was a thing, so this applied mostly to copying code or cheating. The way my prof. checked is that he interviewed everyone on their project and you had to be able not only to understand what the code does, but also why/why not different code or placement. He knew if you wrote it yourself because if you did the actual research you would likely land on something good, and even if your code was subpar you'd have strong opinions on why you did it that way.

He was a great teacher to me and he took it very seriously. He was one of those guys that would rather hear a bad answer than no answer at all.

What part of that is surprising considering the history of big corporations? Literally the one strategy they use over and over again

"He"?

Micro Services can be done right, but not with lambdas. And the only way microservices end up working well if they are separated by strict domains and there's not a lot of them. In any project you're unlikely to need more than 2-3 microservices. If you go beyond that there's a good chance your domains are split too small and the communication overhead will kill all the benefits.

And lambdas are by design too small to do this. They are just functions in a cloud and that's just hell. It's literal hell. Imposible to debug, track or test. Especially once you start handling communication via queues, dynamo updates and event triggers.

It sounds nice on paper, and it might work for very basic projects, but maaan, it doesn't scale at all. I mean it scales performance-wise but not maintenance wise

@12bitfloat hey, maybe it wasn't get "dumb" decision. Maybe this guy is a control freak that breaks into her phone. Who knows what other privacy basics he disregarded! Girl went to a friend, spilled her heart "yeah, OP just keeps breathing down my neck, I don't think I can stay in this relationship any longer" the hooked up and now we're here!

OP came in with a name like "sweetkid" and a fresh new account. So it's either a troll like Sid or someone, or it's a guy that legit thinks of himself as "the nice guy" and "the victim" and made the relationship toxic himself... Eitherway, fuck a guy who's first reaction is "how to get into my gfs phone".

not sure if I misunderstood, but I already do processing like this in some of apps on a higher level. Isn't this pretty much how SIMD architectures handle stuff anyway? You load a bunch of data into the memory, and then each thread operators on it's own bit/stride of the data.

Not sure if this is different, or if you want to make this into a more low-level concept in compilers or in hardware or something, but as far as I can tell the technique isn't new as a concept... unless I'm not getting it :D

Besides, I don't care for these companies one bit. I'd rather see this tech firmly in the hands of the open source community than a fake non-profit.

Yeah, while we live in a world where people have no critical thinking and end up hooking up in relationships with AI, and killing themselves or others because of AI, or literally spiral into full on psychosis because of AI, I'm fine with knee-capping AI. In fact I think those corporations should be held liable for what their tools and misinformation cause.

the tool is one thing, but the way they chose to sell it, that's on them. And they managed to convince a big chunk of people that this is sentience and essentially magic, so they are on the hook.

If you sell a radioactive rock to someone, saying that it's a magic rock that will fulfill your wishes, and hundreds of people die because of it, then yeah, the people were probably on the way out of the genepool already, but you still did that wanton disregard...

When the AI craze started and we only had bits and pieces of information, it made sense, but at this point it's criminal negligence in my opinion