Was lead developer at a small startup, I was hiring and had a budget to add 3 new people to my team to develop a new product for the company.

Some context first and then the rant!

Candidate 1 - Amazing, a dev I worked with before who was under utilized at the previous company. Still a junior, but, she was a quick learner and eager to expand her knowledge, never an issue.

Candidate 2 - Kickass dev with back end skills and extras, he was always eager to work a bit more than what was expected. I use to send him home early to annoy him. haha!

Candidate 3 - Lets call him P.

In the interview he answers every question perfectly, he asks all the right questions and suggests some things I havent even thought of. CTO goes ahead and says we should skip the technical test and just hire the guy, his smart and knows what his talking about, I agree and we hire him. (We where a bit desperate at this stage as well.)

He comes in a week early to pick up his work laptop to get setup before he starts the next week, awesome! This guy is going to be an asset to the company, cant wait to have him join the team - The CTO at this stage is getting ready to leave the company and I will be taking over the division and need someone to take over lead position, he seems like the guys to do it.

The guys starts the next week, he comes in and the laptop we gave him is now a local server for testing and he will be working off his own laptop, no issue, we are small so needed a testing stack, but wasnt really needed since we had procedures in place for this already.

Here is where everything goes wrong!!! First day goes great... Next day he gets in early 6:30am (Nice! NO!), he absolutely smells, no stinks, of weed, not a light smell, the entire fucking office smells of weed! (I have no problem with weed, just dont make it my problem to deal with). I get called by boss and told to sort this out people are complaining! I drive to office and have a meeting with him, he says its all good he understands. (This was Friday).

Monday comes around - Get a call from Boss at 7:30am. Whole office smells like weed, please talk to P again, this cannot happen again. I drive to office again, and he again says it wont happen again, he has some issues with back pain and the weed helps.

Tuesday - Same fucking thing! And now he doesnt want to sign for the laptop("server") that was given to him, and has moved to code in the boardroom, WHERE OUR FUCKING CLIENTS WILL BE VIEWING A DEMO THAT DAY OF THE PRODUCT!! Now that whole room smells like weed, FML!

Wednesday - We send P a formal letter that he is under probation, P calls me to have a meeting. In the meeting he blames me for not understanding "new age" medicine, I ask for his doctors prescription and ask why he didnt tell me this in the interview so I could make arrangements, we dont care if you are stoned, just do good work and be considerate to your co-workers. P cant provide these and keeps ranting, I suggest he takes pain killers, he has none of it only "new age" medicine for him.

Thursday - I ask him to rather "work" from home till we can get this sorted, he comes in for code reviews for 2 weeks. I can clearly see he has no idea how the system works but is trying, I thought I will dive deeper and look at all of his code. Its a mess, nothing makes sense and 50% of it is hard coded (We are building a decentralized API for huge data sets so this makes no sense).

Friday - In code review I confront him about this, he has excuses for everything, I start asking him harder questions about the project and to explain what we are building - he goes quiet and quits on the spot with a shitty apology.

From what I could make out he was really smart when it came to theory but interpreting the theory to actual practice wasnt possible for him, probably would have been easier if he wasnt high all the time.

I hate interview code tests, but learned a valuable lesson that day! Always test for some code knowledge as well even if you hate doing it, ask the right questions and be careful who you hire! You can only bullshit for so long in coding before someone figures out that you are a fraud.

*Manager enters the room quickly*

Manager: Coffe2Code, we have a serious problem on the application, (We are working on a chat app).

Me: What? now just few hours before the Demo?, what is it?

Manager: when I send or receive a media message (audio or video) the sound is not playing, the file seems like corrupted !

Me: that's strange, let me debug it and see.

*Me spending an hour and could not even reproduce the bug..*

Me: Boss, I cannot see the bug, can I debug on your device quickly?

Manager: Sure, here it is.

Me: hold the fucking device, press VOLUME UP, IT WAS FUCKING MUTE. THERE WAS NO ISSUE MOTHERFUCKER.

Manager, oups ok good no issue then, thanks

My first job: The Mystery of The Powered-Down Server

I paid my way through college by working every-other-semester in the Cooperative-Education Program my school provided. My first job was with a small company (now defunct) which made some of the very first optical-storage robotic storage systems. I honestly forgot what I was "officially" hired for at first, but I quickly moved up into the kernel device-driver team and was quite happy there.

It was primarily a Solaris shop, with a smattering of IBM AIX RS/6000. It was one of these ill-fated RS/6000 machines which (by no fault of its own) plays a major role in this story.

One day, I came to work to find my team-leader in quite a tizzy -- cursing and ranting about our VAR selling us bad equipment; about how IBM just doesn't make good hardware like they did in the good old days; about how back when _he_ was in charge of buying equipment this wouldn't happen, and on and on and on.

Our primary AIX dev server was powered off when he arrived. He booted it up, checked logs and was running self-diagnostics, but absolutely nothing so far indicated why the machine had shut down. We blew a couple of hours trying to figure out what happened, to no avail. Eventually, with other deadlines looming, we just chalked it up be something we'll look into more later.

Several days went by, with the usual day-to-day comings and goings; no surprises.

Then, next week, it happened again.

My team-leader was LIVID. The same server was hard-down again when he came in; no explanation. He opened a ticket with IBM and put in a call to our VAR rep, demanding answers -- how could they sell us bad equipment -- why isn't there any indication of what's failing -- someone must come out here and fix this NOW, and on and on and on.

