Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "yolo"
I asked my teammates if it would be ok if I made multithreading code for the collisions of our game engine and they just sent me this, I'm going to try anyway. Yolo.2
When you have a bizarre bug that you can't consistently reproduce, but you're already past your deadline.7
1. Finish my own game
2. Get a publisher
3. Get rich
4. Buy a big house with a swimming pool on the top and get 2 bisex girlfriends44
I recently suggested we start giving our releases code names, so that they accurately describe our client's change requests.
The idea was quickly rejected after I suggested the first two code names be "#yolo" and "Leeroy Jenkins"
Apparently I'm the only one that thought it was funny.8
Probably posted before, still funny!
alias yolo='git commit -am "DEAL WITH IT" && git push -f origin master'1
I just saw
`git add . --all&&git commit -m update&&git push`
as a npm script hook m) I don't even care, just surprised it wasn't named yolo.2
That awkward moment when you realise that your machine is doing more learning than you this semester.5
I literally cannot get this computer to boot from ANYTHING other than its hard drive.
I want to boot from a usb flash drive, but the bios doesn't support that. it supports standard and 120mb floppies, ZIP drives, usb floppies, usb cd drives, etc. but not a generic USB drive. You'd think the bios developers would have heard of them back in 2012, but they also refer to Windows as "window os", so who knows.
I changed the boot order multiple times to include everything that might possibly include a usb flash drive, and then just tried all of the other options as well. No luck. Everything just booted straight to Windows.
Okay, that's not exactly unexpected, so I found a boot manager that allows booting to usb drives, and burned that to a cd. I made sure the boot order included "CDDRIVE" first (and "USB-CD" second just to be sure), and tried again. The bios refused to boot from the cd because it's in a cd/dvd drive, and cd drives are VASTLY different beasts than dvd drives, apparently. Like, it didn't even ask the drive to spin up! It just booted straight into Windows.
After a few more reboots (and quite a few middle fingers), my dvd drive magically appeared in the list of allowed boot devices. Why did it just show up now? No clue :/ I'm just happy it's there.
So, I pick that, save and exit, and wait for my shiny new boot manager to pop up. The cursor flashes a bit, moves around, and flashes some more. Then Windows starts loading.
what the crap? why?
So this time I disable booting from the hard drive altogether. In fact, I disable everything except the dvd drive, because screw this, and save/restart for the twelfth time.
Windows greets me.
What the hell?
At this point I'm tempted to unplug the friggin' drive. If Windows still greets me after that, I'm just going to check myself into an asylum and call it a life.
Either the boot manager in question is triple-faulting and the bios is transparently failing-over to the previous boot config (Windows), or said boot manager is just like "yolo!" and picks Windows anyway.
If a different boot manager doesn't work, I'm totally out of ideas.
Edit: disabling HD boot entirely and removing the boot manager cd also results in Windows loading. It's like the bios is completely ignoring my settings. :/19
That moment when your software has been running so smoothly for the past few months that you have to start intentionally introducing bugs in patches to avoid unemplyment #yolo2
When a A.I. is gonna take over my job, Im gonna build a robot to steal the job of the A.I. and then kill it.
Maybe the robot will kill all of humanity, but yolo let's try it. Wanna see a real life terminator 😂4
When working in embedded, you basically write your program, compile it and flash it on some hardware.
Compiling and flashing usually require some black magic commands with lots of parameters so i set up two shortcuts in my terminal
yolo to compile
swag to flash
Understandably i keep it to myself1
Commit Message Part2:
6528fff Code was clean until manager requested to fuck it up
241b35f Who knows WTF?!
4381a32 Argh! About to give up :(
c3bf1a9 more debug... who overwrote!
2d68d6d Fixed a bug cause Maciej said to
b112c1a This branch is so dirty, even your mom can't clean it.
bb456d4 Shit code!
4878b46 Copy-paste to fix previous copy-paste
e2c7e87 A fix I believe, not like I tested or anything
e4b8f4c formatted all
3691208 I'm just a grunt. Don't blame me for this awful PoS.
0888b69 just checking if git is working properly...
62741aa I'm too old for this shit!
0735196 COMMIT ALL THE FILES!
09caccf I CAN HAZ PYTHON, I CAN HAZ INDENTS
ab70bde Fixed errors
934436d Now added delete for real
5f84e30 My bad
99baff8 CHRIS, WE WENT OVER THIS. C++ IO SUCKS.
953473d final commit.
f0c3b57 Just committing so I can go home
4e5ce4e yolo push
deb4e3b I CAN HAZ PYTHON, I CAN HAZ INDENTS
710c06a Commit committed....
3c45e67 it is hump day _^_
4487788 Committing in accordance with the prophecy.
bf86e7e This solves it.
4804f68 FONDLED THE CODE
051d42e REALLY FUCKING FIXED5
There are many ways of development...
Test Driven Development.
Behaviour Driven Development.
Acceptance-Test Driven Development.
YOLO Driven Development.
But nothing in this world is so frustrating as...
Buzzword Driven Development.
As soon as your managers spot a new technology, it needs to be integrated...
For fucks sake... New is not always better.8
So, the house next door to me is being renovated into half a dozen apartments. This process has been ongoing for like 4 years of here-and-there houseflipper failboating, and if I had to guess, 3 owners worth of this fuckery.
The latest shitheel trying to polish this turd into something saleable has had it sit partially covered with plastic for months, mostly getting rained on. One crew came by last week and put half the thermal shielding up before something happened and they left. Then half of it fell off the house, into my yard. Nice person that I am I gathered it all up and left it in the various excavated pools of water on their property in which I can only imagine they are busily raising farm to table mosquitoes for the local market.
FF to today and I see a crew pull up to the house and start nailing plywood to the side of the house with no thermal pad underneath it. Which is a legit code violation and a mold hazard, but yolo amirite? I chat up some of the guys and find out that they were scheduled to install the plywood today (apparently he'd run out of money for the nice modular siding they used on the back half) and the owner didn't give a shit if the rest of the work was done. Meanwhile shit is still falling off the house onto my house, but also wgaf. 🚬
Tl;Dr the people trying to flip the house next to mine were obviously IT managers in a previous life.6
My computing teacher says that html is his favourite programming language to teach.
Needless to say he's not very good at teaching us html and js.7
Found this in a code base I just started to work with. I'm glad it wasn't referenced anywhere. This is going to be fun...4
Made this project "Come Fix Me" in a 24hr hackathon. Won the most innovative solution.
An android application for citizens(users) which allows them to register issues on potholes in their area.
Web for report management
User clicks a photo of the pothole and registers a new issue.
The photo gets uploaded on the firebase database along with other information like GPS co-ordinates.
The image is downloaded in the server and served in the pothole detection script.
If pothole is detected an estimated area is calculated, if no pothole is detected user's issue gets rejected.
After successful detection details are uploaded on the web for administrator, these issue are forwarded to govt. officials.
Once the officials claim that they have fixed the pothole, the user gets a notification and they can close their issue if pothole is fixed
Recently someone from QA came to me yelling "Why did you push to master? You have a feature branch for these changes..."
I replied "Indeed. Coincidently it's called 'master' "2
Microsoft sent me this on Friday... So i keep reading people complaining about the update and visual studio sucking dick... Me? Ahhaha I don't give a Shiiiiii-et!!! Bring me moar swaaagggggg!!! Hahaha whoooo4
even when I'm drunk like now, i still feel a pain in the ass, you know, like if i tried to do a fcking reverse tombstone with a beer bottle in my asshole.
This is the end of my sixth year. Yup, 3 years network/system admin, and now 3 years programming.
Now what, you were useless, didn't teach me anything, i feel like the chimp's sperm filled leprous mare that write planning for the year just want us to learn french and laws.(oh, the chimp as IST prolly.)
You ruinned me, I'm fcking poor now, but i have a degree (yolo)..
Well, you gave me some friends.. thanks for that you dumbass.
Dear teacher, i want to know, why are you so incompetent ? I mean, did you find your degree in Mother of shit' school as me ?
And also, pleaseee : next time i get an exam on a specific software that runs only on windows, i'll probably kill the fcking entire classroom, and this include you, and your merkel's ass licker familly.
That's it, random post, some hate, sorry fellow ranters, have a good day!5
This is what I call bureaucracy3
I'm having an in-person interview with Amazon AWS team next week. What to expect? Any tips on these interviews?4
I am currently doing my first ever internship. It is a medium-ish sized IT company and I basically do stuff in networking and software development. I sit on my chair, wheel it back and forth the small space behind my desk for like and hour. Then I go to the cafeteria, eat whatever is there (it’s absolutely free? Hopefully). There is a pool table which is always occupied. Then I sit in the lab and configure routers till 8 in the night. Boring.
I am developing a management system side by side so I break my head over server side routes (seriously, they are confusing) over the night.
So coffee is my mantra and boring is my life.2
Continue with my ALL-OUT year of JUST DO IT. Trying to see what happens when I go YOLO for a year.
It started well about 4 months ago, but I slowed down a bit. I just want to pick up the pace again and JUST DO EEET. See where it leads.
Been working on a lot of side projects. I want to finish a few. One is already pretty much finished.
Then, towards the end of the next year, I think I'll start looking for a dev job.2
Something to cheer you up mid-week:
> alias yolo='git commit -am "DEAL WITH IT" && git push -f origin master'
So there was an initial meeting how this new feature can be done..
Developers and Software Architects decided quickly that it is technically not a real effort. But the problem is, its not the correct way to do it, and it should be solved in a clean way, or we will be fucked for the years to come.
I just got an email, that in the WebEX just held, between Project Lead and Customer, it was decided to do it anyway. Well thanks Project Lead.. Your project ends in 2 years and will be considered feature complete. Congratulations. Fuck whats coming after that, right. The fucks in the support and maintenance we will be having in the years to come arent on your budget, right, so who cares. Enjoy your bonus. Why dont we just go and write IFs everywhere the software needs a feature in the future from now on?
Dude i wish that ONE day, project success will be measured considering the costs following the project, so that all these fucks gotta pay back their success fees. Fucking YOLO i guess1
I do not believe in those complex conspiracy theories. I have been long enough in IT and have seen the most simple plans fail.
When another developer has put a "Yolo" production log in de codebase and committed that to the release branch..2
College came to me today with version 3 of an attempt for a bug-fix followed with the comment "This one should work, this time i tested it myself before commited it and came to you"
I just thought: then wtf did you do the previous two times? Just yolo commit it to the codebase?
Maybe its time i found some other place to work..8
Anyone know of any good reference material that teaches you how to implement and train your own Yolo object localization neural network? (Preferably for tensorflow) I'm not looking for pretrained models that you just downloaded and run, rather a tutorial that walks you step by step through the implementation of the network, the reasoning behind the architecture, and examples of the training data used for the training as well as the process of training?
I know it's a lot to ask but it's really frustrating when ever example is just "clone this repo, hit run and use the pretrained models" sure it might get you up and running quickly but it doesn't really teach you anything...
P.s. - seems like every educational post goes from super simple to super complex without any middle ground and the super complex stuff doesn't tell you why its used the way way it is.5
Coworker pushed some changes and gave me good reason to rant.
Here's my story:
I start implementing a new feature, senior reviews it and suggest some changes, which are actually good ideas. I continue developing and implement the suggested changes.
The next day, senior keeps working on outdated source and makes similar changes like i did on the day before. Just pushes it anyway and breaks fucking everything.
The api now contains redundant information.
My classes still exist, but aren't used anymore. Let's keep some redundant code in the project, because deleting it is so much work.
All the unit tests broke, but he just commented them out, so everything is green again. We have now 0 tests which actually do something in the project, but at least the build is green...1
Fack I hate this CMS we have. Using Fetch and sending data as encoded JSON doesn't get parsed nor recognized by the CMS. I was pulling my hair out, understanding the differences, switched back to XHR... and then noticed the buggar:
XHR sends data as "FormData()".
I switched everything to FormData and TADAAA IT WORKS MOTHERFUCKA
Lost a whole fucking day on this trying to understand whether it was my code or the CMS the problem.
Ah yes, of course, I had to reproduce the CMS on my machine, instead of having the developers lend us a "development" platform on it, so obviously I don't know what's happening under the hood :))))))))2
Accidentally... I was flicking through YouTube and ended up watching a video showing some VB I think, I enjoyed it (I've always been a techie), and it went from there... Now I'm the senior (web - progressed from VB pretty sharpish) developer. I actually wanted to be a Secondary School Art Teacher.1
I really really hope that no one post this,a friend texted it to me and I wanted to share it because made my day.
Idk where it comes, so feel free if know where this came from to post it:
//FUN PART HERE
# Do not refactor, it is a bad practice. YOLO
# Not understanding why or how something works is always good. YOLO
# Do not ever test your code yourself, just ask. YOLO
# No one is going to read your code, at any point don’t comment. YOLO
# Why do it the easy way when you can reinvent the wheel? Future-proofing is for pussies. YOLO
# Do not read the documentation. YOLO
# Do not waste time with gists. YOLO
# Do not write specs. YOLO also matches to YDD (YOLO DRIVEN DEVELOPMENT)
# Do not use naming conventions. YOLO
# Paying for online tutorials is always better than just searching and reading. YOLO
# You always use production as an environment. YOLO
# Don’t describe what you’re trying to do, just ask random questions on how to do it. YOLO
# Don’t indent. YOLO
# Version control systems are for wussies. YOLO
# Developing on a system similar to the deployment system is for wussies! YOLO
# I don’t always test my code, but when I do, I do it in production. YOLO
# Real men deploy with ftp. YOLO
So YOLO Driven Development isn’t your style? Okay, here are a few more hilarious IT methodologies to get on board with.
*The Pigeon Methodology*
Boss flies in, shits all over everything, then flies away.
*ADD (Asshole Driven Development)*
An old favourite, which outlines any team where the biggest jerk makes all the big decisions. Wisdom, process and logic are not the factory default.
*NDAD (No Developers Allowed in Decisions)*
Methodology Developers of all kinds are strictly forbidden when it comes to decisions regarding entire projects, from back end design to deadlines, because middle and top management know exactly what they want, how it should be done, and how long it will take.
*FDD (Fear Driven Development)*
The analysis paralysis that can slow an entire project down, with developments afraid to make mistakes, break the build, or cause bugs. The source of a developer’s anxiety could be attributed to a failure in sharing information, or by implicating that team members are replaceable.
*CYAE (Cover Your Ass Engineering)*
As Scott Berkun so eloquently put it, the driving force behind most individual efforts is making sure that when the shit hits the fan, you are not to blame.2
Data scientists unite!
I am working on a face recognition solution to identify and tag different faces in real time and currently using chinese whispers algorithm for clustring. The more I think about it the more inadequate it sounds (number of faces encoded increase over time thus the complexity). I've heard about YOLO but cant really decide. Please enlighten me!12
The first dev project, like real dev project, I participated in was a school one and it was double.
The class was meant to make us learn about the software's life cycle, so the teacher wanted us to develop a simple, yet complicated, thing: a Web platform to help tutors send/refer students to the university services (psychologist, nutriologist, etc) and to keep track of them visits.
We all agreed on it being easy.
Boy were we so wrong.
I was appointed as dev leader as well as some others (I was the programming leader, the other ones were the DB guy and the security guy) and as such I was in charge of the technology used (well, now we all know that the client is the one in charge of that as well as the designer) and I chose Django because we had some experience with it. We used it for the two projects the teacher asked us to do (the second one was to find a little shop and develop something for it, obviously with the permission and all that), but in the second one I decided to use React on top of Djangl, which ended being a really good combination tho.
So, in the first project, the other ones (all the classroom) started to discuss and decided to use some other stuff like unnecessary carousel for images, unnecessary functions, they created mock ups for stuff that was never there to begin with, etc. It was really awful, we had meetings with the client (the teacher) with updates on the project, and in not a single one he was satisfied with the results. But still, we continued with the path the majority chose and it was the worst: deadlines were not met, team members just vanished until the end of the semester, one guy broke his leg (and was a dev leader) and never said a word not did anything about the project. At the end, we presented literal garbage, the UI was awful, its colors were so ugly because we had to use the university official colors, the functionality was not there, there literally was a calendar to make appointments for the services (when did the client ask for that? No one knows), but hey, you could add services and their data to it, was it what the client wanted? Of course not! What do you think we are? Devs?
Suffice to say that, although we passed with good grades, the project and the team was shit (and I'm counting me in)
The good part is that the second project was finished by me and it looked really good, yet it didn't matter, the first project was supposed to be used by the university, but that thing was unusable.
Then, in the subsequent vacations I tried to make pretty and functional/usable, yet I failed because I had a deadline for another thing I had to do, but hey, the login screen looked amazing!
I missed ranting so much that I have come to a realisation that ranting keeps us waaaaaay calm!
When I was 11, my uncle called me genius and I should study computers after I went online to HP's official website (using a 56k modem connection) to download the drivers for the printer we had at hone, since somebody lost the cd with the installation that came with the printer. Today, I am 25 yo software developer earning 25k+ a year :) #thanksuncle
PM's who doesn't have enough technical skill, doesn't listen to those who have, and asks if "is there is absolutely 0% risk involved" before making a decision which only makes their project look good than rather trying to make their projects deliveries improve the world outside their project...
What about just a little yolo some time? Huh?2
arrow button click down end file goto headder include joke kunt lime
next opcode push quit up retern s unknown visual wise x(xin) yolo zup1
What should I do, I have a central function that is not documentated and no test-cases are written for it. I have no clue what the method should really do, I know that it works in 99.9% of all cases otherwise we had much more bugs. Now there is one Unit-Test that reports an issue. I tracked it down to this method, no one touched the method nor the unit-test.
My logical thinking says that there is one statement missing, but it could also fuck up another part of the code... (This project has a bad testing coverage :'( )
What would you do?
- copy paste the method for this special case (I would hate me so much for breaking DRY)
- inheritance?! (Would make it more complex and then it would be still untested / undocumented)
- YOLO changing oO?! (hope for luck, just joking)
P.s it's an edge case unit test, the client / customer probably wouldn't realised it if it happens
Every time I decide to remove/edit something in a written SQL statement in the CLI. The delete and backspace key are to close to the return key -.-4
"Even at the very least of curing your boredom, temporarily, while you sit in your cubicle and pretend to work."
I hate this guy :|1
Does anyone know any good resources that walk you through building a image localization neural network(preferably in tensorflow)? Something that talks you through the though process behind the network design decisions and perhaps examples of training data used to train the network? It seems like every search result is just an example of how to download a premade network and it's weights which from a learning perspective is not very helpful. I'de really love to see one of the Yolo version walked through and trained but honestly any localization would be helpful.