Programming thread

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
Does anyone have experience with cleanroom development? I do with hobby projects frequently, but I'm going to have to do it for a corporate product and I'm wondering if there's anything I should be aware of so that I don't cause a legal kerfuffle
 
I may be retarded, but how it is different from standard enums?
For one, it adds better handling of Java-style enums, for another, it supports stuff like flags, and the best part is that it's totally compatible with existing enum code.
I've had to hack together different things that this package adds at points, and it's so much nicer just having it written
 
Does anyone have experience with cleanroom development? I do with hobby projects frequently, but I'm going to have to do it for a corporate product and I'm wondering if there's anything I should be aware of so that I don't cause a legal kerfuffle
I suspect the insight you're looking for- if it might get nasty- would be from the legal side of things. If so, I assume this is a difficult question, and the legal answer to what is appropriate differs based on things that don't necessarily have to do with software development:
  1. I'm sure case law (in various courts) will have evolved from the Phoenix BIOS days
  2. That Phoenix BIOS cloning? I bet the 'Chinese wall' was breached many times, with engineers talking on the phone (through a mechanically switched switchboard, recording no records) and in the cafeteria and probably even via letters (shredded prior to release).

    You cannot fuck with that shit nowadays, everything is recorded and any record of contact between the 'clean' and the 'dev' guys even if it's a call about where you're going to meet up so he can drive you to the Christmas go-kart race sober can be subpoened and interpreted in civil court as suspicious. Of course, if you're dicking over a smaller player that might not be able to take the legal fight to you, that might still be an acceptable risk.
  3. Lawyers will have ways to mitigate these concerns. Whether they are commercially practical is another question.
If you're working for a company that's going to step into this space, then your bosses should speak to (preferably specialized) legal counsel.
 
I did an interview loop at one of the FAGMAN companies last week and have a final interview coming up soon. Any tips on surviving in FAGMAN if I make it (as someone who hates troons)? Or any tips on the last interview itself? the recruiter has not told me the nature of the interview.
Keep your head down on the job. Lots of people do. Depending on the department you're in, the people might be majority conservative, but won't say it out loud. The pajeets also hate the troons, by the way. Your projects will probably be mind-numbingly boring unless you are both really smart and gullible enough to take resposibility for something. Also, if you are a white man in engineering, you aren't making it past "senior" unless you are literally worth hundreds of millions of dollars to the company, and even getting there will be a bit of a slog unless you learn to play internal politics well. The same goes for whities of all genders outside engineering. Your job is getting promoted, and getting promoted means playing internal politics.

The last interview is usually an onsite, which is a full day off faggots asking you dumb leetcode questions plus some "behavioral" questions (like "how did you debug a particularly tricky bug"). It's all an exercise in gayness, so when they ask you about the last time you put on your programmer socks, come up with a good story. Small talk is your friend, and generally just tell them what you are thinking while you solve problems.
 
Truly some of the most insufferable people on the planet
A few jobs ago, there was this autistic Chinese guy with a PhD who literally could not speak English. He didn't have a heavy accent or bad grammar, or even both of those. He straight up could barely speak English. I have no idea how he functioned in life. He would get some request from our director, who also sucked at communication, barely understand it, then disappear for a few weeks before producing some fork of Jupyter Notebook or something that didn't solve the issue at hand. He also worked from 6AM-2PM for some reason. Didn't last for more than a few months, obviously.

Since I work in machine learning now, at least the PhD holders I encounter have relevant technical knowledge. Their big problem is that they're entirely helpless outside of their area of specialization. "What command did you run, what did it do, and what did you expect it to do?" is like pulling teeth with most of them. Zoomer bootcamp kids can figure that out fine, graybeards obviously can figure it out fine, but if you've spent decades working on algorithms for computer vision, somehow you forget that along the way. Unless they went into the managerial track rather than the Super Senior Staff Principal Research Scientist Engineer track. Then they send you some Deloitte "27 steps to deploy an AI workflow" PDF and ask you to implement it by Friday.
 
