I don't mind the rejection (I know I'm not _that_ good, I understand there's tons of applications and I'm fine with that), but the wait and lack of clear feedback sucked.
The response was particularly unclear - was I rejected outright? Did I slip through the cracks and then the role got filled by someone else? Should I reapply, or am I not a fit for company culture? Or just maybe not a fit for the role? If I reapply, should it be with the same interview packet, or should I rethink it? Like, is it me or is is it you?
Even when I applied to Google (a famously 'bad' recruitment experience according to most) I was able to at least regularly talk to a human who would give me feedback from interviews. And when there was a lack of team fit they'd tell me so clearly and help me look for another role. They treated me like a human! Like, I could talk to someone! Oxide just gave me a canned answer without a signature attached and no way to actually talk to anyone.
Oh well, in the meantime I've actually found a meaningful job where the recruitment experience didn't feel like I'm just throwing messages in a bottle into the ocean and hoping to get a response.
The particular 'mess' I've encountered was I applied (wrote 11 pages of interview material) on 2024/09/29 and then received a canned 'yeah whoops sorry for taking this long, not interested' on 2025/03/24. That's almost 6 months of delay from submission to first contact.
Terrible process. You need to give feedback early if you're not interested in someone, not leave them hanging for nearly half a year.
It's one of those things that every embedded dev kind of cobbles together on their own as they discover the limit of struct arrays stored in EEPROM.
Except this one actually seems worse in some ways, because to find a file you have to keep following what is effectively a single linked list of file headers until you find the file you need.
The authors even acknowledge this is just a copy of tar's approach, and even acknowledge that that was in turn done this way due to a lack of random seeking on tape systems at the time. But a microcontroller's EEPROM/SPI/... data is nothing like this? You can just do arbitrary seeks. So I'm not sure what they were going for here.
I see cams intersecting eachother and still nothing that is actually ready to be manufactured or even looks like a design that has had any thought put into it. It's the CAD equivalent of idle doodling.
Do you have a single person on your team that's actually a mechanical engineer with practical industry experience?
Yeah, no, that's a lie. This isn't a CAD model. It's a fantasy 3d model that looks like it's straight out of Gearhead Garage (1999).
Any time I see these 'AI CAD' solutions it's always toys, toys, toys. Show me something functional that you've actually manufactured (shitty 3D prints don't count). Or at least show me something that can actually be assembled and isn't just a bunch of boxes with no fasteners to hold them together.
It's surprising to me how many people here seem offended that someone might just not want their code.
I guess it takes quite a lot of experience as a maintainer to realize that 'free' in 'free code contributions by strangers' is like 'free' in 'free puppy'.
matrix: @q3k:hackerspace.pl
irc: q3k on libera.chat