Management : "How long you think it would take?"

Me : "now this is a rough estimate, but I think building the back-end and database alone could take 6-months minimum"

Management : "WHAT ARE YOU TALKING ABOUT? YOU ARE NOT SERIOUS"

me : "its a big proj..."

Management : "I thought it will be something like 10 days, already told the client it can be done"

me : "but we are not ready"

Management : "how are we not ready? we already have the virtual 3D shop, and we can use this ready-to-deploy eCommerce service as our data base "
... "you need to figure this out, this is not acceptable" he continued

* 2 Days Later -talking to my direct boss *
Boss : "since you don't know how to do it..."

me : "what ? I didn't say I can't do it, all I said it will take six months"

Boss : "yeah yeah, anyway there is this studio, a professional polish studio, we called them and they can do it, we will sign a contract with them, this will let you focus on the front-end. good?"

me : "well alright then"

Boss : "please write a doc, explaining everything needed from the backend"
-to me that was the end of it, took a long time to tell me they made the deal-

* 5 Months later *
- "Abdu, can you come here for a minute..."
- "yes boss?"
- "the document we asked you to do for the Polish studio, did you specify that we needed an integration with the API we are using for eCommerce?"

scared to death I answered : "why of course I did!"
I ran to my PC to check it out because I didn't know, I forgot because no one even comment on my doc. I check it out, and it was clearly explained... I got relaxed...

turns out they didn't even do what we asked them for. took them 5 months, and with no communication whatsoever. all their work was useless to us. complete dump waste.

----------------
never mentioned this until a year later... in a heat of moment when they were asking me to make an impossible task with no men and no time... I reminded them of this story... management didn't like it. but it was the truth. they didnt push this crazily this time

Hey everyone!

devRant will be going down on Friday, July 7th around 10:30pm EDT so we can do some database maintenance and restructuring of our cluster. It hopefully won't be down for more than about 30 minutes or so, and during that time you should see our "down for maintenance" message.

If you usually use devRant while you're on the toilet (we know many do!), we apologize and suggest you try to schedule around this!

Please let me know if you have any questions and apologies for the inconvenience.

Me: That's not how browsers work.

Designer: Well, our users need it.

Me: Uh, I'm not arguing with your idea, but no browser supporters that kind of thing

Designer: Well, figure it out because it's not optional.

Me: ... I'm not disagreeing with you, I'm saying that's not something we can do.

Designer: So, what will it take? What do we need to do to get this in?

Me (not actually): motherfucker this isn't a negotiation! I'm not arguing I'm fucking explaining the limitations of web apps!

PM: You know that screen that pops up at the start of the app asking for permission to access health data?

Me: Yeah the iOS HealthKit permission screen. What about it?

PM: Can you take that out. I don't think people are going to agree to it. I want people to use the app.

Me: Well we can't do that, apple says if we want to use HealthKit we have to ask for permission. We shouldn't be touching that data without permission anyway.

PM: Oh no permission is fine I get that, but is it not implied by downloading the app, its clearly a health app. I really don't want people to download it and then uninstall it because they don't like this.

Me: Not really, not everyone will know what data is needed, some of it might be sensitive to them.

PM: Nah I don't buy into that. I asked 5 of my friends on the golf course at the weekend and 3 of them said they wouldn't agree to it, thats 60% of our user base, we can't have that.

Me: ... ok, well I don't agree that your 5 friends is a fair sample to judge the whole world by, either way we have no choice.

Pm: No this isn't going to fly, can we not build our own HealthKit that doesn't have this kind of permission screen? Maybe we could start our own, and invite our partners to use it?

Me: ... no

Pm: why not? We'll have legal draw up something we put in the terms and conditions.

Me: ... it will take months to build for all the different types of devices we have, if they even let us get access to them, and then we will have a different standard to everyone else.

Pm: ... no your not seeing the big picture, i'll run the idea up the ladder.

**It was approved up the ladder, and subsequently cancelled when they realised the scale of the work involved which is both a "thank god" and a "wtf" moment**

Someone at Google: how do we make Android build times quicker?

Someone else at Google: we could make a new button next to Run and call it 'Instant Run' and give it an awesome lighting bolt icon!

First someone: what will it do differently?

Second someone: nothing 😎

Boss: We are using Angular 1 in our project, right?
Me: AngularJS, yeah, we are using it.
Boss: I heard they have AngularJS 4 now and it's faster and better.
Me: Angular, yeah that's much better.
Boss: So shouldn't we upgrade it? Can you do it this week?
Me: Erm... It's gonna take more than a week.
Boss: How much time do you need?
Me: 6 months, at least.
Boss: What if I put one more guy with you on this? How much time will it take then?
Me: Let me rephrase. It's gonna take 6 months for the entire team to upgrade all the modules in our product to Angular 4. Not including the time to train everyone on Angular and TypeScript.
Boss: Oh, Angular 1 is suddenly seemed to me a better option now.
Me: Smart move 😉

classmate: Hey, "friend" told me you do freelance website development. right? I need to create a new website and need your help.

Me: umm... OK... what's it about?

Classmate: It's for my dad's friend's business.

Me: OK. but I will charge the standard rate.

classmate: No... I will make it myself. I just want your help.

Me(Internally): ...not again...

Me: Do it yourself then.

Classmate: It will be quick. an hour or two max.

Me: *speechless*

Classmate: And one of my uncle who did IT told me that c++ is faster. can we use that instead of HTML?

Me: huh...?

classmate: you don't know shit.

... classmate walks away...

This guy somehow manages to get As in exams (mostly cheating. and our papers are shitty theory papers which you can mug up. so that helps) and in a year will have an IT degree.

Interviewer: Do you know about SQL injection?

Student: Yessss

Interviewer: Okay, how we can prevent it?

Student: Yes, we should prevent it as prevention is always better than cure. It can lead to data loss and other problems so it can be difficult to fix it if it happens. The best case is that nothing like that takes place. [...]

Interviewer: I get it but how?

Student: By not building any web applications.

[Silence]

Interviewer: Nice, you may go. Do not call us. We will call you.

Recruiter: Will you like to do internship?

Me: yes,how much time I need to dedicate?
R : 40 hrs/week atleast

Me : Is it a paid internship?

R : No we will provide you with experience letter

Like seriously 40hrs/WEEK unpaid

We have new scrum master. First meeting together.

Project owner:
- I would give them time to wensday (2 days away) days to do migration
Manager:
- delivery is in Tuesday. can we have two teams to work on it so it will be done twice as fast?
Scrum Master:
- do you really think that if you get 9 women pregnant they would deliver you baby in a month?

So my programmer boyfriend chose his career over me.

We made plans together that he will teach me how to do be better at coding and that he will leave his company because it sucks. However, they joined some hackathon and won.

Now, they are going overseas and our plans? Nothing. He chose his company, success, money and fame over me.

We’re engaged btw. Sorry for being so dramatic. Any advise?

One of our CEO: “we dont have the internet speed that we have paid for - I will check it out”

Developers: “please dont, remember last time?”

CEO: “the net will only be down for a couples of minuts”

Developers: “please dont touch anything, and do it after hours”

1 hour later we still dont have the internet restored.

FML!

Interviewer: For this next code challenge you will not be allowed to use the internet, or an IDE.

Dev: …

Interviewer: OR a keyboard OR a mouse. I will be verbalizing the code to you and you need to memorize it and tell me where the bugs are.

Dev: …

Interviewer: We must do this exercise to know how you are as a dev without any performance enhancing “aid”. This way we can understand where you are truly at skill-wise, and what you are truly worth from a compensation perspective.

Dev: …

Dev: If I get a job with you will I be allowed to use the internet and an IDE and a keyboard/mouse?

Interview: Of course you would! Getting anything done without those is just about impossible. We just need to evaluate you without them to see how good you REALLY are.

Dev: …

What happens when you change the service call center to 100% AI

AI: Hello, this is the After Service center. How may I help you?

Angry customer: Hey! Do you count this as a product? Do you sell this to use it? F*** shit?! Bring the manager now!

AI: Thank you for your response. We will connect you to the Development team.

Angry customer: Uhhhhhh

AI: Hello, this is the development team. Please state your problems.

A bit relaxed customer: Umm, so this product you guys are selling stops working sometimes, so...

AI: We are sorry, but for the product misfunctions, please contact the After Service. We will connect you to After Service.

F***ed out customer: Wait, I just came from the After Service!

AI: Hello, this is the After Service center. How may I help you?

Angry customer who is ready to throw the phone: I said that the product is not working, and I asked to bring the freaking manager in the line!

AI: Thank you for your response. We will connect you to the Development team.

Customer throwing the phone and shouting: F*********************************************************************************************!

Real Story:

Manager: You have to add an extra section in the app to show more details.

Me: We are already showing so many unnecessary details. These changes are not required.

