I'm trying to sign up for insurance benefits at work.

Step 1: Trying to find the website link -- it's non-existent. I don't know where I found it, but I saved it in keepassxc so I wouldn't have to search again. Time wasted: 30 minutes.

Step 2: Trying to log in. Ostensibly, this uses my work account. It does not. Time wasted: 10 minutes.

Step 3: Creating an account. Username and Password requirements are stupid, and the page doesn't show all of them. The username must be /[A-Za-z0-9]{8,60}/. The maximum password length is VARCHAR(20), and must include upper/lower case, number, special symbol, etc. and cannot include "password", repeated charcters, your username, etc. There is also a (required!) hint with /[A-Za-z0-9 ]{8,60}/ validation. Want to type a sentence? better not use any punctuation!

I find it hilarious that both my username and password hint can be three times longer than my actual password -- and can contain the password. Such brilliant security.

My typical username is less than 8 characters. All of my typical password formats are >25 characters. Trying to figure out memorable credentials and figuring out the hidden complexity/validation requirements for all of these and the hint... Time wasted: 30 minutes.

Step 4: Post-login. The website, post-login, does not work in firefox. I assumed it was one of my many ad/tracker/header/etc. blockers, and systematically disabled every one of them. After enabling ad and tracker networks, more and more of the site loaded, but it always failed. After disabling bloody everything, the site still refused to work. Why? It was fetching deeply-nested markup, plus styling and javascript, encoded in xml, via api. And that xml wasn't valid xml (missing root element). The failure wasn't due to blocking a vitally-important ad or tracker (as apparently they're all vital and the site chain-loads them off one another before loading content), it's due to shoddy development and lack of testing. Matches the rest of the site perfectly. Anyway, I eventually managed to get the site to load in Safari, of all browsers, on a different computer. Time wasted: 40 minutes.

Step 5: Contact info. After getting the site to work, I clicked the [Enroll] button. "Please allow about 10 minutes to enroll," it says. I'm up to an hour and 50 minutes by now. The first thing it asks for is contact info, such as email, phone, address, etc. It gives me a warning next to phone, saying I'm not set up for notifications yet. I think that's great. I select "change" next to the email, and try to give it my work email. There are two "preferred" radio buttons, one next to "Work email," one next to "Personal email" -- but there is only one textbox. Fine, I select the "Work" preferred button, sign up for a faux-personal tutanota email for work, and type it in. The site complains that I selected "Work" but only entered a personal email. Seriously serious. Out of curiosity, I select the "change" next to the phone number, and see that it gives me four options (home, work, cell, personal?), but only one set of inputs -- next to personal. Yep. That's amazing. Time spent: 10 minutes.

Step 6: Ranting. I started going through the benefits, realized it would take an hour+ to add dependents, research the various options, pick which benefits I want, etc. I'm already up to two hours by now, so instead I decided to stop and rant about how ridiculous this entire thing is. While typing this up, the site (unsurprisingly) automatically logged me out. Fine, I'll just log in again... and get an error saying my credentials are invalid. Okay... I very carefully type them in again. error: invalid credentials. sajfkasdjf.

Step 7 is going to be: Try to figure out how to log in again. Ugh.

"Please allow about 10 minutes" it said. Where's that facepalm emoji?

But like, seriously. How does someone even build a website THIS bad?

So I've taken the first steps into mobile development this past week, I attached two joysticks to a basic unity app to check if touch input was working and I guess I never got around to uninstalling it. so I go to school and finish some class work early and decide, why not check and see what it would take to get my current main Alpha project working. I open my unity folder and see Joystick_Test and someone walking by asks "what's that?" To which I reply tapping on the app "it's a touch screen test, to see if the phone can detect me touching the screen and dragging my fingers. I hand him the phone and he asks why nothing is happening which I respond with "it's just an input test, it's not ment to be anything fancy I just need to program the joysticks and the scripts are still in development" and he hands the phone back and says "your lazy as shit. I can make the controls work in under a minute" and he walks away. It's lunch now and I manage to catch him in the library. I open Unity, and Mono-develop and call him over. I get out of my seat and say "program the left joystick to move around. I'll give you a hint, vector3". He sits in the chair and stares at the screen for a solid minute until I see him type
Console.writeline("hello world");
And he said it would work and just walked away.

So finished a project for a client, the client signed a contract. He signed off that all milestones where reached. Text me that he was very pleased.
We give 30 days to pay. 8 days before the due date he asked for a meeting, telling us he wants to go another direction and he wants the source code to show the new development team he's going with to get a quote from them. I tell him that, that's fine he can have the source files once he pays for the product which was in the contract they signed mind you!! And this FUCKING DICK FART threats to sue, saying he's calling his lawyer, threatening me and my development partner with physical violence, and saying he's going to sue me personally not because me work was bad but because I refused to give him the product before he paid. I was calm we offered to meet his new dev team explain the code, and show them what they needed to see to give the clients a quote and they would not allow that, saying how now I'm not getting paid instead I'm getting sued and that he will publicly shame my startup company. Just complete bullshit, good thing I saved the original contract he wanted me to sign which had threats of physical violence I. His contract... Which in retrospect should have been a hint, but it was the highest paying contract we ever landed. Seems he never planned on paying. What's a guy to do?

My first job was actually nontechnical - I was 18 years old and sold premium office furniture for a small store in Munich.
I did code in my free time though (PHP/JS mostly, had a litte browsergame back then - those were the days), so when my boss approached me and asked me whether I liked to take over a coding project, I agreed to the idea.

Little did I know at the time: I was supposed to work with a web agency the boss had contracted to build their online shop. Only that he had no plan or anything, he basically told them "build me an online shop like abc(a major competitor of ours at the time)"

He employed another sales lady who was supposed to manage the shop (that didn't exist yet). In the end, I think 80% of her job was to keep me from killing my boss.

As you can imagine, with this huuuuge amout of planning and these exact visions of what was supposed to be, things went south fast and far. So far that I could visit my fellow flightless birds down in the Penguin's republic of Antarctica and still need to go further.

Well... When my boss started suing the web agency, I was... ahem, asked to take over. Dumb as I was, I did - I was a PHP kid and thought that Magento, being written in PHP, would be easy to master. If you know Magento, you know that was maybe the wrongest thing I ever said.

Fast forward 3 very exhausting months, the thing was online. Not all of it worked yet, but it was online and fairly secure.

I did next to everything myself, administrating the CentOS box the shop was running on, its (own) e-mail server, the web server, all the coding required for the shop (can you spell 12 hour day for 8 hour pay?)

3 further months later, my life basically was a wreck, I dragged myself to work, the only thing I looked forward being the motorcycle ride home. The system worked though.

Mind you, I was still, at the time, working with three major customers, doing deskside support and some admin (Win Server 2008R2 at the time) - because, to quote my boss, "We could not afford a full time developer and we don't need one".

I think i stopped coding in my free time, the one hobby I used to love more than anything on the world, somewhere Decemerish 2012. I dropped out of the open source projects I was in, quit working on my browser game and let everything slide.

I didn't even care to renew the domains and servers for it, I just let it die without notice.

The little free time I had, I spent playing video games and getting drunk/high.

December 2013, 1.5 years on the job, I reached my breaking point and just left, called in sick at least a week per month because I just could not see this fucking place anymore.

I looked for another job outside of ALL of what I did before. No more Magento, no more sales, no more PHP. I didn't have to look for long, despite what I thought of my skills.

In February 2014, I told my boss that I quit. It was still seven months until my new job started, but I wanted him to know early so we could migrate and find a replacement.

The search for said replacement started in June 2014. I had considerably less work in the months before, looks like he got the hint.

In August 2014, my replacement arrived and I got him started.

I found a job, which I am still in, and still happy about after almost half a decade, at a local, medium sized ISP as a software dev and IT security guy. Got a proper training with a certificate and everything now.

My replacement lasted two months, he was external and never really did his job - the site, which until I had quit, had a total of 3 days downtime for 3 YEARS (they were the hoster's fault, not mine), was down for an entire month and he could not even tell why.

HIS followup was kicked after taking two weeks to familiarize himself with the project. Well, I think that two weeks is not even barely enough to familiarize yourself with nearly three years of work, but my boss gave him two days.

In 2016, the shop was replaced with another one. Different shop system, different OS, different CI. I don't know why and I can't say I give a damn.

Almost all the people that worked at the company back with me have left for greener pastures, taking their customers (and revenue) with them.

As for my boss' comments, instructions and lines: THAT might not be safe for work. Or kids. Or humans in general. And there wouldn't be much left if you put it through a language filter...

Moral of the story: No, it's not a bad thing to leave a place if you're mistreated there. Don't mistake loyalty with stupidity!

And, to quote one of my favourite Bands: "Nothing matters when the pain is all but gone" (Tragedy + Time by Rise Against).

I think there is such a thing as "getting too comfortable with the people you work with".

My boss came over and wanted to show me how to do a new process. We start going through the steps and a question arises. I then IM my team lead, because he's the one who would know the answer, and all I get back from him is sarcastic comments and profanity (he doesn't know my boss is sitting at my comp with me). So I keep trying to get him to be serious, and he just keeps his mouth (well, fingers) going. (He is remote - not in our bldg). I want so badly to shut him up because what if he says something about my boss while she is sitting there? Not that he does that, but at the pace he's going, it no longer would surprise me.

There should be some sort of code to hint to your team to STFU and give a fucking answer when one is needed. Sort of like what kids do to hint that a parent is in the room, but for work?

My fav interview was at my previous job. It was a junior position. The lead was a very friendly and wise guy. He kept pushing me (positively) with subtle hint until I get a code right. After completing each problem he give me elaborate explanation about the meaning of the problem and how to approach it from other angles. It felt like I'm in front of buddha who is making me realize the inner working of the world. Didn’t get 50% of the questions right, still he recruited me because "You were very curious and you were having fun solving problems". Best one and half years of my career.

If this isn't the worst thing.

I was asked to develop a WordPress plugin as an intern developer and I've been on it since last week. I got stuck when i finally had the loops running but couldn't find a way to format the output without overwriting the existing values on each iteration.

For the last one week I've been showing the progress on my code to the CTO and this is how it has been.

Me: Hello. Everything is coming along fine, I have most of the functions running properly, do you mind looking into the algorithm?

CTO: Oh not at all, let's see what you got. Omg great code for an intern. I think you should add a new variable there and maybe clean up that function over there because it's deprecated now and yeah HaHa, Great work.

Me: Thanks xD I'll have it finished latest next week.

CTO: Oh great. I can't wait to see what you'd have by next week so we can install it on our WordPress.

*Next finally week comes and I'm done with the code.

Me: Hello, I'm done with the entire code! Want to take a look? The plugin works just exactly as described.

*CTO takes a look

CTO: Omg?

Me: Omg?

CTO: This is completely bad programming practice, so you are running 4 nested loops that all send queries to our data base and make changes to data. This would have a very drastic effect on the server considering the traffic we get.

Me: But you saw this exact code last week and said it was okay, I only changed some CSS since the last time.

CTO: Omg, we can't accept this, you have to develop it again from the scratch without using those loops and queries.

Me: What? Okay, fine. Any hints?

CTO: Yes.

Me: What?

CTO: Just start. That's the greatest hint I could ever give. And also, always have a plan before you begin.

Me: Yeah, thanks for those. It's the first time I'm hearing them and they would totally be applicable to building this thing.

Today I told 3 devs that they either get their shit together or they can pack their things and look for a job.

I can get easily pissed, but it's rather rare for me to get to that point easily.

Now my dear friends, can you guess what they did?

I give you a hint...

They made a test suite validating a network library.

So we have roughly 200 plus lovely splitted tests, neatly put in a directory structure - lovely organization.

(I might have written in the ticket that as a requirement... Cause I know my lil hellspawns)

But as I started looking at some tests, there was always something missing...

Network library...

So we needed to create an endpoint... And handle of course the tests communication with the endpoint *somewhere*.

I'd guess you know already what these mofos did...

Yeah. We have one class.... That handles all tests endpoints... Via different methods... Plus additional methods like utility functions....

The ticket was easy they said.

Me chewing their heads off was easy too.

Jesus Christ, I really doubt sometimes that some devs are able to go to a toilet.

Maybe thats the reason some wear baggy pants - easier to hide the pampers.

*rolls eyes*

teamLeader: We can't release because your change doesn't work, it breaks on the machine ABC123
iHateForALiving: I diagnosed the issue and I still don't know what's related to. BUT I'm 100% sure it's not related to my change, or anything that has changed in the last 24 months. Anyway we can take a look at this, just give me admin credentials for this machine.
teamLeader: no we can't.
iHateForALiving: ... Wait what? How am I supposed to reproduce the issue? Why can't I access the machine?
teamLeader: It's in use by the testers.
iHateForALiving: What for?
teamLeader: ... Educational purposes!

They report some issue on some particular machine, then refuse to give us access to said machine to reproduce the issue because they have "educational purposes", me and God know fuck kind of education I have in mind for this circus but as soon as I get my hands on them they'll get a hint.

Man wk89 awesome... bringing back a lot of memories. The one thing really stands out to me though is the software.

I see a lot of rants about people shocked that turboC is still in use or other DOS programs are still in production. A lot can of bad be said here but I think often it's a case of we truly don't build things like we did in the good old days.

What those devs accomplished with such limited resources is phenomenal and the fact that we still haven't managed to replicate the feel and usability of it says a lot, not to mention just how fucking stable most of it was.

My favourite games are all DOS based, my most favourite of all time Sherlock is 103kb in size. When I started coding games I made a clone of it and to this day I am still trying to figure out what sorcery is in the algorithm that generates/solves puzzles that makes it so fast and memory efficient. I must have tried 100+ ways and can't even come close. NB! If you know you can hint but don't tell me. Solving this is a matter of personal pride.

Where those games really stand out is when you get into the graphics processing - the solutions they came up with to render sprites, maps and trick your eyes into seeing detail with only 4-16 colours is nothing short of genius. Also take a second to consider that taking a screen shot of the game is larger than the entire game itself and let that sink in...

I think the dramatic increase in storage, processing power and ram over the last decade is making us shit developers - all of us. Just take one look at chrome, skype or anything else mainline really and it's easy to see we no longer give a rats ass about memory anywhere except our monthly AWS/GCE bill.

We don't have to be creative or even mindful about anything but the most significant memory leaks in order to get our software to run now days. We also don't have constraints to distribute it, fast deliver-ability is rewarded over quality software. It's only expected to stay in production 3-4 years anyway.

Those guys were the true "rockstars" and "ninja" developers and if you can't acknowledge that you can take ya React app and shovit.

So I did an interview today and the problem was given a = 1 2 3 and b = 2 3 write code that finds the common elements.

I asked what the data structures are and they said it can be whatever so I said cool then we can use sets and do an interception to get unique elements.... this was in Python... but for the life of me I couldn't remember what the intercept notation was... and brought that up hoping they're give me a hint haha.

So I ended up writing a 8-9 line solution for what could've been a one liner fml: return a | b.

All because I didn't know the notation and still needed to give them something. Painful to write when I knew I was reinventing the wheel. Sign

I almost never use sets so this was heartbreaking hopefully I still get an offer!

How bad of a fail is this in y'all opinion?

I'm very short tempered at the moment.

A lot like Dr Cox in Scrubs.

And really ... You mother fucking stupid idiotic developers with your tendency to discuss absolutely everything just to not have to work for a dozen more minutes...

But ok. Let's discuss.

But even that seems to be absolutely impossible for you little shitheads.

Instead of discussing solutions, nooooooooo....

We're grown up developers so we discuss how the baddy manager hurt our lil feelings by saying that we're morons for wasting all the fucking time without coming up with a solution.

Now my lil cry babies, once the baddy manager got your pacifiers so at least once in an hour my migraine finally calms down for not hearing your bitching pathetic lil whiny noises...

Face it. Over the years you collected a huge ton of mother fucking tech debt because no one of you actually took a bit of time to use that empty space in your head to think at least a mu further than the dumb jira task you were given.

And yes. That ends badly.

And yes. As it is now in a state of cluster fuck, guess what. You have to work. You get money for it, remember?

And yes. if you would stop moping and bitching and crying and being a pathetic lil piece of shit, you'd realize we could come up with solutions very fast.

But nooo... Let's talk about our feelings.

And how we are over worked.

And how nothing works.

Cause yes. That will be the hail mary that saves us all.

Let me give u a hint: it's a mother fucking waste of time bitches.

I think it's time I put a pacifier not only in your mouth, but arse too. Maybe it helps overcoming the anal and oral phase of childhood so we can at least have something close to adult talk.

*breathes in*

Gooozfraba.

Don't need Netflix when you have a production deployment right before a long weekend. It has failed since last two weeks due to vulnerabilities present in one of libraries(P.S. FUCK JAVASCRIPT and Post release vulnerability scans!). You have rewritten the whole functionality from scratch twice! Security gates finally open for you, welcoming with arms wide open. So you click Deploy! DAFUQ!! FUCK MY LIFE! Deployment failed! It's only a 3 hour window to deploy! You frantically re-review your code, is it me?? Not again!! It isn't! Well, why is the deployment failing, you work against the clock. Going through configs, code, documentation! WTF is it?? Should I give up and raise a support ticket? Nope! You login to the server, sifting through logs and configs, there's a couple of other tickets with today's deadline. What are you going to do? And you get a hint! You take the hunch, change the config 5 minutes before deadline!
Get merge request approved, wait for the build, hit DEPLOY!! Nail biting 3 minutes! Your eyes fixed on the logs! Building..... Pushing instances..... Starting App..... SUCCESS!!! Finish the remaining tickets! Your long weekend still exists!

A loooong time ago...

I've started my first serious job as a developer. I was young yet enthusiastic as well as a kind of a greenhorn. First time working in a business, working with a team full of experienced full-lowered ultra-seniors which were waiting to teach me the everything about software engineering.

Kind of.

Beside one senior which was the team lead as well there were two other devs. One of them was very experienced and a pretty nice guy, I could ask him anytime and he would sit down with me a give me advice. I've learned a lot of him.

Fast forward three months (yes, three months).

I was not that full kind of greenhorn anymore and people started to give me serious tasks. I had some experience in doing deployments and stuff from my other job as a sysadmin before so I was soon known as the "deployment guy", setting up deployments for our projects the right way and monitoring as well as executing them. But as it should be in every good team we had to share our knowledge so one can be on vacation or something and another colleague was able to do the task as well.

So now we come to the other teammate. The one I was not talking about till now. And that for a reason.

He was very nice too and had a couple of years as a dev on his CV, but...yeah...like...

When I switched some production systems to Linux he had to learn something about Linux. Everytime he encountered an error message he turned around and asked me how to fix it. Even. For. The. Simplest. Error. He. Could. Google. Up.

I mean okay, when one's new to a system it's not that easy, but when you have an error message which prints out THE SOLUTION FOR THE ERROR and he asks me how to fix it...excuse me?

This happened over 30 times.
A. Week.

Later on I had to introduce him to the deployment workflow for a project, so he could eventually deploy the staging environment and the production environment by hisself.

I introduced him. Not for 10 minutes. I explained him the whole workflow and the very main techniques and tools used for like two hours. Every then and when I stopped and asked him if he had any questions. He had'nt! Wonderful!

Haha. Oh no.

So he had to do his first production deployment. I sat by his side to monitor everything. He did well. One or two questions but he did well.

The same when he did his second prod deploy. Everythings fine.

And then. It. Frikkin. Begins.

I was working on the project, did some changes to the code. Okay, deploy it to dev, time for testing.

Hm.

Error checking out git. Okay, awkward. Got to investigate...

On the dev server were some files changed. Strange. The repo was all up to date. But these changes seemed newer because they were fixing at least one bug I was working on.

This doubles the strangeness.

I want over to my colleague's desk.

I asked him about any recent changes to the codebase.

"Yeah, there was a bug you were working on right? But the ticket was open like two days so I thought I'll fix it"

What the Heck dude, this bug was not critical at all and I had other tasks which were more important. Okay, but what about the changed files?

"Oh yeah, I could not remember the exact deployment steps (hint from the author: I wrote them down into our internal Wiki, he wrote them done by hisself when introducing him and after all it's two frikkin commands), so I uploaded them via FTP"

"Uhm... that's not how we do it buddy. We have to follow the procedure to avoid..."

"The boss said it was fine so I uploaded the changes directly to the production servers. It's so much easier via FTP and not this deployment crap, sorry to say that"

You. Did. What?

I could not resist and asked the boss about this. But this had not Effect at all, was the long-time best-buddy-schmuddy-friend of the boss colleague's father.

So in the end I sat there reverting, committing and deploying.

Yep

It's soooo much harder this deployment crap.

Years later, a long time after I quit the job and moved to another company, I get to know that the colleague now is responsible for technical project management.

Hm.

Project Management.

Karma's a bitch, right?

I understand that some people have trouble with home office.

Well. I don't.

But at least have the fugging frigging respect and
1) answer my bloody questions, especially if I'm frigging nice and make a questionaire and notify you without a shitty meeting.
2) when you ask for an appointment during non working hours.... Then don't be fucking late and especially don't fucking miss it without telling.
3) And don't... Don't fucking give me a bullshit excuse like "yeah, I forget".
At least an honest apology....