(As a quick aside, in case it's not clearly coming through between-the-lines, our team leader was always a little bit "over to top" for me. He was the kind of person who "got things done," and as long as you stayed on his good side, you could just watch the fireworks most days - but it became pretty exhausting sometimes).

Back our story -
An IBM CE comes out and does a full on-site hardware diagnostic -- tears the whole server down, runs through everything one part a time. Absolutely. Nothing. Wrong.

I recall, at some point of all this, making the comment "It's almost like someone just pulls the plug on it -- like the power just, poof, goes away."

My team-leader demands the CE replace the power supply, even though it appeared to be operating normally. He does, at our cost, of course.

Another weeks goes by and all is forgotten in the swamp of work we have to do.

Until one day, the next week... Yes, you guessed it... It happens again. The server is down. Heads are exploding (will at least one head we all know by now). With all the screaming going on, the entire office staff should have comped some Advil.

My team-leader demands the facilities team do a full diagnostic on the UPS system and assure we aren't getting drop-outs on the power system. They do the diagnostic. They also review the logs for the power/load distribution to the entire lab and office spaces. Nothing is amiss.

This would also be a good time draw the picture of where this server is -- this particular server is not in the actual server room, it's out in the office area. That's on purpose, since it is connected to a demo robotics cabinet we use for testing and POC work. And customer demos. This will date me, but these were the days when robotic storage was new and VERY exciting to watch...

So, this is basically a couple of big boxes out on the office floor, with power cables running into a special power-drop near the middle of the room. That information might seem superfluous now, but will come into play shortly in our story.

So, we still have no answer to what's causing the server problems, but we all have work to do, so we keep plugging away, hoping for the best.

The team leader is insisting the VAR swap in a new server.

One night, we (the device-driver team) are working late, burning the midnight oil, right there in the office, and we bear witness to something I will never forget.

The cleaning staff came in.

Anxious for a brief distraction from our marathon of debugging, we stopped to watch them set up and start cleaning the office for a bit.

Then, friends, I Am Not Making This Up(tm)... I watched one of the cleaning staff walk right over to that beautiful RS/6000 dev server, dwarfed in shadow beside that huge robotic disc enclosure... and yank the server power cable right out of the dedicated power drop. And plug in their vacuum cleaner. And vacuum the floor.

We each looked at one-another, slowly, in bewilderment... and then went home, after a brief discussion on the way out the door.

You see, our team-leader wasn't with us that night; so before we left, we all agreed to come in late the next day. Very late indeed.

Once we were going to present a web service to governmental firm. All is going well so far and my boss asks me to host the web application the day before the presentation.

I hosted it and all was good with demo production tests, but I had a bad feeling.

While it was running on our server, I also ran it locally with a reverse proxy just in case.

* Meeting starts *

* Ice broken and down to business *

"And now our developer will run the demo for you..."

* Run the demo from my laptop to double check --> 500 Internal Server Error *

Holy shit!!!

* Opens reverse proxy link on my laptop. Present demo during meeting. Demo works like a charm. *

Firm representative: "Great! Looking forward to go live."

*Our team walks out*

GM: "Good job guys"

ME:

Them: Root, you take too long to get tickets out. You only have a few simple ones. You really need to rebuild your reputation.

Also them: Hey, could you revisit this ticket? Could you help ____ with this other ticket? Hey Root, how do you do this? Root, someone had a suggestion on one of your tickets; could you implement that by EoD? Hey Root, i didn't read your ticket notes; how do you test it? Hey, could you revisit this ticket for the fourth time and remove some whitespace? Hey Root, someone has non-blocking code review comments you need to address before we can release the ticket. Hey Root, we want to expand that ticket scope by 5-6 times; still labeled a trivial feature though.

Also them: Super easy ticket for you. Make sure you talk with teams A, B, C, D, E and get their input on the ticket, talk with ____ and ____ and ____ about it, find a solution that makes them all happy and solves the problem too, then be sure to demo it with everyone afterward. Super easy; shouldn't take you more than a couple days. Oh, and half of them are on vacation.

Also them: Hey, that high-priority ticket you finished months ago that we ignored? Yeah, you need to rewrite it by tomorrow. Also, you need to demo it with our guy in India, who's also on vacation. Yes, tomorrow is the last day. (The next day:) You rewrote it, but weren't able to schedule the demo? Now you've missed the release! It's even later! This reflects very poorly on you.

Also them: Perfect is the enemy of good; be more like the seniors who release partially-broken code quickly.

Also them: Here's an non-trivial extreme edgecase you might not have covered. Oh, it would have taken too much time and that's why you didn't do it? Jeez, how can you release such incomplete code?

Also them: Yeah, that ticket sat in code review for five months because we didn't know it was high-priority, despite you telling us. It's still kinda your fault, though.

Also them: You need to analyze traffic data to find patterns and figure out why this problem is happening. I know you pushed the fix for it 8 months ago, and I said it was really solid, but the code is too complex so I won't release it. Yeah I know it's just a debounce with status polling and retrying. Too complex for me to understand. Figure out what the problem is, see if another company has this same problem, and how they fixed it.

-------------

Yep. I'm so terrible for not getting these tickets out, like wow. Worst dev ever. Much shame.

LF work, PST.

Me: "If today's demo to the client goes well,i will get my first cheque"
My server:"If today i stop working,it will be great"
Android Studio: "If i force a gradle update,it will be just fine".

*crying*
Fuuuuuck.Why nothing goes my way when I want it to????Whhhhyyyyy??

One day Bill Gates died and met god. God said "Now then, Bill, i'll show you heaven and hell and you can choose which one you want to go to. Sound good?"

"Yeah!,"replies Gates. So god takes Gates to hell first. In hell he shows him pretty maidens, beautiful landscapes and an endless supply of pop tarts. "So you like it?"he asks him. "Yeah, it's great,"Gates replies.

So god takes him to heaven. In heaven he shows him quite pretty maidens, quite beautiful landscapes and a not quite endless supply of pop tarts. "So bill have you made your choice?" "Yes, God. i want to go to hell," "OK then." And Bill Gates is whisked away to hell.

But it is not the hell he saw before. Here there are no pretty maidens, no beautiful landscapes and no pop tarts. Instead there are all the most horrible things ever. "Aaaahhhh! Where am I!"asks Gates. "In hell,"replies god. "But it's not how it was before!"cries Gates. "Aahh. That was just the demo Bill."

As usual finished the task just an hour before demo meeting. That hour is for transportation. Obviously I didn't test nor rehearse.

As usual, in to 2 mins of demo and greeted by error page.

As usual
1) stay the fuck calm
2) this features was already demo-ed and fixed and went fine few weeks ago
3) what the fuck happen now
4) stay the fuck calm, smile.
5) "ah please give me one minute, I forgot to clean up some stuff while working on new features"
6) shit shit. read the error message and log
7) oh I did refactor some files last week. Reorganized the files and folders for better structure and easier understanding. Thought I corrected every occurrences. Obviously I missed few.
8) ssh to the server while screen is still showing on projector
9) dig into the file quick
10) stay the fuck calm
11) fix
12) refresh
13) sorry all good, so I was saying ....

Well finally it's done for today and going back to office. After all it went ok. 👌

Was working on a Django thing (server-side, so no dynamicness as far as I'm aware?) under a contractor at my company.

Needed a popup to display results of a subprocess, so I asked "We're going to need to AJAX it, right?" and give brief justification. Guy says no - pretty much "Django 10/10 supports this, let me Google". Proceeds to send me a link to a python package that enables using popups as a way of inputting values for form fields. I see as much on the couple of images for the package demo/introduction, so I'm kind of just like "It doesn't look like it's what we need though..." But the guy says to trust him, and implement it.

A day later, after scrutinizing the demo code, and trying to figure out how to implement the package, I go back to him and say "I really really really don't think this is going to work" and give the same justification from the day before. He opens the demo code himself and follows the long trail of confusing methods and stuff.

After an hour of my sitting there watching him read the code and disappearing for 10 minute periods a few times, he comes to the conclusion "Okay you need to understand the code to implement it. But go ahead and use AJAX"

This is abridged and a few other super annoying things have been cut out, but I TRUSTED HIM.

I. TRUSTED. HIM.

Craziest bug, not so much in the sense of what it was (although it was itself wacky too), but in what I went through to fix it.

The year was 1986. I was finishing up coding on a C64 demo that I had promised would be out on a specific weekend. I had invented a new demo effect for it, which was pretty much the thing we all tried to do back then because it would guarantee a modicum of "fame", and we were all hyper-ego driven back then :) So, I knew I wanted to have it perfect when people saw it, to maximize impressiveness!

The problem was that I had this ONE little pixel in the corner of the screen that would cycle through colors as the effect proceeded. A pixel totally apart from the effect itself. A pixel that should have been totally inactive the entire time as part of a black background.

A pixel that REALLY pissed me off because it ruined the utter perfection otherwise on display, and I just couldn't have that!

Now, back then, all demos were coded in straight Assembly. If you've ever done anything of even mild complexity in Assembly, then you know how much of a PITA it can be to find bugs sometimes.

This one was no exception.

This happened on a Friday, and like I said, I promised it for the weekend. Thus began my 53 hours of hell, which to this day is still the single longest stretch of time straight that I've stayed awake.

Yes, I spent literally over 2+ days, sitting in front of my computer, really only ever taking bio breaks and getting snacks (pretty sure I didn't even shower)... all to get one damn pixel to obey me. I would conquer that f'ing pixel even if it killed me in the process!

And, eventually, I did fix it. The problem?

An 'i' instead of an 'l'. I shit you not!

After all these years I really don't remember the details, except for the big one that sticks in my mind, that I had an 'i' character in some line of code where an 'l' should have been. I just kept missing it, over and over and over again. I mean, I kinda understand after many hours, your brain turns to mush. and you make more mistakes, so I get missing it after a while... but missing it early on when I was still fresh just blows my mind.

As I recall, I finally uploaded the demo to the distro sight at around 11:30pm, so at least I made my deadline before practically dropping dead in bed (and then having to get up for school the next morning- D'oh!). And it WAS a pretty impressive demo... though I never did get the fame I expected from it (most likely because it didn't get distributed far and wide enough).

And that's the story of what I'd say was my craziest bug ever, the one that probably came closest to killing me :)