Manager: No !! You have to do it.

Me : Ok !!! So why can't we show it in the section where we are showing the other details. Why make a separate section for it.

Manager : No !! It won't be clearly visible to the user. Just do it.

So I added another section to show useless information that we are already showing it f**king everywhere else in the app.

So I released a new apk next day with the added features.

In meeting, our CTO goes through the app and ask manager....

" Why we have added an extra section for showing same details that we are showing everywhere else ???

Who approved this ?? This is nonsense !!! "

Here comes the fun part.

Manager : I don't know. I didn't ask for it. These changes were not there earlier.

And ask me.

"Who told you to make these changes ? "

I am like... F***k man you a***ole told me to do it even when i told you it will be nonsense.

Dev : Every user in your organisation requires their own username and password...

User: Why?

Dev: Because if everyone uses one account, every note, product, message etc made by all the user's will be saved to that one account and confuse the he'll out of everyone using it when they can't find their 'own' information they made/captured/downloaded.
We just need the user emails.

User:We can't give you all the user emails just use one account ....
(The reason for not providing us the emails is purely cause it would require user to do work and that's out of the question)

Dev: Uhm ok, but this is not what you want, and *interrupts*

User: It is what we want, do it like that everyone will understand and it will make the system easier.

*Two weeks later*

User: Why is there only one account? Why doesn't everybody have their own account? This is not what we wanted.

... The shit you have to deal with when you are on holiday ...

Dev: What do you think of the new version of the app?

Client: It’s great! We just have a couple notes of feedback we are working on compiling. We should have those to you by next week.

*Next week*

Client: We need another week to compile all of this feed back we are generating

*Another week goes by*

Client: Still working on it, it’s going to be a really thorough review when you get it though. No stone will be left unturned!

*2 weeks later*

Client: Here it is!

Attached: A word document with a single line of text “can’t nobody log in” next to a picture of the login screen with a red circle drawn around the login button

Client: Can you hurry up and action our feedback? We want to go live next week

Dev: …

A real interaction I just had...

Team Member: "Can you handle this ticket for a bug fix?"

Me: "Whats the problem?"

TM: "We aren't exactly sure..."

Me: "Ok, so can you show it to me?"

TM: "We can't get it to happen again, and when it does the machine freezes and we can't debug it..."

Me: "So, if I find a fix then how do we test to make sure it worked?"

TM: "I'm not sure..."

Then today,

Product Manager: "How's that bug fix going?"

Me: "Well, let's see. The problem still hasn't been defined. I have never been able to recreate the issue. I have a hacky fix in a PR..."

PM: "Great, so we can deploy today?!?"

Me: "No, because we have no way to reproduce or test this issue at all..."

PM: "Do you think your fix will work?"

Me: "Honestly, no. If you're asking for my opinion then you can have it. IMO this is NOT a bug fix but a change to how the system operates altogether. This system was built by someone who didn't know what they are doing. We have done our best with it but it is a house of cards. And now the solution is to replace a card at the bottom layer. It is likely that no matter what fix we do (even when we can fucking test it) that it will topple the house of cards..."

PM: ~Looking at me in disbelief~

Me: "If you ask me for my honest professional opinion then you will get it. Keep that in the future if that honest response was outside what you expected."

PM: "I will do that, thanks for your assessment"

Where do we go from here? God only knows.

Praise Joe Pesci

"Stop working from home. Fuck this. We do enough and don't get paid what we should. It is you and me for two campuses and you are far more knowledgeable and qualified than what they offered you at the beginning. I get that the benefits are killer but don't burn yourself out. I am not expecting you to work from home. Will not ask of it unless really is required and would much rather we have a few beers instead of getting together to finish bullshit deadlines...for 2 devs"

My current lead developer. He turned into my work best friend and he is really into the whole concept of "fuck it we ain't getting paid enough"

Dis b ma dude.

!rant

A: "Hi, I'm A, I'm the CEO of X, we had this project I'd like you to do for me"
Me: "Hi, can I have more details about the project?"
A: "Ah yes, this is some kind of e-commerce for our start-up, we need you to do a web app, iOS, and Android app in 1 month"
Me: "OK we can do it in 2 month."
A: "OK we'll let you know our decision tomorrow"

(next month)
A: "Sorry we have to postpone this project"

(next 5 month)
A: "Hi! now I'm building this Y start-up and we need you to help us migrate our android app to web"
Me: (Looks feasible than his last project) "OK, I can do it"
A: "Can we meet tomorrow?"
Me: "OK"
(tomorrow)
Me: "Hello? where will we meet?"
Me: "?"

(next month)
A: "Hi! Sorry for not replying, can we meet this week for the Y project?"
Me: (...)

The following meeting occurred at a client between a recently added client PM and our team, we'll call her Shrilldesi, previously from one of the main consulting vendors.

*Meeting begins after 15 minutes of bullshitting, waiting for people to file in*
Shrilldesi: "Ok everyone, let's get started
TeamMember: "We're still waiting for Z and W, not sure why they're late."
SD: "We can start there. It was decided had to lay off Z and W, because we didn't have enough work."
Moi: "Wait, what. Who made that decision? Why weren't we consulted on this? We have another project starting next week that they were needed for. They just delivered the entire public facing rewrite, why would we let them go?!"
SD: "It was decided by myself, pajeet, and venkata looking at the backlog. Not enough work, week gap."
Moi: "This is going to hurt our ability to deliver the next phase. When are we going to start interviewing new people, the project begins next week?"
SD: "We will interview new resources as needed."
Moi: "Who is we? And 'as needed' is yesterday, or realistically several weeks ago as the. project. starts. next. week. Also, we're obligated by federal law to bring back anyone we lay off before we hire anyone else for the same position."
SD: "Interviews will be done by myself, Mohd, and Pajeet."
Moi: "...can I point out that there's only one modestly technical person in that group, they're an admin, and none of them are from this team? How do you conduct an engineering interview without any engineers?"
SD: "That does not matter, I have watched enough to be able to ask your questions."
Moi: *anger intensifies* "I have to respectfully disagree. I don't feel it's appropriate to cut us out of the process of interviewing our own team members."
SD: "It is decided, we will take care of it, let us move on. Next, we need to find work for the Manasa, she doesn't have anything to do."
Moi: *sharpens baseball bat* "...shouldn't we just fire her then?"
SD: "Oh that is so mean, why would we fire her? We were thinking she might be able to do some of my project management work."
Moi: *sharpening intensifies* "You do realize it's a violation of H1-B statutes for someone to be employed in work other than what is stated on their contract, and Project Managers are specifically listed as not specialized skillsets per federal law."
SD: *ignores question* "We also need to find work for the offshore team, they don't have enough to do. Please find them work for the next period."
Moi: *checks how long the wait period is for ar-15s*
SD: "We also have a new person rolling onto our team, he comes from the xyz team, Dikshit *gestures to person we all figured was lost*. He will be handling our front end development."
Moi: *seething hatred* "WE JUST LET TWO EXCELLENT FRONT END DEVELOPERS GO. WE DO NOT NEED DIKSHIT."
SD: "Please calm down. We will be replacing the other two shortly, there is no problem."
Moi: "Have you heard nothing I've said? Did you even run this by legal and HR? Why did we let them go in the first place? Why do we even need Dikshit?!"
SD: "I said it before, please listen. There is not enough work for them. Dikshit will do front end. What is unclear?"

Note: There's not really any dramatization here. It's almost verbatim what happened. Eventually, the next project was cancelled, they incrementally rolled the rest of the local team off. They then had the cojones to express aghast anger when I notified them I would not be renewing my contract, and open hatred when I explained to them I was not a slave, and I refused to be a bag holder for the inevitable failure of a project without any chance of success. I don't really care what happened after that, they can all burn in their own little nepotistic shitshow of perpetual failure.

Slowbro: Do you have time tonight?
Me: No sorry, I can't stay late tonight, I have a thing with my wife.
S: Oh yeah, I'm not staying late either.
M: Oh, so what do you want?
S: Can you help me install linux?
M: Uh no, I can't stay late -
S: No, no you don't have to stay, you can do it from home.
M: What? No I don't have time tonight. Wait you want me to take your computer home?
S: No, no I need to use my computer tonight.
M: So... What do you want me to do?
S: You can do it on your computer.
M: You want me to install an OS on your computer, but on my computer??
S: No, no *sigh* just try it on your computer so we know it will work on my computer. It is a proof of principle.
M: Reinstall my OS?
S: As a proof of principle. So tomorrow when we do it on my computer, we need not waste any time.
M: ... No I'm not going to reinstall my OS just as a test for you.
S: Not a test, a proof of principle.
M: What are you.. I'm sorry, I don't have time for this tonight.
S: Just a proof of principle!!
M: Ok see you.

*In teams meeting with client*

Manager: Yes we can do all of that and it will be actioned very quickly. We will make all of these feature requests top priority. We will set aside everything we are currently working on in order to get this done!

Dev: ...Are you writing any of this down?

Manager: I don't need to, I always remember everything!

Dev: Just so you are aware, I'm not writing anything down. You're going to need to create a ticket with requirements spelled out for each one of these promises you're making otherwise they won't get actioned by the team.

Manager: I know that!

Dev: ...

*Later that day*

Ticket Title: Action client feature requests TOP PRIORITY!!!

Ticket Description: *empty*

Dev: ...

tl;dr stupid clients with their stupid requirements.

Client: (on Monday) hypothetically could you implement "A"?
Me: (on Monday) yeah I could do that by Friday, let me know if you want me to start it.
Client: (on Thursday) hey remember we talked about "A" well do "B" instead and I'll need it by Friday still.
Me: "B" is completely different than "A" and will take probably twice as long.
Client: but you told me you could do it by Friday.
Me: ............ I want to smash your face.

Had a follow up meeting today to resolve the issue of Product ignoring our comments about possible issues, better ways to do it etc.

New rules:
- We are allowed to suggest to Product that they might be doing something wrong
- We are not allowed to tell product they are doing something wrong
- If Product don’t listen, that’s fine, we will document our comments to protect us later.

Conclusion:
Product are too sensitive to have a conversation with. We are now going to let them fuck everything up, make some notes and say “I told you so” at a later date.

Maturity at its finest ladies and gentlemen.

Actual email I just sent to a customer:

"I logged into your account and I see the problem. I will update you and have it fixed either by tonight or tomorrow morning. It is a rare bug we have encountered before, and we are working on it as you read this. "

The truth:

"Im fucking drunk right now. I know that error. I put off fixing it for awhile now hoping it wouldn't come up because it's fucking annoying to fix. I'll try to fix it tomorrow morning, k no promises though. If I can't I'll still have your problem taken cats of it just means I'll have to do it manually. Anyway.. Gonna drink some more now, bye. "

P. S. There is no we. It's just me. K bye.

Mgmt: We will need you to work on Saturday
Me: I'm afraid I can't, I have plans that cannot be rescheduled.

Mgmt: Then please call your coleague out of vacation. Treat this as super urgent.
Me: I do not feel comfortable calling him out as, as you know, he is on leave (family emergencies) and it is a weekend. I do not think it would be ethical to do so either.

Mgmt: *crickets chirping in my mailbox*
Me: *Updating my LinkedIn*

Whoever thinks that coding is easy.

Fuck you motherfucker stupid chicken head nugget sized brain faggots. You think all we do is smash keyboards in front of our screen and it poops code and creates beautiful applications? Fuck you in particular.

One of my friend says sitting on computer for whole day is the easiest thing. What the fuck motherfucker.
One fucking string can fuck your life forever. Innumerable hours will be wasted behind one simple fucked up logic. And u shithead say its easy.
Get into my shoes and let me bang your head on the keyboard and we will see how beautifully it poops code.

Stupid people.

"Hey, about that matter from yesterday..."
"Yes, what about that?"
"We need to talk about that again! How often do you trigger that system?"
"Once."
"You sure?"
"Yes, but i can check it, if you like."
*find references*
"See, only once."
"Can it happen at a random point later one?"
"No."
"Are you sure?"
"Yes"
"Can you check it?"
"Okay."
*shows code"
"Look here, as you can see, it will not happen at other times."
"Do you have an idea why it could happen anyway?"
"Maybe that system does the action without my software telling it to do so, wasn't that specified that way?"
"Yes, but it normally does that roughly 10 seconds after you give the command the first time, so we thought maybe you could say what makes it do the action at other points maybe."
"Did you check that systems sourcecode?"
"No not yet. But did that happen with the older version?"
"No. But we didn't try."
"Did you change something between the versions?"
"Yes, the new feature."
"Could that make a change in behaviour?"
"I don't see how."
"Can you remove that feature for test?"
"We can take the old version."
"No, we need the new version, but without the feature you added."
"That IS the old version, there is no other difference!"
"Are you sure?"
"Would you like to see it in source control?"
"No, ~ okay. What do you think causes the problem?"
"I haven't had any new ideas since we talked yesterday."
"Okay. Mhhh,...okay. Lets talk again later."

YES SURE! BRING IT ON! I'M LOOKING FORWARD TO THAT! PLEASE COME BY OR CALL ME AGAIN! AND BRING THE BOSS WITH YOU, TO SHOW HOW SERIOUS THE MATTER IS! LET ME TELL HIM THE STUFF I TOLD SEVEN TIMES LAST WEEK!

UPDATE: devRant Trans-Oceanic Journey Community Project

It was a mere 12 days ago that I asked the question; 'Could devRanters, as a community, build a 21st Century Technology-Laden ‘devRant devie-Stressball-in-a-Bottle’ and send it on a journey across the Atlantic ocean?

I am thrilled to report that devRanters enthusiastically accepted this difficult challenge. A core team quickly formed and a tremendous amount of research and progress has been made in a short period of time. I want to give you a high level-flavor of what we are doing. Please keep in mind we still need your help. We welcome all develops to take part in this journey.

I want to give appreciation to the devRant Founders @dfox and @trogus. Without your support and sponsorship this project would not have been possible. devRant brought us together and it a reality. Devie journeying across the Ocean the Columbus sailed will stir the imagination of children and adults worldwide when we launch on May 1, 2017.

Some of the research and action items in progress:

- Slack and trello environments were created to capture research and foster discussion.

- A Stony Brook University Oceanography Professor suggested the Gulf Stream would be a good pathway across the ocean. We researched it very and agree. The Gulf Stream has been a trans-Atlantic conduit for hundreds of years. We are deciding whether to launch from Cape Hatteras, NC or the Virginia coast. Both have easy access to the rapid currents in the Gulf Stream.

- We are researching every detail of the Gulf Stream to make the journey easier and faster for devie. We have maps and a team member gathered valuable ideas reading a thorough book – ‘The Gulf Stream’.

- We decided on using a highly resilient plastic rather than glass for the bottle material. Plastic is much lighter, faster and glass breaks down more easily. The lightweight enclosure will allow us to take full advantage of waves and ample trade winds. We are still discussing the final design as we want to minimize friction and mimic the non-locomotion fish that migrate thousands of miles riding the Gulf Stream.

-The enclosure might be 3D printed unless we can locate a commercial solution. We have 3D specs and are speaking with some experts. There are advantages and dis-advantages to each solution.

- We will be using Iridiums' RockBLOCK two-way satellite technology to bounce lat-long coordinate pings off their 36 low-orbit satellites. The data will be analyzed by our devRant devie analysis software. IOS and Android public apps being built by the team will display devie's location throughout the journey in.

- Arduino will be used as the brains

- Multiple sensors including temperature and depth are being considered

-A project plan will be published to the team Friday 12/9. Sorry I am a few days late but adding some new ideas.

There are still a lot of challenges we must overcome and we will.

That’s all for now. I will send updates and all ideas / comments are valued.

Me: *reinstalling windows10 using the recovery disk.

"Your partitions will be reformatted if needed... warnings this, that... Continue?"
Me: do it already!

"Recovering... 1%..."
.
.
"Recovering... 1%..."
.
.
"Sorry cannot recover. We didn't change anything."

Me: *reboot
.
.
.
.
"No bootable drive found"
YOU MOTHERFUCKING LIAR! *throws away the thumb drive with the laptop attached out of spite

"We need to reduce the scope of the project, guys... What if we don't make tests? They're taking some time do write, so..."

Yep. Let's compromise the quality and call it scope reduction. It will make wonders to our roadmap 👍

Always the same story:

Marketing: hey I'm gonna do a demo to a customer. They were asking for feature XYZ. That's ready on thr staging server right? Do you think I could use the staging server for the demo?

Devs: well feature XYZ is not 100% done. Basically just feature X is done, and it still has a few bugs. The deadline ain't for another month, since we gotta finish ABC first. I guess you could use the staging, but it has a lot of bugs.

Marketing: perfect!

*after presentation*

Marketing: the staging had so many bugs! Why didn't you tell me?! It was so embarrassing showing it to new customers! Anyway, they loved the new feature. We need it to be ready ASAP.

Devs: What?! That's gonna mess up with our schedule. You know what? Fine, but feature ABC will have to wait another month.

Marketing: Well, it'd be ideal if we could do both...

Devs: Pay for more devs or dor extra hours.

Marketing: Just do XYZ. It's a pity that you'll have to push back ABC but it's fine, XYZ is more important.

(I might ask, if it was so important, why didn't you notice so in the meeting where we had decided that ABC would be prioritized?)

*tons of working hours later*

Devs: There, we finished XYZ.

Marketing: Yay! Wow, this month we'll have two major features done: ABC and XYZ!

Devs: No, ABC is not done yet.

Marketing: What? But the deadline was this week.

Devs: It was, but then you decided to prioritize XYZ and we said we had to push back ABC to get XYZ ready, and you agreed.

Marketing: Did we? Fine. But do it quick.

Marketing and their mood swings.

I'm the sole developer at work.

Literally the entire company, save myself, is sales people. (We have one remote mobile contractor as well, but he only does mobile; I'm responsible for everything else.)

I inherited a gigantic pile of nightmare from the previous "senior-level intern" solitary dev/CTO, and I'm still trying to figure out the bulk of it, meaning everything takes longer.

Anyway, we have a meeting roughly once a week, and during each of these -- and several times throughout each week -- the salespeople say things like "We should address this" or "This should be our top focus" or "We really need ___ so I can sell more merchants" or "___ doesn't work right; we should fix it." All of these "we"'s and "our"'s, of course, mean me.

So, today, I decided I'd make a list of everything I have to do, and their general size. Assuming large projects will take one month, medium projects will take one week, and small projects will take one day... I have four months, two weeks, and four days of work ahead of me. (yet I know one of those large projects will take at least two months...)

Make it stop ;;

Pm: OK what you've got here?
Me: a bug, haven't tested yet
Pm: *grabs a phone* follow me we will do it
Me: mkay
Pm: *attaches it, goes to the DOM inspector, starts clicking random divs* OK where the fuck the canvas is?
Me: uhmm there in this tree
Pm: *inspects the canvas element for a few sec* what do you think?
Me: ... ... Well the bug was that it wouldn't resize properly after you change to landscape
Pm: *rotates the phone back and forth looking at the canvas properties*
Pm: gotcha, see? Width and height
Me: yes, those are the default html prope...
Pm: now see, there's another width and height. That's the malfunction right there. I'm telling you.
Me: no, this is css. It overrides the html properties there
Pm: well, say what, it doesn't
Me: no it does, that's how html works for decades already
Pm: but why does that not work properly then? Mm? *stares at me wide open*
Me: well I need to do some testing before I can sa...
Pm: then what do you think we are doing now?
Me: we jus...
Pm: *gets a phone call, stands up and walks away*

No protesting for me today. Sorry.
if anything happens today however, I will create my own Tor exit node.
And you will be among the first to know about it.
Tor will be the next uncensored web. And I will strive to protect it.
At least that's something I can do from home, regardless of time zones and timing altogether.

I feel like we can't save the internet anymore. But we can create another one.
The darkweb is waiting for you.
It's only the Tor Browser away.

This story starts over two years ago... I think I'm doomed to repeat myself till the end of time...

Feb 2014
[I'm thrust into the world of Microsoft Exchange and get to learn PowerShell]

Me: I've been looking at email growth and at this rate you're gonna run out of disk space by August 2014. You really must put in quotas and provide some form of single-instance archiving.
Management: When we upgrade to the next version we'll allocate more disk, just balance the databases so that they don't overload in the meantime.

[I write custom scripts to estimate mailbox size patterns and move mailboxes around to avoid uneven growth]

Nov 2014
Me: We really need to start migration to avoid storage issues. Will the new version have Quotas and have we sorted out our retention issues?
Management: We can't implement quotas, it's too political and the vendor we had is on the nose right now so we can't make a decision about archiving. You can start the migration now though, right?
Me: Of course.

May 2015
Me: At this rate, you're going to run out of space again by January 2016.
Management: That's alright, we should be on track to upgrade to the next version by November so that won't be an issue 'cos we'll just give it more disk then.

[As time passes, I improve the custom script I use to keep everything balanced]

Nov 2015
Me: We will run out of space around Christmas if nothing is done.
Management: How much space do you need?
Me: The question is not how much space... it's when do you want the existing storage to last?
Management: October 2016... we'll have the new build by July and start migration soon after.
Me: In that case, you need this many hundreds of TB
Storage: It's a stretch but yes, we can accommodate that.

[I don't trust their estimate so I tell them it will last till November with the added storage but it will actually last till February... I don't want to have this come up during Xmas again. Meanwhile my script is made even more self-sufficient and I'm proud of the balance I can achieve across databases.]

Oct 2016 (last week)
Me: I note there is no build and the migration is unlikely since it is already October. Please be advised that we will run out of space by February 2017.
Management: How much space do you need?
Me: Like last time, how long do you want it to last?
Management: We should have a build by July 2017... so, August 2017!
Me: OK, in that case we need hundreds more TB.
Storage: This is the last time. There's no more storage after August... you already take more than a PB.
Management: It's OK, the build will be here by July 2017 and we should have the political issues sorted.

Sigh... No doubt I'll be having this conversation again in July next year.

On the up-shot, I've decided to rewrite my script to make it even more efficient because I've learnt a lot since the script's inception over two years ago... it is soooo close to being fully automated and one of these days I will see the database growth graphs produce a single perfect line showing a balance in both size and growth. I live for that Nirvana.

"Your resumé looks really good. We would really like to hire you. But you need to do this completly job unrelated test/coding challenge first."

----

"Is the test Android related?"
"Yes"
*Opens Test* -> "what ist the complexity of this function (written in c)"
*Scrolls*
"Implement algorithm xyz in Go lang"
*Closes test and breaks something*

----

"You will need to Code on a small Android projekt so we can see how you work"

"OK, how much time will i need to plan for it?"

"Our lead dev decided to make it small so its only 4-5 days."

----

What is it with all this stupid hiring test these days? And what do these recruiter think?

If a CPU were an employee...

CPU: Hey boss, I'm seeing you are giving me a lot of mathematical tasks that would really profit from splitting into parallel calculations. GPU's are great for that, we should get one.

Boss: But you can still do them, right? If you can do it, I'm pretty sure you can do it at GPU speeds. We gotta save up so I can buy another car!

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

Boss: Why is this taking so long?

CPU: I'm overloaded with work, so I'm overheating. Maybe you could buy a GPU to help me out, or at least a fan...

Boss: You're overheating? Your personal problems should not affect your professional life. Learn to get your shit together or we will hire someone who will

CPU: *melts*

"Can you do this?"
Sure, give me the information I need...

"We don't have all of it yet"
So I can't do it then

"Well when can you do it"
When you get the information

"Do you need *all* of it"
Well, it's either I do half a job and waste my time, or get it all done in one shot

"The client wants it tomorrow"
When will we have the information?
"We don't know"
Well they aren't having it tomorrow then, are they...

Sales people... don't care *how* things work, as long as they get a tick against their name to show they've sold something...

These anti AI type news articles are ridiculous. We are decades away from anything like skynet. People have seen too much fiction. Everyone used to dream of flying cars, did that happen? No. Do not be fooled, machines can do clever things but they are no where near becoming sentient beings. You try and build something that has the same IQ of a dog and it will still require a shit ton of power and hardware. Plus as far as I'm aware dogs haven't taken over the planet with their level of intelligence.

At the end of the day machines need power to run and we control the source. If anything futuramas more realistic in how AI/robots will integrate with society than these shit piece newspapers.

Manager: We should do X with the database

Dev: That will cause issue Y

Manager: But I read an article that said that issue Y wasn’t a problem

Dev: It did?

Manager: Well it didn’t mention issue Y

Dev: …

When you are given a task or bugs to fix and your boss will tell you everytime that, "this is so easy this will be done in just 3 seconds".

WTF! Then don't hire devs and do it yourself! And start fixing all the damn bugs in just 3 seconds yourself! There are 28800 seconds in whole fucking 8 hours, I guess if we divided it by 3 you can finish a task or fix a bug at approximately 9600! (Applause) Now we are silently calling him "The 3 seconds man'.

Project manager: We have 13weeks for this project. We have promised the client.

Me: okay, why wasnt I consulted on that commitment?

Project Manager: yeah.... we have to do it

Me: okay, if we have 2 dedicated backend and one full time frontend - ONLY on this project.

Project manager: (with the face of lies) yes yes sure we can do that.

6 weeks later, after continuous interruptions. Frontend is behind because he was only on the project to an amount of 2 weeks of the 6 weeks.

Project manager: Are we still on time?

Me: *looks around for prank cameras* no the f#*k we not

Project manager: can we put in weekends?

Me: its 2019 bro, that ain't happening

*But because I am a nice guy, and dont like taking Ls, we will have it ready. Just not gonna tell the project manager, he deserves a few sleepless nights *

It's getting close to that time of year when we are all encouraged to think of others and spread joy around the world. I've decided to go against my usual snarky/anti-social nature, and do something to help others this year.

I'm announcing the practiseSafeHex charitable fund, to give back and help others.

This fund will invest in cutting edge medical research to detect the genetic abnormality in humans that results in project managers not being able to comprehend the simplest of concepts.

Together we can find the reason why the concept "more meetings = less work" is uncomprehendible.

Together we can discover why we can't use an automated bot to generate reports, instead of spending hours in excel spreadsheets.

And together we will find a reason why the answer to the question "can we please just try it?" is always "No".

We do this not for ourselves for short term gains, we do this for the greater good. Together we can find the cause and build a test to filter these people out. So that never again will stressed out developers have to deal with these petty ridiculous issues.

Together, we will solve this!

Thanks,
practiseSafeHex, CEO and managing director of the practiseSafeHex charitable fund for the betterment of developer sanity

6 months ago:

Boss: We have this idea to improve our onboarding to avoid drop off in the new app. See this section here? Were going to take that out of the onboarding and just let them pass straight through to the app. Then when they get into the app, there will be a banner telling them they should go to settings and set this up. That way they can ignore it for a while and get into the app sooner

Me: Get into the app sooner to do what?

Boss: Explore it

Me: Explore an empty app with no content, as they are a brand new user with nothing setup? While theres a big banner on the screen saying "You have insecure settings" ... basically forcing them to do it straight away anyway?

Boss: Yeah, we can give them some recommendations or something while they click around. It will be good. This is months away anyway, we'll talk again

Yesterday:

Boss: So this weird unexpected thing happened. We showed some beta users our plans to remove this section from onboarding and they felt weird about it. They said they didn't like the idea of the banner telling them they haven't set it up correctly

Me: Thats not weird, I said the same thing 6 months ago

Boss: ......... oh, really?

Me: Yep. Its not an improvement to get them through onboarding quicker, just to tell them they have to now go do it somewhere else

Boss: ... right. Ok maybe we'll build it anyway and see how they feel with it in there hands?

Me: nope

Boss: ... what do you mean?

Me: We are behind, you've asked me 3 times in the last week if we are going to be able to get everything in on time ... and now you want me to build something that everyone, apart from you, says they don't like. So realistically, i'm going to build it, and then remove it next week ... and we'll have a discussion about what has to be dropped because of this

Boss: ........ right .... ok .... hhhmmm

Me: *sits with resting bitch face*

Boss: ... maybe we can hide the banner until later. Not show it to them until they've done something in the app?

Me: ... maybe we can not do any of this?

Boss: right but then the onboarding will ...

Me: *talks louder* ... yes will be the way our users want it to be

Boss: ... hhmm i'm not sure

Me: Ok heres what we'll do, so long as it doesn't delay me getting the designs I need, feel free to have the designer mock up what it would look like using that figma on device preview thing. If users say they like it, i'll build it

Boss: ... right but it won't be real on device app so ...

Me: Its that or we cut feature X

Boss: ... well we need that

Me: ok glad we agree, let me know what feedback the designer gets

Boss: ... ok

Dear customer,
as our services are completely free and we do not get paid for working, we beg you to understand, that there are some things you have to tolerate.

1. We are DEFINITELY not going to work 24/7 for you and answer immediately anytime. Only because it's 3pm in your country doesn't mean it's 3pm in our country!

2. We will NOT waste any time figuring out your gibberish and translate your language to our language or whatever, you have to be able to understand English anyways because our website and rules and everything is English!

3. Speaking of rules, READ THEM, I'm sick of explaining to you why you are banned, what do you think FAQs are made for?!

4. STOP SPAMMING AND TAGGING ME FFS. First we have a support chat so you can leave a message there and somebody will read it eventually AND SECONDLY I'M NOT THE ONLY SUPPORTER SO STOP BUGGING ME.

5. READ THE FUCKING MESSAGES I WRITE!

geez.. I just lost it for a second... okay.. gotta go now, I got 20 new messages since I started writing this rant.

I bet some day we'll have robots tell us where bugs in our code are instantly and our kids will say "How did you ever write code without them?" And we will say "We had to use this archaic thing called Google and do research... It took forever!"

~March 7~
Boss: Hey cory, guess what, you will not take control of the servers anymore so you can focus on your real job, the company hire someone to do it
Me: Great, finally i can just program, thanks for the news boss

~Yesterday~
Boss: Hey cory, guess what, the person the company hired needs help to migrate some servers so you need to help him on weekend
Me: Well, it's ok i can do the job

~Today~
Director: Hey mr cory, we need you to help jonny on weekend
Me: Fine boss, i will be on weekend
Director: That's the attitude we need in the company, I do not know how much time you need but we're going to pay you 24 extra hours
Me inside ~every went better than expected~ 🤷‍♂️

Shitty call
Me: what do you want?

Q: I Lost my iphone

Me: (already pissed) ok,do you have an icloud account?

Q: Yes, but i forgot the password.

Me: what!?!, ok, fine, we will reset it, which is your ID?

Q: I lost it too.

*stay calm* *stay calm*

Me: I can't help you go to an apple store and ask there. *I Close the call*

*Add that number to blacklist*

Friend asked my if I could create his webshop.
I agreed.
Some time after that he told me “It’s ok. Will install WordPress. If it doesn’t work I will come back.”

1) I don’t like to be your second choice
2) FUCK WP

Just now he came back: “Hi WP works, but I have a problem removing x”
Me ...
F: “Fix it”
Me “Sorry don’t work on command”
F: “Just do it we are friends”
...

To be continued

PO: Here's a small cool feature I thought of, should be easy enough *shows very basic draft spec*
Me: Cool, how does it work for logged out users? What about customers in Spain? Does it work with US sales tax? Do we need to update the privacy policy? Do we have translations? What's the fallback if it breaks? Who will be maintaining the content?
PO: ...
PO: I'll get back to you

*never hears about feature again*

Teacher: "Will this SQL statement work LavaTheif?"

Me: "you need to put a 'WHERE id.."

T: "but will it work like this?"

Me: "well it wont do what you're trying to do, so it wont work properly"

T: "so will it work?"

Me: "no."

T: "wrong. It will work, but it will change everything in the database, which we dont want"

Thats what I was saying??

Also, he spent 50 mins out of our hour lesson explaining how to use SELECT, INSERT, UPDATE, and DELETE. I just wanted to get on with the work tbh.

I'm gonna have a serious talk with my bosses the day after tomorrow. We have so much to do, we are basically at 150% workload. Problem is: they don't pay us for overtime.

This has been going on for 18 years in the company. It will not be easy. But they either start paying our overtime or I am out (and probably taking the whole dev team with me.)

Wish me luck!

Action takes place during demo to the stakeholders.
Manager : During the demo we will show a working prototype of new functionality. In this sprint we focused on that feature not on UX. Please do not pay attention to UI and focus on business values
*Dev starts sharing screen*
*1 sec after*
Executive : This is unacceptable. It looks gross, why you don't use default controls.
Manager : We did, this is how they look like, but please do not pay attention to UI, it is not finished
*Dev continue presenting*
*1 sec after*
Executive : I see missing comma in that sentence. It is unacceptable to show features in that state, lets move on to another team.

It was really large feature working as a charm, but they focused entirely on unpolished UI :/

Supervisor: so you're going to write a perl script that will compile a jar that will be used to invoke a web service
Me: okay. What does the web service do?...
Supervisor: I'm not sure how it works. It'll just return a success or error code
Me: so I'm just going to invoke a black box?
Supervisor: that's a good way to think of it
Me: so how does the qa process work with this black box/how can we debug?
Supervisor: we don't have qa for it and we can't debug

What the fuck?!?!? You expect me to call a literal fucking black fucking box?!?! This isn't lambda calc you jabroni.

Reject original specs. Do the bare minimum MVP that works and solves problems people actually have, and not problems you think people have.
Improve it if needed.

In my experience, software projects don’t live long enough to outgrow the MVP. If they do, it happens way down the road. At that point, business will change, and the original spec will become irrelevant.

It’s a paradox: 90% of the spec was discarded, but the business is happier than if we followed the spec word by word.

Also, static typing and unit testing solve nothing. I’m sorry.

3 person help desk shop for 450 users. One of my tasks is procurement.

Customer: we need a portable monitor that takes up less desk space than the one you typically have us buy

Me: at the conference last week we displayed the upgraded model of that portable monitor which takes up half the desk space. It’s $250 instead of the $150 that you normally would pay.

Customer: that ones too expensive, find me something else.

Me: unfortunately not too many companies make portable monitors and since AOC is unreliable in quality we have been recommending Asus, who only makes those two models that I’ve shown you.

Customer: I want the AOC one anyways. You shouldn’t have shown the more expensive one because now my staff want it and I can’t get it. If everyone can’t afford it you shouldn’t have it available.

Me: I understand your frustration, we have recommended that more expensive one as an option for people who have special accommodations for eye care and as an alternative if people dislike the current model. Since it’s not required that you purchase it and since we do have a much less expensive option we will continue to recommend it. As for the AOC one we will allow you to purchase it but will not be supporting or repairing it.

Customer: Can we get this instead? *sends link to $989 pre tax off brand version of Razer Project Valeria*

Hey junior... when I'm asking a question it's not the answer I'm looking for.... It's your thought process! Just tell me the things you will not do and we can take it from there!

If you haven't seen silicon valley... Do... For the love of God do.

And if you don't like it one... We will never get on, it's god damn hilarious ... Constantly

3rd time I've watched them all

It's perfect.

I applied for PHP Developer

Interviewer: What is interface?
Me: it is class with unimplemented methods?
Interviewer: But why we use it?
Me: it acts as a contract so you can assure that
on implementing interface developer will follow
the same architecture.
Interviewer: that's okay but why is the need for an interface at first place?

I was irritated with the interview process as he was smirking
every time I answered.

Me: I never get a chance to do that kind of research. Truth is
even if you hire me your manager will declare the unrealistic deadline and won't care if I comment the code or know why we really need to implement an interface.

After he did not smile and I left the chair.

PM: We have to do this this and this. How long will it take you?
Me: Looks like a 4 hr job
PM: ok
Me: Still not complete after 2 days

Me every time :D

So my friend was in a hurry when she was setting up the passocde for her phone and later she forgot the code.
So she takes it to the service center.

SC guy: Ma'am we have to do bla bla bla. And you will lose your data. It will cost you around $10.

She just came back and later gave me the phone.
*unlocks bootloader *
*flashes a custom recovery*
*delete passcode file*
Phone is now unlocked with all the data intact.

PS: I got a small treat at McDonald's. 😋

Client : We need this feature

Team lead : Sure, we will deliver this to you in 3 days.

Meanwhile Teamlead forgets to work on it or assign it to anyone in the team while he was surrounded by many other tasks.

Client on 2nd day morning : What's the progress on that feature?

Teamlead to Client: It's going fine, we will deliver it to you on time.

Meanwhile, Teamlead to a junior developer in the team (on 2nd day afternoon): We have this priority feature where we need to finish it in one day and deliver it tomorrow!

Junior Dev to Teamlead : This is too much of work to complete it in 1 day, it atleast needs 3 days!

Teamlead to Junior dev : I don't care, can't talk, busy, just complete the work and deal with the client, bye.

And the Junior dev continues to struggle where he is unknown of the fact that the task actually was of 3 days but just because the Teamlead forgot to do the task and also to assign the task early, he is in trouble!

I don't like how being an entrepreneur is glamorized these days.

People make you think that just starting a company will make you rich.

But we don't really pay attention to the hundreds of startups that fail each year. (And that could very well be you).

We only pay attention to those that do make it.

I honestly don't get too mad when people aks me to do things like install programs for them. This is not my dayjob, but when you think of it, they're right when they say "you are a programmer so you must know how to do that". We do know how to do that. When you have a question about plants and you know a farmer, you are going to ask the farmer, even though he is not a gardener. He will know. Just as we know how to use computers very well.

HAPPY NEW FUCKING YEAR BECAUSE IT WILL SUCK WAY MORE THAN THE LAST ONE AND CAN WE PLEASE JUST FUCKING STOP CELEBRATING AND GET BACK TO WRITING FUCKING RANTS AGAIN?! BECAUSE I WILL FUCKING DO!

Our internship and placement tests start from 30th and this is message we got from our coordinators.
😤
(We do have WiFi on campus and in labs ,idk why they aren't letting us use that!!)

They are asking use to use the DONGLES ! who the hell has those, these days !
Uni's response to this : if you can't get your own internet source,then don't give the test. (Translation : we don't give a single flying fuck)

Got my self a Jiofi ,I hope it would work fine.

BUT !!!!!!!!
Often our phones catch no network in the labs ! And if they do,the internet speed is slow.

The tests will go GREAT ! 🙃

Dev: I need you to do X

IT: Ok we will do Y

Dev: I don’t want Y I want X

IT: Well you’ll need to go through the change request process then since you have just modified your requirements.

Dev: …

I don't always leave my job..
But when I do, I leave a bunch of shitty code that will make the next developer suffer.

That's what they get if they keep asking 'We need it now/today'

Me : I found this code issue, I think we need to fix it
PO: does it affect the user?
Me: not really but we can make it better
PO: do you have a defect for it in *insert issue tracker here*
Me: no, I just noticed it
PO: is there an IM ticket for it?
Me: I don't think so
PO: is this issue already in production?
Me: possibly. Yes. That's why I was wondering if we should fix it.
PO: okay then we will fix it in the 3rd release from now if you still remember it by then.

New boss: So, you'll do just some coding, we just need to restructure current DB.
Me: Ok

One month later...
Boss: So, we are creating new LMS in WORDPRESS (yeah, fcking wordpress) so you'll do this and that and...
Me: Oh, well I like challenges so let's see.

Another month later...
Boss: WE NEED OFFLINE MOBILE APP THAT WILL DOWNLOAD WHOLE FUCKING WP WITH EVERY SINGLE VIDEO AND EVERYTHING AND STUDENT WILL LEARN FROM THAT. WE ARE OPENING IT IN ONE MONTH.

Manager: Could you create the UI for the new feature? The client wants to test it. We need it in 3 days.

*1 week later*

Client: IT DOESNT WORK

Me: This is just a visual demo... but everything will work when we realse the feature.

Client: okay but can I see what it will do?

Of course you can! Just wait until we relase it!

*2 weeks later*

Manager: What are you doing?

Me: Working on the UI for the new feature.

Manager: Wait, hadn't you already done it for the demo?

Me: That UI didn't really work. It was basically a bunch of HTML, without reactivity or abstraction or any functionality.

Manager: Okay, how much where you able to re-use?

Me: almost nothing.

Manager: So... you wasted those 3 days?

Oh so I'm the one who wasted 3 days.
Me: Kinda, yeah

Manager: Why couldn't you have done this when I asked you to do the UI?

You can't expect good quality code in 3 days. Pls stop wasting it on demos.

A conversation that me and my boss had this week:
Boss: "Hey, why is this not progressing"
Arcsector: - "We're waiting on system users to move their destinations"
"We need the system in the database in order to move it"
- "Okay awesome - let's move it, oh wait, I can't do it because I don't have access, here's the stuff that needs to be done: a, b, and c"
"Oh I'm actually not able to help with that"
- "So then how are we supposed to get it done?"
"idk but also this other issue is something missions are complaining about"
- "oh I already am talking to them about it and it should be remedied by the team creating the problem because it's a false positive"
"Well we need to solve it still"
- "We would've solved it already but it has dependencies with other projects that we're still working on because we don't have enough people"
"We cant get you more people because we don't have the budget"
- "Then this stuff will have to wait"
"Get it done"

ACTUALLY SCREAMING! Why cant people understand that there are conesequences for their actions??!!

It astounds me that people will actually pay thousands of dollars to come to a bootcamp and just fuck around...

Like we will spend an hour going over materials and concept and when it comes time to apply it and build something the kid next to me never knows what's going on! And then always asks me how to do it.

I tried being positive about it and be like hey if I can explain it to him...then that means I really know it!

Fast forward a couple weeks and I'm ready to strangle the kid.

He will sit on his phone playing games the whole time the lesson is going. Then when the lesson is over, put his phone down and immediately ask me how to do it...

The fuck!? Maybe if you'd just listen you'd know wtf you're doing by now you useless vapid brainless twatwaffle!

*me teaching someone to code*

Me: So what do you think will happen when we run this?
Student: ummm... I don...🤔
Random: I KNOW! It does xyz 😄
Student: agh yea, it does xyz 😅
Me: (ffs) 😐

Nothing gets learned in the end 😮

My boss: "We need this feature by Friday"
Me: "I can make it work, but I need more time to do it properly"
Boss: "Just fix it by Friday, and you can make a proper implementation later, when there is time"

Like there will ever be time once it works...

Let junior dev design module.

Make code review.

What junior dev says: "It is a totally flexible concept!"

What junior dev means: "It is extremely shitty to use for the one use case it was meant to do, but it will be equally shitty to use for all the use cases we will never have."

Back to square one.

Looks like Keybase now also has its own shitcoin. Isn't it about time for that cryptocurrency wank to end already? How many more BitconneeeEEEECT's do we need?

But but but.. this is the next big thing! It will go *stellar*!

Backstory: Offering manager brings a project through a few months of requirements gathering / feasibility study etc. Project spends 8 months with a R&D team to flesh out. Our team gets 6 months to turn it into a ship able product. 4 months in, offering manager calls a meeting.

OM: ok so you are all working on project X, well I need your input on something

Team: Ok, go ahead

OM: what do you think the app needs to do?

Team: ... I'm sorry?

OM: well we've been looking at it, and we don't think it does very much compared to existing apps. We need a killer feature but we don't know what. Any ideas?

Team: well we were looking at project Y originally, which was a lot more advanced. But you pulled the plug in favour of this.

OM: yeah, believe me customers will want project X a lot more. It just needs to do something interesting ... you know what I mean?

Team: not really, if it doesn't have anything, why did we go for it?

OM: ok I don't think I'm being clear. Point is, if anyone has any ideas let me know, we need to ship it in 2 months and it needs to be killer

I handed in my notice that week and was asked why ... let's just say I told them.

Boss: "Sooo.... How long will it take?"

Me: "Maybe we should agree on some processes and specify your wishes for the new feature first?"

Boss: "Yeah you're right.... But what do you think? Will you get it done til $deadline?"

...

Why am I even trying? Who needs project management anyway?

System design meeting with the client.

Client: We need feature X in the design document
Me: But feature X was not a requirement, so it's not in the document and we will not add it.
Client: But feature X should be a common feature today.
Me: That doesn't matter, it wasn't a requirement. And besides that you don't even need it today, the planned system doesn't even support feature X, so we couldn't implement it, even if it was mentioned in the design document.
Client: But we may need it some day, and what do you do, when we decide to enhance the system in a few years and we need that feature then?
Me: Then we make you an offer for feature X.
Inner me: You ordered a bicyle and now you want it converted into a delivery truck next year without charge. That's not how things work.

Guy: "We need you to update a few applications so we can get some new data. We have very important reports we need out of it!"

Me: "OK how soon do you need it?"

Guy: "Two days!! So we can start putting in the data then will have you create the reports."

...two days later...(in the spongebob narrator voice)

Me: " OK its done. Go in add the data you need then let me know so I can generate the reports."

....4 weeks later...still haven't heard from them and they haven't put in the data. Glad it was soooo important that I had to drop everything else to put in the updates that haven't been used.

HR: you didn’t write in your job experience that you know kubernetes and we need people who know it.

Me: I wrote k8s

HR: What’s that ?

…
Do you know docker ?
Do you know what docker is ?
Do you use cloud ?
Can you read and write ?
Are you able to open the door with your left hand ?
What if we cut your hands and tell you to open the doors, how would you do that ?
What are your salary expectations?
Do you have questions, I can’t answer but I can forward them. Ask question, ask question, questions are important.
What is minimal wage you will agree to work ?
You wrote you worked with xy, are you comfortable with yx ?
We have fast hiring process consisting of 10 interviews, 5 coding assessments, 3 talks and finally you will meet the team and they will decide if you fit.
Why do you want to work … here ?
Why you want to work ?
How dare you want to work ?
Just find work, we’re happy you’re looking for it.
What databases you know ?
Do you know nosql databases ?
We need someone that knows a,b,c,d….x,y,z cause we use 1,2,3 … 9,10.
We need someone more senior in this technology cause we have more junior people.
Are you comfortable with big data?
We need someone who spoke on conference cause that’s how we validate that people can speak.
I see you haven’t used xy for a while ( have 5 years experience with xy ) we need someone who is more expert in xy.
How many years of experience you have in yz ??? (you need to guess how many we want cause we look for a fortune teller )

Not much changed in job hunting, taking my time to prepare to leetcode questions about graphs to get a job in which they will tell me to move button 1px to the left.

Need to make up some stories about how I was bad person at work and my boss was angry and told me to be better so I become better and we lived happy ever after. How I argued with coworkers but now I’m not arguing cause I can explain. How bad I was before and how good I am now. Cause you need to be a better person if you want to work in our happy creepy company.

Because you know… the tree of DOOM… The DOMs day.

Customer: Do you have a 2GB RAM stick?

Me: Yes, we do. Do you know what you have and what you need?

Customer: Yes, I have a one-zero-two-four M-B stick and a two-zero-four-eight M-B stick.

Me: So... a 10-24 Meg stick and a 20-48 Meg stick

Customer: Yes.

Me: Ok.... and do you know if it's going to be DDR2 or...?

Customer: Yes, DDR2.

Me: Okay, yes, we do have some. And will you want us to install it?

Customer: No. I can install it. I've been putting computers together for 30 years, so I think I can do it.

Client : I am unable to download data from your sever for last 10 days.

Me : Sir, we are sorry to hear that. We are doing some maintenances on our server from this morning today. We request you to call back us in next 4 hours.

Client : But i am facing this problem for last 10 days.

Me: Sir, i heard you. As maintenance is going on it will not be possible to download data this time.

Client: From when this maintenance is going on?

Me: from this morning sir.

Client : but i am facing this probolem for last 10 days.

Me: Sir, you are not understanding it, or may be i am failing to describe the situation to you...

Client: Listen, you guys are incapable. Only knows to make excuse.

Me: Sir..

Client: Sorry to say, i am not Happy with your support. Let me talk to your senior tech guy.

Me : Sir, your problem will be solved in next 4 hours. We will call you as soon as our server went online.

Client: *.....*

It took me 20 minutes to finally make him understand the situation.

Client: Why did not you said that earlier? You guys will have all the time but i do not. Anyway.

He hangs the phone.

My ears are burning man...

"Disregard what you're doing now. We need a FUNCTIONAL prototype (which will become the main app because refactoring is a waste of time huehuehuehue) with these features our POSSIBLE client MIGHT potentially need for TOMORROW's presentation."

"What do you mean that thing you were working on yesterday isn't done? Those are the times we estimated, right? By the way, our (still not confirmed) client thinks he'll choose us over that other company if we do changes A, B, C and D. Need it for yesterday."

Client: I want a new feature for my chat bot. It should be able to rap.
Me: ... k
*monologue: wait u w0t m8*
Also me: Can you please go more into the details? It should be able to rap. Ok. But how do you want it to look like? How "strong" should be the discrimination level, for instance?
Client: It should beat ass, yo.
Inner me -> core me: Let us just ignore him. We won't be able to do it, since he isn't really explaining his needs. "It should be able to rap". We are not wizards.
Core me -> inner me: Chill. We will just use some insult apis, combine it with cleverb0t api et voila.
Me: Alright. I got an idea for it. I can do it within this week. And if you don't like it, I will ofc do some changes to it.
Client: Hmmm... that's nice and good. But within 1 week?
Inner me: I can't do magic and pull that feature out of my fucking ass!

Clients... clients... clients...
0. Don't expect us to be done in a few days. We are also humans. And not fucking machines.
1. Do us (all devs on planet earth. -Microaggression in 3, 2, 1..) a favor and (kill yourself) learn how to request a feature.

Hello world again, long time no rant.

Renewed interest in devRant after some of recent goings on:.

“Let’s define a new language”

“Why? There are lots of great languages out there”

“It will be domain specific and more user friendly”

“Why, there are plenty of other options with support and pedigree”

“We will properly define a grammar in Backus-Naur form, it’ll be great, maybe we can sub it out”

“Why, literally everything we do is already doable with the current tools, this will certainly be more trouble than it’s worth”

“They already gave us the money”

All aboard! Fun times ahead for the next decade...

Question everything!

Comments lie.. sometimes code does too.. Customers..they lie the most..and are sloppy..

Don't be like customers, don't be sloppy. If you were sloppy own it & don't lie about it!

Pick your fights (trying to fix vs rewrite the shit out of it)..you will know what to do more with experience..

RTFM & docs.. If things still unclear, ask before your dick gets stuck in a toaster!

Ask away, learn about the customers & how they use your product.. you'll be surprised how something intuitive to you might be a rocket science for them..meaning more room to fuck things up when using it..more ways you can adapt & prevent things..

Most of all, don't fuckin lie.. ever!!
If you lie on you're CV, we will find out.. If you fuck up something & lie about it, we will find out.. but it will cost us precious time when solving it from scratch.. People fuck up..that's a fact..how you go about it is what makes/breaks it for me. So don't ever fuckin lie to me!!

And don't be arogant.. if you complain about fixing bugs, this is not a job for you.. if you can't even fix the obvious ones you've put there in the first place..twice as bad..

So think before you code..what do you want to do, how you want to accomplish this, is it reusable, can it be extended, does it introduce new technology into the project, will it fuck up current setup.. once you have this shit figured out, code will write itself..

Did I mention already you're not to lie to me, ever?!

And don't try talking about me behind my back either..I've seen it backfire before, results were not good..

What do we have to give you to make you able to accurately predict the scope and length of time it will take you to develop something you know nothing about and have no experience with? How hard could it possibly be? You click a button and BOOM! A unicorn! Please provide estimate in hrs EOD.

They: You got the job! Du you acceppt?
Me: Let me think about it. Do you know what would help me deciding? Knowing if i could get 15% more.
They: We will check and let you know.

So lets see what will happen!

I HATE IT WHEN I HAVE TO BE NICE TO THESE KINDA FCKED UP IGNORANT PEOPLE

[11:10, 16/04/2020] +263 73 ...: Hi I want to develop an app do you live in glen view
[11:12, 16/04/2020] Softaz: Um in budiriro
[11:12, 16/04/2020] Softaz: What do yu have in mind
[11:15, 16/04/2020] +263 73 ....: There's an idea I've been testing and its about creating an app thats track patients with the covid virus the people they have infected even before the infected ones test positive
[11:16, 16/04/2020] +263 73 4....: What do you think about this coz this is not a money generating project but we will do it for humanity
[11:17, 16/04/2020] +263 73 4...: We will finish the project in less than 3 days coz I've got the research covered and how the app will operate I jus need someone who can punch the code
[11:22, 16/04/2020] Softaz: Its a good idea
Though your time frame is too tight

What platform will this app run on?
[11:26, 16/04/2020] +263 73 47...: About the time frame its becoz its a very simple mechanism

Client : We want to develop this particular software. While developing it, we will be following Agile methodology.

Developers: Sure.

After developer achieves few features and decides to give 1st Demo of the software to the client.

Client : Wtf is this? This is an incomplete software, there are bugs in it.

Developer : Yes, you point that out to me and I will solve them.

Client: What do you mean point them out for you l, couldn't you do it yourself?

Developer: As a standard method, we often do unit tests, but we are not testers and with a strict deadline to match, we are more on the core implementation then checking again and again for minor bugs.

Client : I thought it would be a full proof software without any bugs in the 1st demo.

Developer : Software development is a process. It's not straightforward, hence you only mentioned at the initial, it's agile.

Client : If that's so, let's make it not agile and make you rot in hell for the next few fays. Now you next time show me a demo with no bugs, great complicated features and we will not mention you our expectations, predict them by yourselves, and most importantly, here's an impractical strict deadline.

Devs: Can we please get adequate hardware to do our job correctly? Please, just a new set of larger monitors.
Lower management: Sure, this is going to be easy.
Upper management: Wait what? This will cost us around 500€ times 10? Any maybe in the end other departments will want that to, so make it times 100.

We're a 4+ billion company ... but yes, please, I love scroll bars and they make my work so much faster.

Planning.
- Sales people: we will deploy and install 100 customers by the end of the month.
Meaning: 100 it's impossibile, we want actually do 50, but we set a high target so people will sweat their ass off. But we don't tell them the truth.

- Tech people: no way, we will deploy and install no more than 25!
Meaning: we could do 100 but we would die. We will guarantee 25, but since we are good we will optimise the workflow and maybe we will make it to 50. But we don't want to create expectations.

Big misunderstanding arise if these two language are used in the same meeting.

At least if I'm in the meeting as technical people

My company decided to reinvent the wheel by writing its own queue system instead of using the existing message queue service.

And it uses plain PHP with exec() to run the workers.

Where do we store the job? We use mongoDB which is already used in our existing projects. We can query the collection/table each time the queue service start, execute the jobs, and let it exit if there's no job anymore. Don't worry, systemd will start the queue service again once it exits.

How to monitor the workers? Yep, we use ps and grep to check if the worker's PID still exists in the OS.

What about error stack traces? Nice question, we redirect the stdout and stderr when exec()-ing into a file.

What about timeout? We don't need it, let's just assume no one is going to write while(true).

It works flawlessly! /s

Coming up to (very) tight deadline..

Manager - "Stick in a temporary fix, if the data is mocked out it will do for the demo. We really want to show this feature."
Me - "Okay, I"ll pick up the technical debt after the demo."

*Changes are coded and rolled out*

Manager calls me over to his desk..

Manager - "This feature isn't bringing back real data."

Do these kind of people exist in all companies?

Boss: we will build mobile app with web app.
Me: absolutely yes.
Boss: you will do the mobile app (iOS)
Me: absolutely , yes I'm iOS developer.
Boss: you will do the android app too, we can't hired an android developer.
Me: absolutely, yes.(but I need to learn it first).
Boss: you will do the web app , it's difficult to find good web developer)
Me: absolutely,yes . I'm Ruby on Rails developer.
After a while........
Me: do I have a bonus ,sir.
Boss: ...............
(there is no response).
Me: ....................

My Boss, another employee and me were having discussion on a functionality on the website "How we will do it". After talking to us, my boss called his former employee and asked him the same question "How we will do this functionality".

After talking with the former employee, he comes back and tells us the same that we told him on "How we going to do it". Which pissed me off and I am angry on him, why the fuck does he has to call the former employee about this.

What do you guys think, should I be angry?

Day 2 in ComSci class (following my last rant)
"Okay, so! All of the schoolwork and homework will be done on paper and pen, submit and I will grade it. Only once, no second chance"

Okay. Okay. This went over my head. What are you gonna do? OCR the code into the compiler, compile it and run to see if we fucked up to give us an F? What are you, god? Here's a brilliant idea, teach them Assembly! Guaranteed error to give us Fs! FUCK YOU

Today somebody claimed they have the "copyright" of responsive websites.

First of all, I'm here for almost a year now, but this is my first rant. Hello guys!
(linuxxx, call me)

This didn't happen to me.

So, it begins like this:
Some client called us and said "[INSERT_COMPANY_NAME] called us and said they have the copyright of all responsive websites, asking money."

I hanged up, laughed hard and visited [INSERT_COMPANY_NAME] website and saw this:

- Each website that uses the solution must report the domain name in order to register it.
- If a company undertakes web site design, it is the company responsibility to inform and record.
- Any unauthorized website will be considered unauthorized and a violation case will be opened.
...

Pricing (Currency Converted to Dollars)
1 Website ~$260
2 - 10 Website ~$1300
...

Well, eventually I reported this to government. I unmasked this fraud.
OR DID I?

Their site is saying this now: "We do not serve this to anyone except government now, you are making nonsense and we do not want nonsense."

So I posted it on a forum, asking what can we do.

We are suing this company now. Yeah, I said "we".

PS: If we cannot win this, I'll get the copyright of subdomains.

Just realized, we can double tap on any post here...and it will be added as ++. Like we do in instagram.

How I didn't knew about this from so long.😅

Can we agree to from now on do all our sylesheets like this?

Honestly. It takes a bit of work organizing everything but bloody hell is it easy to use.

PS I just started a decent chunk of those #ID's will be replaced it's just to build the UI up.

Also you get a + if you can guess what ui I am trying to recreate. 😂

Microsft (before Win 8 ): we have to fix the blue screen of death! People are pissed off seeing it appear again and again.

Windows: We will do something

*In its remastered blue screen - adds a sad face emoji, changes the shade of blue, and inserts a QRCode for the user to play with in the meantime*

Microsoft ( after win 8) :Good Job Team, it looks great now, people are gonna love it, especially the QRCode feature!

Fucking hate when business people says this to me:
- You have no time to do this, we will find somebody else to do it. (EXCUSE ME? how do you know I have no time? If have no time I WILL TELL YOU)
- Your team is too busy, we will outsource that (IF THAT it's a priority, we WILL DO THAT, fuck you, I'll tell you if we need to outsource or not)
- Requirements are too complex to do now. We will think about it and we will tell you, maybe it's just enough to add a column to db (WHAT? WHAT THE FUCK IS too complex? I didn't even see anything we can call requirement, nor speak with relevant people, so how do you fucking know they are complex if you don't know shit about dev and our platform)

Conclusion
It's true, I have no time, because I don't fucking understand what do you want, so I'm running all day and night doing useless things.

caution: just some dude sharing a random story.

started my own small business around half a year now. a month earlier from that my cousin also started his career as a self employed dev with his own small business and we work together.

next year we we will start a company together, where we merge our existing small businesses into one. we are developing software on our own and we design and implement software for our customers.

seems like we are doing something right because we are reaching our capacities almost all of the time.

we plan to hire apprentices (hope it's the right word) and to teach them all we know to be able to then increase our possible workload.

you know, I do not have a degree or some form of education in the field of IT. And here in germany it was almost impossible to land a job as a dev. needed my cousin who studied cs to get me my first position in that field - and even with his reputation it was not easy.

this shit will not happen on my watch. If I see someone with fire for development I will give them a chance, irrespective of their background. And I will be more than happy to let that person grow and to give every kind of support I can.

we also plan to have something like "if the employee has a good idea for software that sells, we will support it and share revenue". got to figure out the details on that one, but I want to give the employee the possibility to grow some passive income out of their normal job - because for me this was never an option. and I think that this will motivate in some way 😅

just wanted to get this out of my head 😣

Tommorrow is the day! The day we realease on! And I still don't have a final frontend to integrate, build, test and prepare to deploy.

So tonight is the night! The night I will be doing webdesign and googling how to do it with my 'functionality beats design' and 'terminal is the best UI ever' attitude :-)