*pops open some Chinese USB Bluetooth dongle*
*finds a chip inside that seems to be a controller*
"Google, what's the datasheet for this thing?"
> Your search - 653uw1f1 - did not match any documents.

I'm doomed... 😟
Finding Easter eggs is hard you say? Try a datasheet 😑

Fuck you, you motherfucking fuck. How DARE you have the capacity to sell fake fucking chips on Amazon and make me fucking waste hours of my god damn fucking nights trying to program your shitty, lazy-ass implementation of an EEPROM.

I followed the datasheet specs down to the fucking microsecond just to find that nothing would write to the chip, and then spent hours of my goddamn life trying to figure out what I was doing wrong, making myself feel like a fucking failure for not being able to write 1s and 0s to a few pins. Fuck you, fuck you with a giant horse cock with needles on the tip

Some time ago I had ordered a LCD display I wanted to use in a project. Ended up with a vague datasheet and no clue of how to use a 8bit parallel interface. There was also little help on the internet cuz most ppl use a serial interface.
So after HOURS of reading I finally managed to get it to display something!
I sometimes wish some stuff was better documented.

FFUUUuucccckkk me sideways. So I decided to look into USB type-c's power delivery and alt modes. Cause I kinda want to make an adapter card to run my displays over a single cable. TLDR of the rest: USB-C has some huge capabilities which noone is interested in using since its way to complex to handle for what its worth in the end.
Now PD alone is kinda ok to deal with since a lot of powerbanks use it and some hobby guys documented how to work with it. I find it really odd thou that you NEED to use a dedicated IC for using the configuration chanel to negotiate how much power you can draw. Why the USB standard didnt use some simple 5V low speed signalling? Also the standard says that you only have to implement 5v 0.6A with every other power level being optional. (This is also true for cables. Most manufacturers use only the USB 2.0 standard for them and brag about how fast type-C is. ლ(ಠ益ಠლ) )
Now to the alt modes. These motherfuckers are a real shitshow to deal with. First you need a Mux to deal with USB-C's two way insertion, so your signals wont get flipped. Next thing is that you have four lanes at your disposal in alt mode. Which you can either use for four Display Port Lanes or two DP lanes and two USB 3.0 lanes. (You always get USB 2.0) Now you may think that there would be one simple chip to do it all? Nope you need atleast two at the price of 6$ each. One for PD and one for Alt modes. Both are very hard to solder (QFN, 0.5 mm pitch 40+ pins) TI ended up being the only one with a decent offering of IC's that do what I need. As for working with them, you would think that you just slap a simple MCU on there that communicates over I2C or SPI to configure the chips? Nope! You program the chips memory from which it configures itsself. And the programming is done with some TI tool which gives me no idea as to how you can handle everything whith no control logic behind it.
Looking into alternative IC's leaves me with cypress semi. And their documentation is basically a total mess. I wanna know what that chip is good for and what I need to do to make it work. I dont care about technical details mixed with marketing jargon nobody understands. And I really despise that I have to register just to download a datasheet. Especially since there is no info about it on the main page.
And this whole rant hasnt even touched the topic that USB-C only uses DP and nothing else. So you better hope that you have DP++ so you can use a passive conversion.
This was my Ted Talk about USB-C. Some info in it may be subject to my stupidity and errors as it currently is 02:15 in the morning and I need some sleep.

When you try to reverse engineer some $5 toy but the ICs Datasheet is only in chinese ;-(
And Google translate for pdf sucks.

You know what's rocket science? Serial ports.

Every freakin' datasheet states RX/TX but not from which side of the connector. Some look at it from the inside (RX for own receive), some from the outside (RX for receive of the counterpart). But never ever try to explain what is what, that would be too easy.

On literally any first attempt of connecting devices in my life it was wrong. And then you switch 'em and it's still wrong. Then you switch again, and it may work. Or you have to switch a few times more, you never know.

Those freaking bastard interfaces from hell.

when you realise that as an intern you need a datasheet to understand the datasheet...

So I was designing a transformer and was looking up toroidal cores. The one I had in mind was made of a material the manufacturer calls “3E5”. Looking for a material datasheet I found a website with a download link for a material “300000”…

Dear web devs: How the fuck is that even possible? I can see what happened here but who thought whatever they were doing there was a good idea?

When you need to work with the register of your microcontroller but you fuck up the addresses. I wasted so much time looking at my code to figure out what I'm doing wrong. I tried everything, looked up the datasheet again on how to initialize everything and in the end I fucked up the fucking register addresses. Three addresses had, at the offset, one 0 instead of two.

I never felt so dumb in my life

I am trying to reverse engineer a fingernail hardening device for rapid hardware prototyping (becoming some kind of hardware developer I guess)

Since it is a fucking mess (all cables are black) they've chosen a weird construct to operate microcontroller on 240Vac (seems to be possible and made in very low energy consuming devices) i do not find any datasheet for one of the used products. It would help a lot but no. And messing around with high voltage is no fun.

I'm unsure if this fits as a dev rant since most/all I've read so far are software-related.