Things you hear from developers 5 minutes before demo to the whole Management Board.

- "... Does this button work... Nope... Oh well..."
- "What the hell is THAT!?"
- "Um... Is it supposed to look like this?"
- "Please tell me you didn't just merge this!?!"

21:30, sysadmin, chatting with my colleagues, when one posts a screenshot of a message he just received from a dev :
"Hello, sorry for bothering you this late but we have a demo tomorrow morning and the app is completely stalled. It fails with the message 'cannot write to <file>, no space left on device'"

I say "I bet that they somehow managed to make their DB grow uncontrollably".

Colleague asks which server hosts the app, Dev answers "one of ours", then adds after a few seconds "wait, do you need the IP of the server? Dev2 should be able to provide it", before finally adding "we use a scheme in <other project> DB actually".

Finally, Dev2 declares that the bug is solved: "There was a loop that caused a DB view to grow constantly and it filled the filesystem".

Me: "Called it".

They cleaned the view: 41GB freed.

My worst experience was at my job where they told me I have to move to a permanent position from 3 years of contracting without a specific offer.
Why is that bad? In my country it means approximatly 40% lower wage.
I came into the job with PHP knowledge when they were looking for Perl on a project one year behind schedule. I learned the language and finished working demo in 6 weeks.
After that, every project that was ever assigned to me was done within 5-15% of the allocated time. I'm not kidding here. My manager loved be, because I was reliable, fast and I even 'accidentaly' solved other problems, like for instance I developed simple syslog search tool and benchmarked zip algos for reading speed, and the fastest had 70% better compression than the algo used before (gzip into plzip on 1-2gb files). That solved anothet problem - syslog servers did not have enough disk space and they didn't have money to upgrade the server.
The number of projects I touched or developed was over 20.
I also lead and developed our team's most successful tool, that every customer was throwing money to buy, while cutting down costs everywhere.
And after three years of that, my manager says that there are no more money for contractors. And the only possibility is going for employment. Without any specific offer! Just 'we cant do this anymore'.
Which I understand, that can happen in corporation, but ffs after all I've done, I expected warmer attitude. Not like 'you may have to leave, since we do not really care'.
I liked the people there, even though the corporation environment was lacking in many respects, but I wanted to help our local branch with everything I could and they gave up on me like that.
So I started looking elsewhere and I found a startup which offered 6 times the money I had in my previous job and promises to relocate me to USA. Which is the best thing that has happened to me that year and second best in my whole life!

oh, it got better!

One year ago I got fed up with my daily chores at work and decided to build a robot that does them, and does them better and with higher accuracy than I could ever do (or either of my teammates). So I did it. And since it was my personal initiative, I wasn't given any spare time to work on it. So that leaves gaps between my BAU tasks and personal time after working hours.

Regardless, I spent countless hours building the thing. It's not very large, ~50k LoC, but for a single person with very little time, it's quite a project to make.

The result is a pure-Java slack-bot and a REST API that's utilized by the bot. The bot knows how to parse natural language, how to reply responses in human-friendly format and how to shout out errors in human-friendly manner. Also supports conversation contexts (e.g. asks for additional details if needed before starting some task), and some other bells and whistles. It's a pretty cool automaton with a human-friendly human-like UI.

A year goes by. Management decides that another team should take this project over. Well okay, they are the client, the code is technically theirs.

The team asks me to do the knowledge transfer. Sounds reasonable. Okay.. I'll do it. It's my baby, you are taking it over - sure, I'll teach you how to have fun with it.

Then they announce they will want to port this codebase to use an excessive, completely rudimentary framework (in this project) and hog of resources - Spring. I was startled... They have a perfectly running lightweight pure-java solution, suitable for lambdas (starts up in 0.3sec), having complete control over all the parts of the machinery. And they want to turn it into a clunky, slow monster, riddled with Reflection, limited by the framework, allowing (and often encouraging) bad coding practices.

When I asked "what problem does this codebase have that Spring is going to solve" they replied me with "none, it's just that we're more used to maintaining Spring projects"

sure... why not... My baby is too pretty and too powerful for you - make it disgusting first thing in the morning! You own it anyway..

Then I am asked to consult them on how is it best to make the port. How to destroy my perfectly isolated handlers and merge them into monstrous @Controller classes with shared contexts and stuff. So you not only want to kill my baby - you want me to advise you on how to do it best.

sure... why not...

I did what I was asked until they ran into classloader conflicts (Spring context has its own classloaders). A few months later the port is not yet complete - the Spring version does not boot up. And they accidentally mention that a demo is coming. They'll be demoing that degenerate abomination to the VP.
The port was far from ready, so they were going to use my original version. And once again they asked me "what do you think we should show in the demo?"

You took my baby. You want to mutilate it. You want me to advise on how to do that best. And now you want me to advise on "which angle would it be best to look at it".

I wasn't invited to the demo, but my colleagues were. After the demo they told me mgmt asked those devs "why are you porting it to Spring?" and they answered with "because Spring will open us lots of possibilities for maintenance and extension of this project"

That hurts.
I can take a lot. But man, that hurts.

I wonder what else have they planned for me...

I miss old times rants...So i guess, here it goes mine:

Tomorrow is the day of the first demo to our client of a "forward-looking project" which is totally fucked up, because our "Technical Quality Assurance" - basically a developer from the '90-s, who gained the position by "he is a good guy from my last company where we worked together on sum old legacy project...".
He fucked up our marvellous, loose coupling, publish/subscribe microservice architecture, which was meant to replace an old, un-maintainable enormous monolitch app. Basically we have to replace some old-ass db stored functions.
Everyone was on our side, even the sysadmins were on our side, and he just walked in the conversation, and said: No, i don't like it, 'cause it's not clear how it would even work... Make it an RPC without loose coupling with the good-old common lib pattern, which made it now (it's the 4th 2 week/sprint, and it is a dependency hell). I could go on day and night about his "awesome ideas", and all the lovely e-mails and pull request comments... But back to business

So tomorrow is the demo. The client side project manager accidentally invited EVERYONE to this, even fucking CIO, legal department, all the designers... so yeah... pretty nice couple of swallowed company...

Today was a day, when my lead colleague just simply stayed home, to be more productive, our companys project manager had to work on other prjects, and can't help, and all the 3 other prject members were thinking it is important to interrupt me frequently...

I have to install our projects which is not even had a heart beat... not even on developer machines. Ok it is not a reeeeaaally big thing, but it is 6 MS from which 2 not even building because of tight coupling fucktard bitch..., But ok, i mean, i do my best, and make it work for the first time ever... I worked like 10 ours, just on the first fucking app to build, and deploy, run on the server, connect to db and rabbit mq... 10 FUCKING HOURS!!! (sorry, i mean) and it all was about 1, i mean ONE FUCKING LINE!

Let me explain: spring boot amqp with SSL was never tested before this time. I searched everything i could tought about, what could cause "Connection reset"... Yeah... not so helpful error message... I even have to "hack" into the demo server to test the keystore-truststore at localhost... and all the fucking configs, user names, urls, everything was correct... But one fucking line was missing...
EXCEPT ONE FUCKING LINE:
spring.rabbitmq.ssl.enabled=false # Whether to enable SSL support.