Since I work in machine learning now, at least the PhD holders I encounter have relevant technical knowledge. Their big problem is that they're entirely helpless outside of their area of specialization. "What command did you run, what did it do, and what did you expect it to do?" is like pulling teeth with most of them. Zoomer bootcamp kids can figure that out fine, graybeards obviously can figure it out fine, but if you've spent decades working on algorithms for computer vision, somehow you forget that along the way. Unless they went into the managerial track rather than the Super Senior Staff Principal Research Scientist Engineer track. Then they send you some Deloitte "27 steps to deploy an AI workflow" PDF and ask you to implement it by Friday.
Aye, I've said it once and I'll say it again: 99.99% of ML guys are shit at programming. I used to work with a lot of brilliant guys in this field, but so many of them were technically helpless. Their code is barely readable and it's like their ability to process information shuts off the second the python interpreter spits out an error. To their credit, they know their way around numbers better than most people in the world.
 
Truly some of the most insufferable people on the planet
It's difficult to mesh software engineering approaches with computer science approaches sometimes. I think both have value, but they definitely are optimized differently.
In my head, there are three kinds of people in programming:
- Computer Scientists, basically more math and theory oriented
- Software Engineers, people focused on applications
- Code Monkeys, subhumans

Obviously these three groups have crossover, but as a heuristic I've found it fruitful
 
Aye, I've said it once and I'll say it again: 99.99% of ML guys are shit at programming. I used to work with a lot of brilliant guys in this field, but so many of them were technically helpless. Their code is barely readable and it's like their ability to process information shuts off the second the python interpreter spits out an error. To their credit, they know their way around numbers better than most people in the world.
If gen AI was actually good this would be pretty much the perfect use case for it.
 
  • Agree
Reactions: y a t s
To their credit, they know their way around numbers better than most people in the world.
That's because you don't know better. Mathematicians mock ML people for being dumb at math and going "hurr durr gradient descent" too. They seem to know just barely enough math to get through ML interviews, then it's back to "StAcK mOrE lAyErS" and "MoAr DaTa" like a petulant child.

ML/AI bubbles have come and gone because people see what looks like magic and then realize it's actually just trivial math on a lot of data, and they have access to that data, too. The most recent wave is only different because the sheer volume of trivial math involved in constructing an LLM is so large that most companies can't do it in house.
 
Does anyone have any experience with nim? I'm considering using it as a glue language in a hobby project, but I've heard that performance can vary a decent bit.
 
That's because you don't know better. Mathematicians mock ML people for being dumb at math and going "hurr durr gradient descent" too. They seem to know just barely enough math to get through ML interviews, then it's back to "StAcK mOrE lAyErS" and "MoAr DaTa" like a petulant child.

ML/AI bubbles have come and gone because people see what looks like magic and then realize it's actually just trivial math on a lot of data, and they have access to that data, too. The most recent wave is only different because the sheer volume of trivial math involved in constructing an LLM is so large that most companies can't do it in house.
It's probably just sample selection bias. Some of these guys I'm referring to are genuinely brilliant mathematicians and leading experts in their respective fields, but they can't write a python PoC to save their lives. As you might expect, this issue was most prevalent among my fellow theorist colleagues.

Besides, come to think of it, saying you're better with numbers than most people in the world probably isn't that big a flex given how retarded the average Joe is.
 
Does anyone have experience writing virtual file systems? I’ve looked into it, and at least for Linux, there’s kernel modules or FUSE, but I’ve not had the best luck with either thus far
 
Does anyone have experience writing virtual file systems? I’ve looked into it, and at least for Linux, there’s kernel modules or FUSE, but I’ve not had the best luck with either thus far
Haven't written any file systems but I'm pretty sure you're just going to have to suck it up and use FUSE. Kernel modules are probably going to end up being both more difficult to work with and more painful to use as a user.
 
Back