Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "yolo"
Did a nasty thing in prod...
So nasty even default graph tells me something about going yolo in prod.
Maybe it's weed. But feels like that graph tells me not to trry this shit ever again.10
I was nearly about to punch someone today.
So, this guy is taking issues with my 3D model, yeah? But it's not the model he has issues with, it's that "why doesn't this include the stuff """I""" need?". Well, you giant man-baby could have actually visited the model like two months ago when I made it, but noooooooo let's leave it until a few days before his massive demonstration is due. Plus, the pieces I received from someone else also didn't have this info, so, like, where do you want me to get them from? Oh, from the "other" model that was literally delivered by a third party like two weeks ago? Nice. Hold onto your breath while I go rip that model apart piece by piece and put the info you need, in the format you need, in this model. 😒
... Jeeeeeez. And my computer broke down two days ago. 🤦
Could this get any worse? It could, but didn't. Luckily, someone else gave me a hand, so now I just need to go to work on a weekend just to install unreal engine again just so I can rip the second model apart for this one piece that he "really needs".
The worst part? I'm sure all of this tantrum is actually so he can justify why his work is ... well... "not working".
Let the finger pointing games begin!
(Actually not afraid of that at all. My boss knows better so yolo)
Idk, my brain is eeeeeeeeeek.3
Am I more active because I am feeling good, or is it because it's too hot here? 🤔
Anywho, giant NN classifier, come at me!
PS. I think it's gonna be a a major failure, but YOLO. 😜1
- Remake all my hacky products and finally make those adjustments and improvements I always forget about. (A shitton of maintenance that I always YOLO my way through)
- Potentially finally give digital drawing and design a go as a second career (if money permits, also)
- Move to middle of Asia, dead center of Kazakhstan or wherever there are gypsy tribes, learn their language and teach their kids about computers and robots and make a lot of products that'd make a gypsy's life easier. Or rather, create a modern gypsy life that does not override their traditional ways, rather integrates with it. (This is one of my dreams, which I know will never come true. Gypsies and nomads do settle more and more each year and their culture is basically going extinct. Plus, govts around the world dislike them greatly)
- Do a lot more research projects in robotics. Literally make everyday robotic items and then sell them. (with a sprinkle of AI/ML, that is)
All the above would also need lots of money and effort tho.1
Writing simple driver for AT24C256 eeprom on pico (RP2040)
It turned out it was FT24C256A, which should follow same protocol.
After literally over month of coming back to it, getting stuck again, rewriting things (including some functions of pico-sdk), i almost gave up a d started just yolo trying random shit.
Afterall the documentation on addressing the chip fucking missled me -_- (1st bit is r/w flag and 2-7 bits are address, counted from MSB->LSB)
I made it work yesterday.
In meantime Ive rewritten Wire library, Ive modified someone's else rewrite, extended sdk to allow getting i2c registers, tried to use tiny go just to learn it doesnt support i2c slave mode, resoldered entire thing few times, measured connections few too many times etc.
Frustrated I doubted I will ever manage to finish putting this project together because it looked like Im just too noob.1
I’ve been researching the different YOLO object detection frameworks and I saw that YOLOv8 came out recently. It’s seems like the past couple versions (v5, v6, v7, and v8) have come out super fast. Anyone else notice this?1