This little bitch took me 6 hours to figure out...so please guys, learn from my fault and check the spring boot appendix for default application properties, if everything is correct, but it is not working...

And of course, if you want SSL then ENABLE it...
spring.rabbitmq.ssl.enabled=true

BTW i really miss those old rants from angry devs, and i hope someone will smile on my fucking torture

It’s perfect that this week’s topic is “Most awkward video meeting” because I just had two.

The first one was to demonstrate a software process. I had everything lined up and perfectly (or so I thought) ready to demo, kind of like a cooking show. Except the deployment totally failed. I’m still struggling to figure out why several hours later. Luckily I’m getting a second shot at it soon and they weren’t mad.

Then I went and took a shower. Checking out my eyebrows in the mirror, I decided they were getting overgrown, so I took out a trimmer with a guard on it to thin them out a little. Except for some STUPID and INEXPLICABLE reason I TOOK THE GUARD OFF right before I shaved off the right eyebrow almost to the skin! I couldn’t believe it. It was like my brain sabotaged me knowing I had an important video call coming up where I might be making a ton of money if all went well.

What the hell was wrong with me?! What could I do?! I stood there cursing my existence and making plans to become a hermit in the desert. Well, I couldn’t do that. And I still had a video call in a few minutes. I couldn’t just leave one eyebrow unshaven. So, I did the only thing I could do. I cropped the left one and tried to make it match as much as possible.

It wasn’t terrible, but it was definitely noticeable on HD video and certainly up close and in person when my wife and kids returned home soon. I started panicking and wondering just how I could literally save face after idiotically mutilating my face for all to see.

Then, I got an idea.

Now, I’m a manly man. At least, I consider myself to be. I don’t shave my eyebrows for any kind of metrosexual caché. I do it because if I don’t the grease from my face that gets into my brows eventually transfers to my glasses and then I get annoyed by all the smudges. As a dad who was never comfortable when my girls wanted to put makeup on me, I suddenly became aware that their massive trove of makeup “stuff” might just save my bacon!

So, I snuck into their bathroom and, lo and behold, the exact right shade of color for my missing brow brooms was sitting right on the counter. I dabbed a little on each finger tip and carefully (oh so carefully) tinted the area mangled by my apparent dementia.

It was actually pretty amazing how it all turned out. Even on HD video it was undetectable. And when the true test occurred…i.e. my wife and kids returned home and I had to talk to them face-to-face, absolutely NO ONE was any the wiser!

Now I gotta figure out how to keep up this charade for at least a week, maybe two. I hope they don’t put that makeup tray away somewhere where I can’t…oh, wait, they never put anything away. I’m good.

tldr:
first year in college we programmed 24 hrs straight to fix somebody's mess before the deadline. Decided not to screw him over, instead he claimed to have done everything and we failed the assignment.

Long version:
var group= new[]{"Mike", "Gavin", "Gus", "I", "Ben" };
var client = "Jack"';

First year of college we had an assignment to make a web program for somebody.
Ben wanted to join our group and he already knew a client so we let him join.

After joining Ben wanted to be project lead, but we already decided Mike based on his experience.
Ben claimed to be much better in every way than Mike at and kept coming with stuff the following weeks why we should make him project lead. He kept pointing out when Mike did something wrong and he even came with an audio file where he clearly made jack say that he wanted Ben to be project lead .
After that we were all a bit pissed and told him that he should get it in his head that he was not going to be project lead and just start working on his part of the assignment.

We also found out that Ben was a documentation addict, what we could write in a small paragraph, he wrote a whole page about it. No joke, I rewrote a page of his in 5-6 rows with the same information in it.
No problem you thing, wrong! Because of this he kept bothering us arguing and claiming that our documentation was wrong because it was to short.

In the week of the deadline we asked Ben if he was also done, and told us that he was done for a while now.

The day before the deadline we came to school thinking we only had to do some merging and finishing up documentation.
Then we found out that Ben has almost nothing, and what he had the IDE was screaming that it was incorrect, spaces in Id's and css class names for instance. A really good programmer, my ass!
We were so pissed off at this point, but we had 24 hrs and needed to come up with a plan to fix it.

We decided that Mike and I were going to fix Ben his shit in the coming 24 hrs and Ben was going to make our last bit of documentation because we would not have the time for that, Especially if we had to argue with him like we had to do for each bit of documentation. Gus did not have time and Gavin could not program on his own yet, he wanted to help, but helping him help us would cost more time than we had.

We all went home after that and Mike and I started to program 24 hours straight while in a Skype call, making what Ben had 2 months for. Shortly before the deadline Mike looked at our finishing up documentation received from Ben and told me it was "Okay" and zipped everything up and uploaded it to school with a few minutes to spare.

After that we thought everything was good, we made Ben's part work and delivered it in time. We also decided not to throw Ben under the bus, because this would hurt all our grades because we did not work good as a group since we should have noticed it earlier.

A few weeks go by till the assessment.
The assessment start with asking if we want individual grades or as a group when you all think you did equal amount. We choose as a group, because if we chose individual not only Ben but also Gavin would get a lower grade and we did not think that was fair because he tried so hard.

We demo the product and the teachers are positive. When the teachers start about the documentation, the first thing they tell is that they found something interesting in the documentation, and they read it to us:

"I, Ben, have made all the documentation because my group did not want to."

That was so far from the truth, we all did make our documentation about the parts we made. Yes he did do overall a little bit more because every single bit of documentation we had to argue with him, so every time he volunteers to make it, we would all agree. And he made Mike's and i's last bit of documentation.

Telling the teachers on that point would not have mattered, it would only have hurt is in another way, so we did not and all failed the assignment. And we all felt like to strangle him.
This is now a few years back, but i still want too.

Me and my developer friend worked with my ex-colleague with this fitness directory website because he promised to give us {{ thisAmount }} upon the {{ completionDate }}.

He was my friend and I trusted him.

It took me weeks of sleepless nights building the project. I had a full-time job that time, and I worked on the project during evenings. All went well, and as we reach the {{ completionDate }}, the demo site is already up and running.

A week before the {{ completionDate }}, he hired his new wife as the COO of the startup. It was cool, she keep noticing things on the site which shouldn't be there, and keeps on suggesting sections that has to be there. I was okay with it, until I realized that we are already a month late with the deadline.

Every single hour, I get a message from them like, "it's not working", "when can you finish this feature?", blah blah blah.. and so on.

I got frustrated.

"I want my fucking life back", I told them. No one cared about the {{ completionDate }}, the sleepless zombies they are working with and our payment. They keep on coming up with this "amazing" ass features, and now they are not paying because they said "it's not complete".

Idiot enough to trust a friend. I was unprotected, there was no legal-binding document that states their obligation to pay.

My dev friend and I handed over the project to this web development company which they prefer, and kept a backdoor on the application.

I kind of moved on with the payment issue after a month. But without their knowledge, I kept an eye on the progress and made sure that I still have the access to their server, DNS, etc..

BUT when they announced the official launch on social media, I realized that I was on the wrong train the whole time.

They switched to a different server.

They thanked all the people involved with the project via social media, EXCEPT me and my coding partner who originally built the site from ground up. A little "thank you" note from them will make us feel a little better. But, never happened.

I checked up the site and it was rewritten from originally Laravel 5 to CodeIgniter 1. That is like shifting from a luxury yacht where you can bang some hot chicks, to a row boat where your left hand is holding the paddle whilst your right hand is wanking yourself.

I almost ran out of bullets.

Luckily, CodeIgniter 1 was prone to SQLi by default.

