@lungdart They have access to all the leaked data, but if you want to check your password, they (currently or at least used to) offer an API that goes like this:

-You are responsible for hashing your password/ text locally

-You send the final `n` bits of the hash

-Haveibeenpwned sends back a list of all passwords with matching partial hashes

-You are responsible for going through the list and checking if your specific hash is present

If so, you have been pwned

It's a service intended for enterprises to make sure employees don't use cracked passwords.

@lungdart you might need to think up or implement clever zero-trust solutions like haveibeenpwned.com does for password checking. Way above my paygrade.

Oh also:

Syntax error: unexpected end of string input (line 6, col whatever. String starts line 3 with 'toor)

with the site being absolutely dead, I've not been getting the same dopamine hit lately and my digital footprint is starting to be more of a negative than the site is a positive. I'm not upset with any community members or anything dramatic like that, but I think my account is gonna get wiped soon too.

Cool tools, but I think I would probably actually murder a co-worker if he generated/ encrypted secret information from a website like this with zero reputation. Or even a website with a good reputation, for that matter. Everything crypto like this needs to be local and trusted as much as possible/ reasonable.

Amazon? The answer is probably just that they're evil and taking out devs with high salary and replacing them with brand new ones at half the cost and 0% the knowledge of your internal systems.

This is called "brain drain" and is the death throws of a dev team sorry.

I wouldn't make any new clients in the year of our lord 2026. The backend is definitely going down this year.

@qwwerty the most boring thing of all time is a paper comparing the training of 2 copies of the same model using 2 different implementations of ML. Yawnnn

@YourMom of course, models are generally initialized with random weights, not zero, because zero weight wrongfully indicates a negative relationship between two neurons. If the weight is random, it can be smoothed out as you train into the correct value as you optimize for your loss function.

I tuned my LLM personality to make ChatGPT drop the sycophancy plus other conveniences about a month ago. It works great and now I don't feel imposter syndrome every time it blatantly over-praises me (it no longer does this)

The importance of this depends on what "ML code" is.

If it's an already-trained model with temperature at some constant, this is slightly interesting because AFAIK an LLM tuned with 0/ constant temp should produce the same results. It's just a program reading the weights of the model.

If it's a container that is training the model twice and comparing results, this is painfully obvious. There's a lot of stochasticity in model training.

thats why i like windows 7. it only took 7 minutes to boot....

The fact that you indeed have 10 years of experience and additionally said time was not spent with your thumb up your ass doing nothing, probably

That's cool! I just started my first day at github. These idiots think it's some sort of exercise program, but I know better, so I deleted push and pull. Hopefully people appreciate it 🙏🙏🙏🙏🙏

If you need, I can pose as a consultant and tell them to use whatever you want.

Which - out of curiosity - is what? My personal projects I go 100% vanilla and implement all my own controls as custom HTML elements (sort of like web components, but I typically avoid shadow DOM because it's more headaches than it's worth).

But my personal projects don't have the same level of seriousness as a business project does.

With all the time and code you guys spend and write on devRant peripherals, you could have made sox clones by now. At this point just steal the SVG assets and republish them, dfox isn’t even active enough to shut down the site let alone sue you for stealing.

@12bitfloat @retoor ya, my opinion is definitely an outsider's one, that's why I said it was null from the start. I don't know much about Linux or Rust so I'm just guessing. I've seen some of the drama between Linus and the Rust for Linux community and that's basically all I'm working off, besides the two days I spent with Rust before getting bored and moving to Zig instead (fun!)

This is actually a real thing! I watched a YouTube video on Film Noir last night.

Noirvember has a wikipedia page!: https://en.wikipedia.org/wiki/...

As someone who wrote a fairly large JS-only backend and then abandoned it exclusively for the reason it was JS-only, let me give some insight (TypeScript only has a subset of these issues, the build system actually is really nice for adapting JS to the back-end):

- It's great for really small stuff. I still recommend it as a backend for dev servers, simple game servers (like slither.io, whatever), etc.

- It scales horrendously. I was even using modules, not CommonJS, and shit was just awful. Refactoring only worked half the time, so once you write code and start to use it, you're basically stuck with it.

- Performance *does* stink. You can point to benchmarks where bun outperforms assembly or whatever, but at the end of the day, you're writing a scripting language that lives on the stack. If you need to do something that requires high performance, you're going to need to write it as a micro-service that your backend calls out to.

... more, but I'm out of comment space.

I don't really give a shit about the memory safety of Rust. You can write memory safe c code, and c code that is the age of the Linux kernel (plus, the extra set of eyes helps, being the largest collaborative software project on the globe) typically is memory safe anyways.

It's mostly just that c *will eventually* fall out of style. It's already largely out of style. Business applications simply are not written in c anymore. While most devs can make their way around in a c codebase, there are vanishingly less c professionals that work with it daily. That's a bad thing.

But a newer tool, like Rust, that genuinely finds its way into non-niche business applications regularly, has a professional pool to pull from. People that use it at work, then come home and work on open source projects for fun or whatever.

In the next few years I'm honestly expecting a fork of Linux to be completely re-written in Rust, without Linus.

I'm torn on rust-for-linux.

For one, I'm not a Rust dev, so my opinion is largely null anyways.

I am a c/c++ hobbyist, though, and updating the tool chain isn't that bad of an idea from this perspective.

I think the Rusty conversion will be good, but it will take time. A bunch of lifeless hacks will half-implement buggy versions just because they're Rustacean fanboys and want Rust in Linux. We're probably in that stage now.

Then, once things get noticeably bad, genuinely good devs will step in and either replace or fix the shit-tier code hastily written by the hardcore Rustaceans.

Well if it's an internal tool, then that's a horse of a different color, especially if all 8 people are also responsible for maintaining the database.

There should still be a prod and dev environment though, and there should still be a promotion process for database changes from one to the other.

At least the Sr. eventually came around to admitting their mistake. You could be stuck in a bureaucratic loop of "I'm the sr on this project and what I say goes. We already started this way and now your job is to implement it until it's 5x as complicated as it needs to be and you want to kill yourself"

the zip format is an archive format with optional compression. It uses the DEFLATE and INFLATE algorithms along with LZ77 (or something like that idk) run-length encoding (RLE).

Choose a language that you want to learn (maybe haskell? :D) and implement it with UTF-8 file name compatibility!

@12bitfloat well, they sort of need to, or else the global economy will take a dip.

And they sort of won't, so buckle the fuck up I guess.

We worked with RAGs at work.

After a few months, we stopped working with RAGs at work.

It's a retarded system that cannot be perfected, only a % of accuracy will be achieved.

Semantic search SUCKS for specific information. For example, if you have a bunch of data that says "my phone number is xxx-xxx-xxyz" and then you ask "What is Sandy's phone number" it will say "I have no fucking clue!" because RAGs suck dick.

The best approach is hybrid - have a RAG that searches both a semantic index AND a traditional index. This way, you get both semantic and literal matches.

But it's still just throwing more money at the bullshit and hoping it grows into a flower. For us, it never did, and we got bored of spending money.

Good luck!

To be fair, if it exists in c, it also exists in c++. There was probably no rush to implement something that's already available.

Yeah well, when you get paid retail wages, you’re not a tech bro. You’re a retail salesman.

I returned a router the other day and he said “what’s wrong with it” and I said “the 5 ghz band has no internet access” and he was like “okay what’s wrong with it though”

Really awkward but what do you expect, an engineer?!

It should be allowed. Just like googling should be allowed. You should be allowed to use all the tools you normally use. It’s not a quiz, it’s an assessment of your skills: toolchain included.

That being said, you should be judged on your AI usage appropriately. Just like if you were to copy and paste your whole interview from Stack Overflow, using AI to generate your entire interview should be a FLUNK. The company wants to evaluate your productivity, yes, but they also want to make sure you can do work without grinding to a halt if AI spits out the wrong answer. Maybe get ahead of the game and give interview questions that AI struggles at or is difficult to solve with AI.

Hating on tools is for perfectionists. Us guys that need to meet deadlines don’t care about tools as much.

Without looking it up, here's my interpretation:

HashMap is just a regular hash map with an array on one side storing hashes, and a value on the other side (depending on implementation, this is typically a list due to collisions in hash maps)

HashMap = HashMapEntry[ {bin hash, HashMapValue[ ]} ]

LinkedHashMap sounds like the same thing, but linked list driven?

LinkedHashMap = Root = {bin hash, HashMapValue[], Node next}