I'm currently really close to murder people or call an meeting where I declare that waiting for appointments will be counted as work time.

(hint: this is the fucking sixth time in 4 weeks someone fucked up. And I'm really pissed)

My conversation with Avalara support (API for taxing):
Me: Hey I'm implementing your API for a client. The requests are going through, I get a valid response back but all goods are taxed with $0. Can you please give me a hint what I might be missing?
Sup: You're using Salesforce Commerce Cloud, requests might be blocked through their firewall
Me: I don't think so, here are some sample requests and responses I just created. The object returned matches the one in your API Doc.
Sup: This isn't a system controlled by us, no support.
Me: So how in the world can it be you don't control your own endpoint?

Seriously, if you don't want to help, next time just say fuck you...

Saw the ++ number on this rant and it made me feel all warm and fuzzy on the inside.

You win 20 poster points if you can guess why this number is special.

I'll give you a hint: "512" and "5-pin" (or 3-pin if it's cheep)

Story about someone elses rant
A = coworker;
B = random guy from company, but from another office;
C = manager we like a lot, cause he has IT background;

A asked B about a problem, because B worked with the that thing. B answered I dont know. So A asked C, and told him, im asking you, because B said, he dont know. C went nuts and pulled a shitstorm on B, like who WTF do you think you are, that you cant give at least a hint to A on the problem or Cc someone who may know more about the problem.

what i wanna say is, shouldnt it be common sence if someone asks me about a problem i navigate him to a person, who knows more than me? Even if its the first day i the office, I know this is my team leader he should see the bigger picture of the problem, so ask him. But telling idk is like, go fuck your self.

When logging in, why is there no reminder like 'your password was at least 8 characters long with at least one digit'.

Hey Guys!

Hope to find some help here. So i got a MacBook Pro (2015) from my Workplace and upgraded it to High Sierra. I set everything up and it worked fine untill i did some User configurations. I couldnt access the Settings in preferences because my password was wrong (it wasnt really, but it didnt accept it). So i thought reinstalling would help. I did the reinstall process but got an error at the end of it. “Could not create a reboot partition”. I don’t remember the message exactly. So I have tried several things and hope someone can give me a hint.

- reinstall via cmd + r -> failed
- made a time machine backup from my private MacBook (High Sierra) and put it in my work MacBook -> failed
- recovery from internet -> failed
- external drive with High Sierra installer and booting it from there -> failed

Hope you guys have a clue what to do. Thank you :).