I was able to get the administrator password in plain text and fucked with their data. But that didn't make me feel better because other people's info are involved.

So, I looked for something else to screw with. What I found? A message with the credit card details.

Finally, a chance to do something good for humanity. I just donated a few thousand dollars to different charity websites.

Sent my changes before everybody for code review, got git blocked because today was demo day, and ... And asshole guy merged his own PR without code review. That conflicted with my PR. I am going to start posting the shennanigans of asshole guy from now on, just to have a record of his stupidity.

So, with couple of new people in senior managerial roles, pink slips started flying left and right before the holiday season. That didn't happen before in the company. It's still relatively small and when people left that was for better paid or more interesting work.

While I can understand that from the business perspective and especially for a few who might have been considered dead weight (devs and other roles), I have a serious problem with the way it was handled. It's one of those 5 minute notices. If we weren't remote, I guess escorting out by security would follow.

Most recent person to go is actually one of the most senior devs at the position that became redundant over time, as it clashed in the "pyramid" with another dev. He was involved in many aspects of the product and greatly contributed to the overall success during years of hard work, i'd say maybe more than any of us.

He didn't fuck up anything major as far as I know, his services were just not needed anymore, compared to the other guy. Saving money. I get that.

At T-1 day he prepared a demo of his project. Meetings, Slack, everything as usual. Next thing we got was a "we wish him well in future endeavours" e-mail.

What I find most disturbing is the fact his account was removed immediately, and then we were asked to get any files and anything else we might need, all over personal communication channels (private e-mail, Skype etc.) because he was locked out of all company accounts.

I seem to have have survived this year. One thing they have definitely achieved, based on some off the record chat and some public updates, tweets etc I can see, is for many of us to start networking, polishing CVs and generally stop giving many fucks about the company and the outcome.

I've myself started brushing up on some new skills (stacks) and some old ones (algorithms, etc.) I may need any day now, as it seems.

If they can basically tell "thank you and fuck off" to one person maybe most involved with the company growth, with zero dignity and respect for the person, then fuck them.

Completed the coding for my story .One week later just a day before the demo,I am being told that the requirement has changed.Need to do from scratch and I have demo for it the next day ... 😶

Hi all,

This might be a long post so bear with me. I work for a company and there was a project for a huge client. I'm junior in skill (been programming for about two years) but my job title doesn't reflect that. Anyways, I got the design about a month ago but I was on deadline for two other projects so I couldn't pick it up until last week Wed. Ironically, that's when the final design was delivered & told me it was due next week Wednesday. I built it as fast as I could. Finished mobile but for some reason, this last part for desktop just wasn't working out and it just so happens to be the most crucial part of the piece. (I was also sick the entire time and didn't sleep for the last two days nor did I eat). I was supposed to demo it yesterday but I still needed to make a few updates and the project coordinator took me off the project & gave it to a dev with more experience. This has never happened to me before. I'd go as far as to say this is my first big fuck up. I've always delivered on deadline and I'm taking this pretty hard. Has anyone been in similar situations? What do I do? Any advice?

Client : you are hired as a developer.

Me : we need more developers as there's more work and less time.

Client : Ok, here's another dev

(Meanwhile me doing my work...)

ON THE DAY OF DEMO :

Me : Here's the demo.

Client: it's incomplete, where's more work?

Me: that's the part of 2nd dev you hired before

Client : I don't care, I fucking need a work!

Me inside: (Why the fuck would the first dev becomes a task/team manager just because is the first one to join the project! Arrrgh!!! Hire a fucking scrum master to manage your fucking tasks/team, am just a fucking dev! )

In the past: "Alright, have the day off, so can do some serious work (work on my game project). Let me just check my mail first... And a cpl of sub-reddits... And see if there are any updates for Unit3D, or any interesting forum posts, or new assets on asset store that look nice... And check some online newspapers just to see if anything is going on... And check if anything new has been posted on slashdot since I last checked 5 minutes ago (nope)... And maybe see if there's any updates to Sublime Text or new useful packages that can help improve workflow... Ooh came across article on how to improve workflow... Hm someone mentioned a new task-management system in comments, gotta check that out... I'll just sign up for a demo-account and... Hm but what if there are any better ones? Better google for comparisons. Wait, isn't there a new episode of Silicon Valley today? Gotta see that first, no time tmr. Hmm also new episode of Archer, and American Gods. Better get watching these out of the way first, or I can't concentrate... Ah, wait, it's dinner time, no point starting anything until after that."

Now: All of the above, plus "I'll just check devRant real quick before I... hmm... interesting rant... *scrolls and reads rants and comments for 3 hours*"

How am I supposed to get any work done? :_(

It's been two months since I've left my previous job, after 1.5 years. I never had the feeling my boss trusted his dev team, since he was checking up on us regularly, even though we had planned out a sprint and work for us was "clear". I say "clear", because every single feature on this project was pretty much half-baked, since they were just ideas our boss/PO (same person) on the spot and were labeled as "the next big thing" without every properly writing them out as user stories. Every demo came with a bunch of criticism, because features weren't implemented "as he imagined", because what do you know, the user stories weren't properly described anyway. Bringing that up as counter-argument also made him angry every time, so that didn't help much either. The launch of the platform was also postponed every time because of vague reasons, so that didn't make the project any more interesting either.
It took a while before I got sick of this of this pretty hopeless situation and toxic environment. Mind you, it was my first job since I graduated, so I was a bit naive thinking the working environment would improve and aforementioned company issues would be resolved over time. Eventually, I ran out of patience and motivation, so I finally bit the bullet and handed in my resignation letter.
From that moment, I at least had an end in sight, since I was still obliged to do my four-week notice period, which felt like an eternity. The borderline childish and sociopathic behaviour of my boss didn't make it any better (e.g. checking up on me even more, more mistrust, randomly accusing me of ruining the working atmosphere because I shared a meme with a colleague of mine and didn't involve him, going lunching with all of my colleagues but explicitly asking me to stay at work, ...). Being forced to work from home the last 2 weeks as part of the country's lockdown measures at least helped my sanity a bit, since I had the comfort of my home office and not the frequent "looking over your shoulders to check if you're still working".
By the last day of my notice period, I was bitter, exhausted, lost confidence in my skills and had completely lost my joy of being a developer. I had to physically meet with my boss one more time to hand in the company laptop. He thanked me for my service and said that we'd keep in touch. I hope I won't keep that promise (he made a lot of false promises before, too), because I'd rather never encounter him ever again. It felt like a huge relief to finally close the door of this bad experience behind me for good.

Now, 2 months later, I've got a new job and rediscovered my joy for coding, mostly thanks to the complete opposite of a toxic environment here, management which actually has respect and faith in me and a challenging but fun project. My mental state has made a complete turnaround compared to two months ago. I have absolutely no regrets of switching jobs. If only I had made that decision sooner.

Our approach is to get a loose feel for what the client wants, lift some visuals from Theme Forest then spend the next few weeks persuading the client to use our crappy server rather than their preferred AWS solution. Then once the project is behind schedule we break the work down into disparate tasks each of which gets a single line brief from the PM (such as 'create admin' or 'do css'). These then get assigned to different devs with no consideration of their skillset. The PM is available for 10 mins every day to answer queries, the rest of the time our devs are expected to work autonomously. Meanwhile we'll tell the client that we're back on schedule and arrange a demo for an impossibly short deadline. We have the mantra ”dont worry about it” which the PM uses to quash any dev's concerns up until the day before the deadline at which point we'll swap some devs on to unrelated work whilst others concentrate on getting "just the pages the client wants to see looking right" (we have a policy of making it look like it works before it actually does.) Following the demo we will announce all the missing features we had forgotten about from the initial undocumented agreement and set the project aside whilst we service another client.

So I was setting up ELK (Elasticsearch, Logstash and Kibana) all in one EC2 on AWS today for demo purposes. I had everything prepared. Elastic IP, correct security group rules, etc.

I figured I would just do quick test before writing filters and templates if I can access Kibana. So I started service for it and tried to open it with Chrome.

Timeout.

Checked config file. Compared it to documentation. Seemed good but changed some things just for sake of change. Restarted service.

Timeout.

Reverted changes I've made in config. Restarted service. Curl on localhost. It work... OK. 😐

It took me half an hour but finally I figured it out after I took my phone and opened it from there. It was working from the beginning. Stupid company network was for some reason blocking this connection. Fuck! 😡And I was restarting that poor service like crazy trying to fix something that wasn't broken.

monday.com: our manager has been pushing for it for weeks. We barely got any time with the demo before it expired and the company took forever to get licenses.

Now that we're on it ... this thing sucks ass. It hijacks all the browser keyboard shortcuts. You can't use Ctrl+F or Ctrl+L .. you can't even right click.

This is the worst project management software I've ever seen. It's amazingly even worse that Jira. I wish we had just gone with Redmine. It's free and not garbage

"Hey guys we originally set the demo date to August 5th and thus far I have not seen any previews before that, what's going on here?"

Ok see, that is the kind of thing that I would take to me own lil broken heart IF:
1 It was coming from a product manager at where I work

2 He would never get any sort of updates or would just plain not know about us

3 He would be I dunno....fucking paying us?

This is the thing, a friend offered the chance to help him build a product for a business man somewhere down in the land of tacos. Being in a "fuck it" mood and not wanting to say no since it sounded interesting enough I said yes. The "owner" said that he would not be able to pay since he already had hired a team of developers before that did not deliver and as such he was instead offering a part of the company.....sounds familiar?

Not wanting to let my friend down, I told the owner that I would help just as long I get complete CTO power over the product and not crying about the stack being used or ME NOT GIVING THE PRODUCT MY FULL ATTENTION BECAUSE HE WAS NOT FUCKING PAYING.

He said ok.

Of course he did not like it, but he said ok.

He has been asking for the code, the platform, demos and a bunch of other shit which I continue to refuse since he has not offered me or my boy a copy of the legal documents that we require.

Him: "You will get them soon enough, I still need to see the product just to make sure everything is ok"

Me: "You wouldn't even know where to begin looking unless you have a third party that could verify the code, last time I checked I was to be the only one good for this"

Him: "Yeah and you and <friend> are, but I just need to see the product"

Me: "I send you videos and demos, sorry dude, but no binding document == no code. I know you think I am young, give me some fucking credit because this is not my first rodeo"

Him: "I am not trying to play you or anything, you can trust me"

Me: "No, not really. Talk to me about this when you get the documents"

Him: "Well its cuz this is taking too long...."

Me: "Tssss I know!!! It sucks right? Want a good product, built with all the bells and whistles and YOU DON'T WANT TO PAY? guess what dude, I do have a full time job, your product gets my minimal attention, right there at the bottom next to taking a shit, meaning that I will give your product the same time and attention as I would going to the throne. Aye don't feel that bad, I normally take about 1 hour on the shitter, you get that for fucking free."

To be fair ladies and gents I normally don't just explode on people like this. But I just can't fathom not paying someone for a rather large software product, with only a promise that "it will sell" and then telling them to hurry up.

Far as I am concerned this product will flop, but he seems to think it is the next big thing(of course).

He can go choke on some chode.

Fucking prick.

I have 2 juniors working under me that i need to assist with work. I dont mind helping at all because i was in the same boat. The problem is.. 1 of the developers asks questionsnon the last minute (a few hours before demo of weeks sprint) telling me she doesnt understand and i spend all week asking her, if shes okay, does she understand, does she need help, is the work too much, should we take a few hours to rerun through things and even while explaining things after planning, she just says "yes" and "i understand" and has the body language of "i want to get away here" ans doesnt even let me finish my sentances before interrupting mentonsau "yes" or something in that line to end the conversation. I dont know what to do because its going to start affecting my work and the ammount of work i can take for the week because i have to help her do the work on the last day and finish it just so she can look like the sprint was successful.

Any suggestions to help me help her? I really want to see her succeed but i can tell she isnt taking it as serious as she should or putting in as much as she likes because our company is very flexible woth everything and i don't want to get a project manager vibe around her

Just set up my own IoT device for free thanks to the guys at Losant.

I met them at codestock a couple years ago. They were running a workshop with some Adafruit boards and at the time I had never seen anything like Arduinos before. I was fascinated. So I walked up and asked about it. They said they sold the chips just to demo their IoT stuff. I said I'd buy one. I then waited like 40 minutes for them to get their card reader working. They gave up and handed it to me, gratis. That started my dive into electronics from programming.

Few years later, I needed a remote temperature sensor to make sure a certain unattended appliance never got below freezing. I suddenly remembered that kit (now buried under my heaping stash of electronics), followed the tutorials, and had the exact thing I needed up and running in like a few hours, with all the bells and whistles I could want. And for free.

The icing on the cake here? I went on their website to look at a kit to replace it. I found one with even more goodies in it, and the entire kit cost less than the cost to go to adafruit and buy just the board alone.

Thanks Losant for being awesome. If you wanna do IoT anything, look em up.

Anyone ever just get seriously discouraged about peoples view on how easy/difficult it is to code?

A client has requested that they want a system built so they can create surveys and send them to people via email all in one tool. Im not a good front end designer but I know how to develop it. So they hired a designer to send me screen mockups and I will develop them. Easy enough.

This is where the bullshit starts... The designer was supposed to send me the V1 designs last Friday so I could begin building. I told them that I could have a rough version of some pages (with placeholder text and whatnot) ready for the following Friday (tomorrow). However the designer didn't send me the designs until 5 minutes before we were all meeting yesterday. We were all going over the designs in the meeting and this is how the conversation went (roughly):

Client: Wow these designs are amazing, I cant wait to see what it looks like when it functions. Are we still going to have a demo version by Friday?

Me: Well seeing as I just got the designs today, Ill have to look them over and get back to you on a new timeline.

Designer: Yah sorry about the delay, designing can be tricky sometimes.

Client: No worries, I understand. However I want to stick to the same timeline and have the demo by Friday.

Me: Well as I said, Im only getting the designs now, this is the first time I'm seeing them so I'll have to look them over and re-evaluate.

Client: Yeah but the designs are done so it will be easy for you to code it by then. It's all right there in front of you. I need to run, excited for Friday! Bye!

Designer: Bye!

Me: ...........

-- I know its partially my fault for saying I could have a demo done by Friday assuming the designer would have it done on time but COME ON. I hate when people say something is easy when they have no idea what it entails or how to even do it.

Me - "Talks to client about his deliverable"

Him - So when can we show a demo?

Me - On thursday we could show a totally working deliverable.

Him - "Really on thursday? i was hoping to get it done for tomorrow"

My mind - *Dude. do you even know how much time does it takes to finish the latest changes you just asked me today? i mean probably we could get it done if you weren't so cheap at the proposal, you know, when I told you we would take longer if i dropped the price. And I could have a couple more devs working here so we could had the finish product a week ago, and still we are on time... so WTH dude *

Me - No, sorry I wouldn't dare to show you a half baked demo. But ill try my best to show you before that day.

!rant

So this happened sometimes ago.
We ,primarily, makes accounting software with industry specific integrations of manufacturing,etc. A soon-to-be new client visited our office for a meeting and a quick demo.
He's not satisfied with his current software and wants to switch but keeps bragging about how his current software operates and it's easier for him.(Only because he's been using it for years.)

NC : We used to do like that. Blahblahblah.

My Boss : Well, I built this new office last year. I visited "Taj Mahal" just before that. It was so beautiful. But it doesn't mean I should build a "Taj Mahal" for my office because it's not practical. Same goes for this software.

The client has a great sense if humor. He burst into laughing after 5 secs of silence. Not a single word of his current "system" after that.

PS : My first post.

My code was replaced with "return null". I caught it ten minutes before demo.

I get that reverts happen - I just wish somebody told me! Git power user for the win! I revert your revert sir!

Demo of a feature had to be canceled just minutes before the meeting. Entire environment is hosed and don’t know why. Also, the feature to be demonstrated turned out to not be working before the environment stopped working, so we now have more time to shift to another solution. Win?

Rant and opinions wanted. Its a long one.

I have been working on a project for a month and a half. For the first week I was requesting designs that I got about 2 of out of 15. For the next week and a half the designer was on holiday so I couldn't do anything but delivered a few more designs once he got back.

This takes us 2 weeks in already. I have other things to do as well so at the same time I work on support tickets and some bespoke development coming in.

I get given 2 or 3 more designs and can't get anything else out of the designer after waiting a week so I have to design everything myself as I go and build it. Something I have never done before.

We are now 3 and a half weeks in. My boss randomly tells my pm it needs to be demo ready the next day. I work furiously to hack something together. It works but key functionality is missing.

I move house and work from home for a week and a half. I do my best but the project is full of bugs and the CSS is horrible because I didn't know what I was making at any stage. It is therefore CSS rules repeated in IDs everywhere.

My colleagues join me on the project because my boss has decided to try and sell it tomorrow.

They run through it and find all the bugs left from me working furiously to get things done quickly. Things like no search pagination and missing validation.

My boss is now pisses at me because the project is not finished, my colleagues are now all working on it. Throughout it all he knew the designer was not delivering me anything and that I was struggling.

Am I in the wrong for writing shit code that came about because I was coding with no idea of what the finished project should look like? Is he in the wrong for dumping this on me and just letting me get on with it even though he knew there were no designs?

Btw I am just finishing a 1 year internship and before this have never done web dev before.

Discuss.

Let me just say that I've been playing whack a mole with a new feature for while now. And it's becoming very tiring.

TLDR; CTO is changing the way we're going to implement this, every other day.

June 1st,
CEO: let's implement feature AAA,
CTO: we're going to have a call with Andy to tell us all about his product that will make this super easy, call will be June 4th.

Days before June 4th,
Me: Researchs product X, makes demo works flawlessly.

June 4th,
Call all good, few tips from Andy. We come to the pricing section of Product X

CTO: this will not work, pricing doesn't fit on our budget, fair enough.

June 7th -11th
Me: research altenative approach. Makes second demo.

CTO: Works good, seems to have too many moving parts, let's have call with Bob to check Product Y. It should make our lifes easier.

ME: Geee, ok let's check it out.

June 14th,

Call with Bob, all good, product has a fair price, stuff is experimental.

CTO: let's use Product Y, and just use what we get from their api now, and worry about changes later.

Me: Hmmm, that's a bit risky, but ok, you the boss, right?, starts again new demo. API doesn't work as documented.

Lots of trial and error to figure out how the api is working now, finally demo works well,

June 17th,

API changed, now it works as documented, (expected as it is experimental), previous demo doesn't work anymore.

June 18th,

Redoing research. inputs are completely different from Product Y now, need to redo all that is working and do and a lot more of research.

Go live is scheduled for end of next week, I hope that the API is stable now, and that I get to go live on schedule.

It is funny to see, that it would probably been the same if we just waited on the API to stabilize, and check the pricing section before choosing a product? Who knows.

Anyways, I actually feel happy that over the years I developed the patience to work with ever changing situations like this one.

Current I’ve been assigned 5 pages web design, but my coworker only been assigned two simple html and css task. We got same two weeks to finish it. She joined three months before me. After the task done, my manager ask her to do demo to team, she never mentioned me, and today’s stand up, big team manager said thanks for her demo and work, she didn’t mentioned me too… And now everyone contact her instead of me, and then she told me what others said later.
I feel she’ve been take credit from me..
should I talk with the manager about this? Or I should just quit the job?

Was in a university group project and had to make an angular momentum measurement device. An hour before demo voltage on one of the pins was still a bit too high. Friend drove to Chinatown not too far away from campus and bought a pack of the cheapest batteries. Plugged the cheap batteries in, the voltage was just spot on. How awesome was that!

Yesterday, I had to set up a demo environment for a project, we are working on.
Everything was okay, frontend loaded, connection to backend is working, database is connected.
10 minutes before I wanted to leave for my well deserved weekend, PO came over: "I can't play any video, I uploaded"
Okay, couldn't be a big issue, it worked when I added this functionality 3 weeks ago, just before my holidays.
A bit under pressure, my girlfriend Was already waiting downstairs, I inspected the database and realized that a table Was not properly filled.
Checked the backend and everything seems fine, so checked the requests from the frontend and realized that the request was almost empty.
So some code, building the request body had to be wrong.
Already 10 minutes late, with a lightly annoyed girlfriend waiting for me, I found the issue but couldn't recognize that I wrote these few lines. A quick check of the git history showed, that my colleage changed my code during my holidays, so I just reverted everything.
After commit and deployment, I called my colleage and told him that I just reverted his changes.
"But now my feature is not working anymore, I had to change it like this!" he answered. I just responded that we will talk about that on monday and look at it together. While I hurried down the stairs, I was thinking why the hell somebody just changes stuff without checking if it affects other functionalities?
This should be basic knowledge for every dev, that if you change existing, working code to make it work with your feature, you have to ensure to not brake anything.
If you can't do that, then create a new function to handle your shit.

In the end, my girlfriend had to wait 30 minutes, because of 4 lines of codes, someone just changed without thinking what else could happen...

Stupid timeline, there is this company I was working for. It was sub-contracted by another company to do a government project. Government only pays after you deliver in my country. It was a complex system I must say. We were to work with my buddy on this project...now the timeline we were given were not feasible since another company had been given the same project and were not able to deliver. We had a meeting and discussed with our CEO about the project timelines. From the workload the feasible timelines were around 8months if we were to work as two devs. My CEO said that was not going to happen.. The only timelines that was allowed was not more than 3 months. So we suggest use an existing system to customize. .The meetings with the clients were to be weekly demos. So we choose to go with google docs api for the document management part. We were working around 20hrs a day to be able to achieve the target deadline..we management to complete the project within the given timeline..on the commissioning date of the project we faced a government panel and this was my worst disappointment. At the point of login we had to use Google email for business to obtain the API. Just as I was logging in the guy noticed and yelled. "Is that google account ?" and I replied yes..and he said "no need of proceeding since it will be of no use and they won't approve the system". That was my lowest moment in programming. I thought I had done the best project in my life as a programmer only for stupid man to declare my project as null. I felt like calling him son of a bitch but I knew that would have made me more angry...i just walked out. I went to the toilet and all I did was cry for the first time as I can recall.. My question was I was doing weekly demos. Why didn't they raise any questions by then so as to change the entire system??? Later after that demo we went and discussed about the issue and there was time extension. I redid the project using 'open office' but just before deploying the system I got a better job. I wasn't feeling like working on that project anymore. I want to release that project as open source. Recently after one year they haven't yet deployed the system. They are calling for my help. And I don't feel like helping after the humiliation...

Make your code available for your team members, please.

So we're working on this robotics project using ROS, a framework that enables multiple nodes in a network exchange their functionality among each other through tcp connections. Each node can be implemented and executed on your own machine, and tested with dummy inputs, but in collaboration they make a robot do fancy stuff.

The knowledgebase needs data from the image processing unit, providing this data to others with semantic context to high level planning, which uses this semantic data for decision making and calling the robot manipulation node with meaningful input, to navigate the robot's components in the environment. We use a dedicated machine, which pulls the corresponding repositories and is always kept configured correctly, to run each node, such that everybody has access to each other's work when needed.

So far so good. We tried to convince the manipulation guy (let's call him John) to run his code on our central machine, not a week, but since the first day, 5 months ago. Our cluster classification has been unavailable for 2 months, but my collegue fixed that. We still can't run the whole project without John's computer. If his machine blows up we're fucked.

Each milestone feels like a big-bang-test, fixing issues in interfaces last-minute. We see the whole demo just moments before our supervisors arrive at the door.

I just hope he doesn't get hit by a truck.

I don't often have reasons to rant, but today is the one.

We had a deadline to finish a project, because today people are being trained on it. I've been working my ass off on it for a year now.

I "finished" about 2 weeks ago, meaning QA could start for real 2 weeks ago. As you can imagine for a project this long, there was bugs. Lots of them.

We did our best to fix most of them, or find work-arounds we could use during the demo.

Let's just say it isn't going great so far. We have several known bugs, which at some point may crash the app, a very low confidence in the fact that it's going to work well.

Oh and obviously the client is one who already use heavily the solution. Today we figured we never tested on a device with 0% disk space. Files are cut partway because of that, and obviously things crash.

I have a feeling there will be yelling sometime soon.

Right now I'm enjoying the calm before the storm, with coffee in hand.

Why do people still continue to promise dates to clients, after me telling them for 5 years not to do that?

We are a 2 devs team, with 11 apps on 2 platforms, 2 back-ends (one is legacy) and obviously our marketing site, which doubles up as e-commerce. We just can't promise anything, because any emergency reduce our development bandwith for new features either to 50% or 0%. There are so much known bugs it's not funny anymore, and we don't even have time to solve those.

To add insult to injury, at the beginning of the month, the SaaS provider for our legacy back-end (which have not been maintained for 2 years now) decided we had to update to PHP7.1 before 1st October. If we don't do anything, on monday this thing is broken. I hate that thing, and I hate having to maintain it even though I was promised I wouldn't have to ever have anything to do on it.

Monday will be "fun"...

I'm working on a pretty big dataviz project. There was supposed to be a deadline at the end of the month for a first full demo.

This morning I wake up to an email from the client saying the deadline moved to next Monday and they just "forgot to tell me before".

Also, the dev from the client's company who is supposed to prepare the data/API to be used for the project said he'll be able to send something at the end of the week.

They're clearly not going to get what they want for Monday...

OK, so, I see PY files shared on GitHub. All I know is, it is code for certain apps or pages. I download SEVERAL DIFFERENT PROGRAMS trying to get PY to open. Some didn't work, others were in Console and not Form. I asked for help on the Forum, how to open it, they do the same BS; gave me a Console app that just stays black for less than a second, and closes. I ask for a Form version. They made the excuse that it wasn't a program like I was thinking. They rudely tell me to be polite, but something like this IS GOING TO HAPPEN if they can't get their crap working. Eventually, after I TOLD THEM I WAS FURIOUS, THEY HIDE MY QUESTION FOR 10 MINUTES. When I replied, I DID NOT CUSS, I REPLACED LETTERS WITH ASTERISKS AND SYMBOLS, AND STILL GOT SUSPENDED, FOR A MONTH, AFTER TELLING THEM I WAS FURIOUS.

On the other hand, I was using Audacity. I upgraded and a plugin stops working. I thought they messed something up, so I wait using the outdated version for the fix for a few months, and so a few months later I update again, at this point I was a little upset; 2nd update and it still doesn't work. After the 3rd time, I thought they just didn't want to take the time and fix it, as people probably would have reported it by then. So I rant on Audacity's Forum saying they didn't fix an error, showed them screenshots in all versions I got and the 3 newest ones show an error. THEY TOLD ME WHAT WAS WRONG! I was trying to run a 32-Bit plugin on a 64-Bit version! I downloaded a 32-Bit version of the newest Audacity, and the plugin worked fine.

Python could've done what Audacity did, but, "No-o-o, we enjoy banning Winston when he is peed off!" And just so, the Suspension ends a day after my Birthday.

I might just ask when I'm back on, "How to remove my user off this Forum", so they can say "I can't", and flag it as malware because I almost no longer want they're help, and CAN'T GET AWAY FROM IT.

Freak you in the butt, Python.

PS - If anyone knows how to use Python files in Windows 10 or know a free, non-demo program that will more-advancedly edit, save, open PY files in a Form, please, give me the name or link to the software, program or app in the comments.

Before anyone says anything, this page says "Rant", so don't ban this or I'm deleting my account. If this isn't a "Rant" site, please tell me, and/or rename this site.

That is the reason I came here, just to get my frustration out.

fuck this shit.
fuck the pile of arcane shit that is ARCore.
fuck the fucking pile of overcomplicated shit that is mapbox.
fuck the idiotic frankensteiny steaming pile of shit that is "arcore+mapbox lifesized maps unity project" or how is it called.

fuck this retarded scammy culture when a company is doing meetups with investors before even having a working prototype.

fuck this stupid fucking culture where there's no time for some actual, sensible, creative work, just grab these two repos from github and ducktape them together and we'll call that our demo which we will present to inverstors.

fuck every fucking molecule of this fucking world.

i just wanted to be creative. to CREATE stuff. CREATE, not pile up dumb half-baked nonprojects made by someone else on top of each other until the smell is too strong for anyone to see if it's actually reasonable or not.

i wanted to create stuff. make games. design and make them. actual interesting ones which have actual value (because fuck the retarded gaming industry who's imagination doesn't go beyond "u a dude who does pew pew to other dudes", but that's a different rant).

fuck this disgusting, retarded, idiotic, boring, lonely, cold, lobotomizedly stupid world where the only way to succeed is a shitty pile of shit scammy scum.

fuck me for not being able to learn how to be scammy scum, so I could be successful too.

Okay I'm completely lost on how to do this so I'm about to write the most complicated work around I've ever thought of just to get this demo done before my internship ends next week

I both love and hate the BBC microbit

P.s. Anyone know when they'll be commercially available in the U.S???

So my current company held a dev showcase last week. It was an event to show the different projects/tech stacks that different teams are working on/with. There's about 12-14 teams in our company. My team lead and I were brainstorming ideas on what to show on our booth. And I told him, I have an Intel RealSense developer kit that we can use. Anyway, fast forward to the day before the event, I was still developing our app/game for the booth. Just an emotion detector and you have to trick the app with your facial expressions. (Weird and fun, I know). The head honcho walked past the team lead and I and looked over the demo that I was playing around and he said that: "That's not work. You're wasting time again."

We were both irritated by his comments because he's one of the top dogs in the company and he surely knows about the event. Also, it's our way of showing to him that we're flexible in doing fun stuff instead of just enterprise and internal systems!

What a fucking kill joy!

So, apparently my client was about to demo the web app that I've just built to many potential users. The audience/users however is an top notch CEO's, and management from various companies.

Oh god, I hate working with them. They just so lousy and perhaps ocd or smtg idk. They literally changed the concept in the middle of development, and event CHANGE THE NAME of the company days before the demo. God, I hate it.

Should I update the repo with dickbutt pics and deployed it asap? I've prepared the branch btw. Its just a matter of click now lol