Boss - gives tasks to me. Timeline: 10 days.

Me - work hard and finish the solution in 3 days.

Boss- wtf is this. Do it properly.

Me - chills for 15 days. Submit the same earlier solution after that.

Boss - yes this looks nice now! Much better than your earlier work!

Me - dude seriously what kind of stuff do you smoke before coming to work?

[Thursday afternoon on a call...]

Client: Before we get started, can you create a sitescape outlining all of the pages and sections of the new website?

Me: Sure! I'll go through the website and shoot you a full layout in xls format as soon as possible, that way you can easily make notes on what you want added, modified or removed.

[Two hours later...]

Client: Hey, did you build that sitescape yet?

Me: Actually, I've been on back-to-back calls with other clients.

Client: So when are you going to get it done?

Me: Well, I have to go through the current website in it's entirety, which I'm guessing is about 1,000 pages. I have to determine which pages work fine on their own, which need to be combined for better presentation and which should be removed due to redundancy. That's something that is tedious and takes some time to complete. That, in combination with having an existing work queue that I need to fit you within and being at the end of the work week, we're looking at Tuesday morning to have it ready.

Client: "Existing work queue"? This is ridiculous. We're paying you good money to make our project your only priority. If we wanted to wait days for work, we would have saved money and paid for a cheaper service. You're already gouging us as it is! If we don't get the sitescape by end of day Friday, we're going with another company.

Me: I would tell you that I'm sorry for the inconvenience, but I'm not. I'm not going to feed you a line to make you happy. I'm also not going to work on my days off just to rush something out to you. You hired us because you wanted things done right, not quickly. Your current website is the result of not focusing on quality, but by how fast you can deliver it. We don't work that way. We only build quality products.

By rushing your project, not only do we alienate our current clients, affecting our reputation, but we build product of less than the highest quality. That will upset you because it isn't perfect, and it reflects poorly on us to use it in our portfolio.

If you want to hire someone to pump out this project to your unrealistic deadlines, be our guest. But you paid a 50% non-refundable deposit, so not only will you lose money, but your end product will suffer.

I'm going to let you sleep on this. If you decide tomorrow that another direction is the way to go, we wish you luck. But please understand that if we conclude our business, we will no longer make ourselves available for your needs.

Please find the attached contracts you have signed, acknowledging the non-refundable deposit, as well as the project timeline and scope, of which a "sitescape" was never originally mentioned or blocked out for time.

I hope that tomorrow we can move forward in a more professional manner.

[Next morning...]

Client: My apologies for yesterday. We're just very anxious to get this started.

-----

Don't let clients push you around. Make them sign a contract and enforce it whenever necessary.

Somehow I feel like I personally owe Linus for git.

17:50 Colleague whispers "fuck" and the entire project we've worked on for the last half year responds with 404.

17:55 A quick diagnosis shows that she wrote "rm - rf ../" instead of "./" when she threw out her staging dir an thereby deleted everything.

17:58 git pull, everything is back.

18:15 everything is configured and we're up and running again.

**Alternative Timeline without Version control **

17:58 We start looking through Backup folders

18:20 We're fairly confident to have found the most up to date Backup in /var/backup/newback/v2/june/new/released/ and start copying back into the project directory.

19:30 Some files are missing we start patching shit up.

19:40 I realize how much work went down the drain and start strangling my colleague. The Api seems to do the most important things again.

20:00 My colleagues dead body is hidden and I'm 80% confident that the tasks depending on us should run.

Next day: They didn't run. Every nightly build failed, nobody can do anything useful.

A week later : Shits starting to work again, all lost files are replaced. Replacement for dead colleague still missing though.

It's moments like this that make you really appreciate the luxurys we have nowadays...

Client: Can you provide some kind of guaranteed timeline that you're going to be able to move our website to our new servers with the optimizations implemented? I know you said it should take a week, but we have 3 weeks to get this moved over and we cannot afford to be double billed. I'm waiting to fire up the new server until you can confirm.

Me: As I said, it SHOULD take about a week, but that's factoring in ONLY the modifications being made for optimization and a QA call to review the website. This does not account for your hosting provider needing to spin up a new server.

We also never offered to move your website over to said new server. I sent detailed instructions for your provider to move a copy of the entire website over and have it configured and ready to point your domain over to, in order to save time and money since your provider won't give us the access necessary to perform a server-to-server transfer. If you are implying that I need to move the website over myself, you will be billed for that migration, however long it takes.

Client: So you're telling me that we paid $950 for 10 hours of work and that DOESN'T include making the changes live?

Me: Why would you think that the 10 hours that we're logged for the process of optimizing your website include additional time that has not been measured? When you build out a custom product for a customer, do you eat the shipping charges to deliver it? That is a rhetorical question of course, because I know you charge for shipping as well. My point is that we charge for delivery just as you do, because it requires our time and manpower.

All of this could have been avoided, but you are the one that enforced the strict requirement that we cannot take the website down for even 1 hour during off-peak times to incorporate the changes we made on our testbed, so we're having to go through this circus in order to deliver the work we performed.

I'm not going to give you a guarantee of any kind because there are too many factors that are not within our control, and we're not going to trap ourselves so you have a scapegoat to throw under the bus if your boss looks to you for accountability. I will reiterate that we estimate it would take about a week to implement, test and run through a full QA together, as we have other clients within our queue and our time must be appropriately blocked out each day. However, the longer you take to pull the trigger on this new server, the longer it will take on my end to get the work scheduled within the queue.

Client: If we get double billed, we're taking that out of what we have remaining to pay you.

Me: On the subject of paying us, you signed a contract acknowledging that you would pay us the remaining 50% after you approved the changes, which you did last week, in order for us to deliver the project. Thank you for the reminder that your remaining balance has not yet been paid. I'll have our CFO resend the invoice for you to remit payment before we proceed any further.

---

I love it when clients give me shit. I just give it right back.

Manager: Alright, we've decided we're gonna just going to accept PayPal and also credit card checkout through PayPal in the next two days!

Dev: ...

Manager: We can achieve this timeline, right?

Dev: ...

Manager: Alright, awesome to see your motivation! Let's do it!

Dev: YOU ANSWER PHONE CALLS, TALK TO PEOPLE AND 'STRATEGIZE' ALL DAY. YOU DON'T HAVE TO RELY ON THOUSANDS OF PEOPLE USING THE APP WITHOUT ERROR. THAT'S ON ME, NOT YOU, SO JUST SHUT THE FUCK UP!!!

Manager: ...

Dev: ...

Senior manager calls me at 3pm today. I’ve known about this issue since last Friday, one of her pions told me to hold off until Thursday when he’s back in the office and that I could prioritise other tasks.

I have another task with a deadline of the 21st with the potential for fines if it’s not done.

Snr manager: “I’m calling to see how this is going”
Me: “cool, it’s not, bigger problems in the world”
Snr manager: “waah, this has to be done Monday or we face the potential of a court case, fines, this is the biggest problem in the world”
Me: “I’ve known about this issue for a week, have been told not to worry too much and nobody has mentioned the impact or timeline you’ve just given me.”
Snr manager: “so can it be done for monday”
Me: “no chance”
Snr manager: “why not?”
Me: “because it’s 3pm Friday and I have 1 hour of Work left, good luck”

My manager was in the room, he got an arsey call soon after. I don’t really care how that one went but he’s a good guy so I’m sure it was fine.

I also had the joy of asking: so give me an idea of the potential fine... to which they wouldn’t give me an answer.

I need this to weigh up which of the potentially finable tasks takes priority.

The other team that had trouble told me all the dates, gave me over a months notice and the scale of the problem.

If you want someone to help: be polite, give them as much warning as you have and be absolutely honest.

The job’s done cause I’m a fucking legend. But they’re not gonna find out until 5pm Monday. That’s the dickhead tax, they get the dickhead tax for being dickheads.

I’m gonna spend Monday working from home, incommunicado. Fuck incompetent arseholes.

Enjoy your weekend everyone, I know I will mine.

At the data restaurant:
Chef: Our freezer is broken and our pots and pans are rusty. We need to refactor our kitchen.
Manager: Bring me a detailed plan on why we need each equipment, what can we do with each, three price estimates for each item from different vendors, a business case for the technical activities required and an extremely detailed timeline. Oh, and do not stop doing your job while doing all this paperwork.
Chef: ...
Boss: ...

Some time later a customer gets to the restaurant.
Waiter: This VIP wants a burguer.
Boss: Go make the burger!
Chef: Our frying pan is rusty and we do not have most of the ingredients. I told you we need to refactor our kitchen. And that I cannot work while doing that mountain of paperwork you wanted!
Boss: Let's do it like this, fix the tech mumbo jumbo just enough to make this VIP's burguer. Then we can talk about the rest.

The chef then runs to the grocery store and back and prepares to make a health hazard hurried burguer with a rusty pan.
Waiter: We got six more clients waiting.
Boss: They are hungry! Stop whatever useless nonsense you were doing and cook their requests!
Cook: Stop cooking the order of the client who got here first?
Boss: The others are urgent!
Cook: This one had said so as well, but fine. What do they want?
Waiter: Two more burgers, a new kind of modern gaseous dessert, two whole chickens and an eleven seat sofa.
Chef: Why would they even ask for a sofa?!? We are a restaurant!
Boss: They don't care about your Linux techno bullshit! They just want their orders!
Cook: Their orders make no sense!
Boss: You know nothing about the client's needs!
Cook: ...
Boss: ...

That is how I feel every time I have to deal with a boss who can't tell a PostgreSQL database from a robots.txt file.
Or everytime someone assumes we have a pristine SQL table with every single column imaginable.
Or that a couple hundred terabytes of cold storage data must be scanned entirely in a fraction of a second on a shoestring budget.
Or that years of never stored historical data can be retrieved from the limbo.
Or when I'm told that refactoring has no ROI.
Fuck data stack cluelessness.
Fuck clients that lack of basic logical skills.

Small company (1-100 people).

The head of the company comes into the 4-man engineering department and tells the RF engineer that the wireless project will be canceled. The project timeline the RF engineer proposed the week before is not feasible for the company.

RF engineer asks, point blank, if he should pack up and leave. The guy says "no".

A few weeks later the RF engineer puts in his letter of resignation. The head of the company pulls him aside and asks why he's leaving. Wants to know what went wrong...

THE F***ING RF GUY WON'T BE DOING RF, THAT'S WHY!!!

Management at this company is so confused.

(Had to rant. I hear that's what this site is for...)

I'm really close to just quitting coding all together. This job is sucking the life out of me. I've lost my interest in code and the idea that there are better jobs out there.

My "boss" who's not even really my boss but behaves like he is, is micromanaging my every tag, and is an information hog. He doesn't document, he doesn't tell me anything, I've been here six months and still don't know half of what I need to know to do my job properly!

I'm expected to implement a new responsive design, but we don't have design specifications.
Cool, you'd think, new ideas, complete overhaul! Let's get a good foundation in bootstrap going!

WRONG! It needs to fit in with the old, fuck- ugly pre 2000 design.

Not because of any design constraints in particular, but because HE wants it that way. You know what was fucking trendy in 2000? Tables. Tables fucking everywhere. YOU KNOW WHAT TABLES ARE NOT? RESPONSIVE YOU FUCKING ICE LOLLY CHEWER!

We have no development timeline, no process management, no fucking project management. THE FUCKING PASSWORDS WERE STILL STORED IN PLAIN TEXT UNTIL LAST MONTH YOU IRRESPONSIBLE BANANA DEEPTHROATER! 😤😤😤😤😤😤

I'm doing my best here to get something resembling the old page, but there needs to be some fucking compromise! We are in fucking 2017, let's work with Bootstrap instead of against it, how about that you fucking bald cactus!

I know enough about UI to know that the way we're going, this is just going to be another unusable fucking clusterfuck.

YOU KNOW THE BEST FUCKING PART? I'M A FUCKING BACKEND DEV AND I WAS HIRED AS SUCH! GIVE ME A DESIGN TEMPLATE AND I'LL DO MY BEST TO IMPLEMENT IT, BUT FUCK YOU FOR EXPECTING FRONT END LEVEL DESIGN KNOWLEDGE YOU DUMB FUCKING SPAGHETTI!

I have been strongly considering writing a small fb app today named something along the lines of "Hack your fb friends - for realz". Then add basic oauth (You have to login to pick the friend to hack duh), retrieve their friends list and then publicly post to their own timeline and the friends they chose humorously stating they attempted to hack the persons account "for realz". You know just enough to alert people that the "hacker" is a idiot with bad intentions but with just humour enough to fall under "satire" so fb doesn't remove it.

If your bored please feel free steal and implement my idea, it's hereby open sourced and I will even fund this shit on kickstarter 😂

The sheer ignorance on my Facebook timeline makes me glad this community exists

Electron apps are now “normal” and even considered “better” than native ones.

How the fuck did we get to this dystopian timeline of a situation.

At a certain client, was asked to help them with an "intermediary" solution to stopgap a license renewal on their HR recruiting system.

This is something I was very familiar with, so no big. Did some requirements gathering, told them we could knock it out in 6 weeks.

We start the project, no problems, everything is fine until about 2.5 weeks in. At this point, someone demands that we engage with the testing team early. It grates a little as this client had the typical Indian outsourcing mega-corp pointey-clickey shit show "testing" (automation? Did you mean '10 additional testers?') you get at companies who put business people in charge of technology, but I couldn't really argue with it.

So we're progressing along and the project manager decides now is a great time to bugger the fuck off to India for 3 months, so she's totally gone. This is the point it goes off the rails. Without a PM to control the scope, the "lead tester," we'll call her Shrilldesi, proceeds to sit in a room and start trying to control the design of the system. Rather than testing anything in the specification, she just looked at the existing full HRIS recruiting system they were using and starts submitting bugs for missing features. The fuckwit serfs they'd assigned from HR to oversee this process just allowed it to happen totally losing focus on the fact this was an interim solution to hold them over for 6 months and avoid a contract renewal.

I get real passive aggressive at this point and refuse to deliver anything outside the original scope. We negotiate and end up with about 150% scope bloat and a now untenable timeline that we delivered about 2 weeks late, but in the end that absolute whore made my life a living hell for the duration of the project. She then got the recognition at the project release for her "excellent work," no mention of the people who actually did the work.

Tl;Dr people suck and if you value your sanity, you'll avoid companies that say things like, "we're not in the technology business" as an excuse to have shitty, ignorant staff.

*In the final weeks of development with a project on a short timeline because the client "needs it".*

Client: "We've hired a consultant we want you to work with."

Me: "Okay, can we push this to after the delivery?"

Client: "Of course"

Wake up to an email from the consultant with a list of scripts he just ran on the production database server for the currently live app.

Get follow-up emails about bugs and app crashes from the client.

My rage is so hot it can keep warm an Eskimo tribe over the winter season.

Memo on August 4th: Staff, we're moving to the new building. IT, make sure the building is ready by September 15th.

IT: But the entire networking, surveillance, fire suppression (yes, we do that too) and power management systems have to be installed/redone.

Management: What's so hard about that? Just get it done.

Memo about a week ago: Timeline for move shifted to September 9th

IT: Sir, this request is unreasonable especially since you still want us to go through the usual procurement process of hiring vendors to deal with stuff.

Management: So you mean to tell me you can't handle that in the next couple weeks?

IT: We're a large organisation with ~300 employees. The data centre in the new building isn't even usable yet.

Management: I don't care. Make sure everything is placed and operational by the 5th. Stop making a mountain out of a mole hill!

Unity3D Game Dev Interview

Interviewer: What is reflection and why would you use it?

Me: Gives overview of system and how I've used it in games before.

Interviewer: Sorry that was a trick question, Reflection is really dangerous and slow. You need to go back and learn the basics.

Me: ???...

A huge portion of Unity is built upon Reflection based systems, the entire Monobehaviour base relies on it. Their events system uses it, animation and timeline. I guess their team needs to go back to the drawing board.

How is this person a senior dev?

Why management has such orgasmic attachment to numbers?

Example 1.
Mngr: split this into tasks
Me: done
Mngr: now estimate these tasks
Me: can't. Team is new and codebase is unknown. Any estimations would be subjected to huge error and I will not commit to anything if I'm not at least partially sure.
Mngr: but we need some timeline
Me: so give it yourself. I'm not doing it

Example 2.
Mngr: we need to measure how your knowledge sharing sessions impacts our organisation
Me: how?
Mngr: e.g. amount of bugs lessen in next quarter
Me: bugs can go up and down because of hundred other reasons. Also, knowledge sharing is just to inspire people, it's up to them if they keep educating and growing. Me sharing knowledge 1h per week, I can't guarantee they will understand and apply this new knowledge.
Mngr: but we need to measure it somehow, otherwise it is useless.
Me: <speechless facepalm frustrated>

Bloody shit, I hate all the hypes right now.

Seemingly everyone is going from 0 to zealous hype at the moment...

Be it Musk's fanboys (that arsehole must have a prolapse), the mfucking GPT chatbot or anything else.

Everything's hyped up and noone talks about normal stuff...

... and when you point that out, everyone gets angry for reasons I cannot understand.

We had so many good inventions and progress in science this year (despite the world being pretty apocalyptic....), but seemingly everyone can only talk about either Twitter or their Twitter timeline. -.-

The Christmas bullshitting was hard enough each year, as it has nothing to do with being a festive event and love etc, but being just an commercial bullshit bingo...

But adding all the hypes makes the bullshit parade unbearable.

Dear Santa, please fry all the mobile electronics at Christmas, so we can talk about normal stuff and have a nice evening.

... Would be probably even better to just fry all electronics, even stone age was probably more interesting than the earbleeding conversations at the moment.

Worst collaboration experience story?

I was not directly involved, it was a Delphi -> C# conversion of our customer returns application.

The dev manager was out to prove waterfall was the only development methodology that could make convert the monolith app to a lean, multi-tier, enterprise-worthy application.

Starting out with a team of 7 (3 devs, 2 dbas, team mgr, and the dev department mgr), they spent around 3 months designing, meetings, and more meetings. Armed with 50+ page specification Word document (not counting the countless Visio workflow diagrams and Microsoft Project timeline/ghantt charts), the team was ready to start coding.
The database design, workflow, and UI design (using Visio), was well done/thought out, but problems started on day one.
- Team mgr and Dev mgr split up the 3 devs, 1 dev wrote the database access library tier, 1 wrote the service tier, the other dev wrote the UI (I'll add this was the dev's first experience with WPF).
- Per the specification, all the layers wouldn't be integrated until all of them met the standards (unit tested, free from errors from VS's code analyzer, etc)
- By the time the devs where ready to code, the DBAs were already tasked with other projects, so the Returns app was prioritized to "when we get around to it"

Fast forward 6 months later, all the devs were 'done' coding, having very little/no communication with one another, then the integration. The service and database layers assumed different design patterns and different database relationships and the UI layer required functionality neither layers anticipated (ex. multi-users and the service maintaining some sort of state between them).

Those issues took about a month to work out, then the app began beta testing with real end users. App didn't make it 10 minutes before users gave up. Numerous UI logic errors, runtime errors, and overall app stability. Because the UI was so bad, the dev mgr brought in one of the web developers (she was pretty good at UI design). You might guess how useful someone is being dropped in on complex project , months after-the-fact and being told "Fix it!".

Couple of months of UI re-design and many other changes, the app was ready for beta testing.

In the mean time, the company hired a new customer service manager. When he saw the application, he rejected the app because he re-designed the entire returns process to be more efficient. The application UI was written to the exact step-by-step old returns process with little/no deviation.

With a tremendous amount of push-back (TL;DR), the dev mgr promised to change the app, but only after it was deployed into production (using "we can fix it later" excuse).

Still plagued with numerous bugs, the app was finally deployed. In attempts to save face, there was a company-wide party to celebrate the 'death' of the "old Delphi returns app" and the birth of the new. Cake, drinks, certificates of achievements for the devs, etc.

By the end of the project, the devs hated each other. Finger pointing, petty squabbles, out-right "FU!"s across the cube walls, etc. All the team members were re-assigned to other teams to separate them, leaving a single new hire to fix all the issues.

"four million dollars"

TL;DR. Seriously, It's way too long.

That's all the management really cares about, apparently.

It all started when there were heated, war faced discussions with a major client this weekend (coonts, I tell ye) and it was decided that a stupid, out of context customisation POC had that was hacked together by the "customisation and delivery " (they know to do neither) team needed to be merged with the product (a hot, lumpy cluster fuck, made in a technology so old that even the great creators (namely Goo-fucking-gle) decided that it was their worst mistake ever and stopped supporting it (or even considering its existence at this point)).

Today morning, I my manager calls me and announces that I'm the lucky fuck who gets to do this shit.

Now being the defacto got admin to our team (after the last lead left, I was the only one with adequate experience), I suggested to my manager "boss, here's a light bulb. Why don't we just create a new branch for the fuckers and ask them to merge their shite with our shite and then all we'll have to do it build the mixed up shite to create an even smellier pile of shite and feed it to the customer".

"I agree with you mahaDev (when haven't you said that, coont), but the thing is <insert random manger talk here> so we're the ones who'll have to do it (again, when haven't you said that, coont)"

I said fine. Send me the details. He forwarded me a mail, which contained context not amounting to half a syllable of the word "context". I pinged the guy who developed the hack. He gave me nothing but a link to his code repo. I said give me details. He simply said "I've sent the repo details, what else do you require?"

1st motherfucker.

Dafuq? Dude, gimme some spice. Dafuq you done? Dafuq libraries you used? Dafuq APIs you used? Where Dafuq did you get this old ass checkout on which you've made these changes? AND DAFUQ IS THIS TOOL SUPPOSED TO DO AND HOW DOES IT AFFECT MY PRODUCT?

Anyway, since I didn't get a lot of info, I set about trying to just merge the code blindly and fix all conflicts, assuming that no new libraries/APIs have been used and the code is compatible with our master code base.

Enter delivery head. 2nd motherfucker.

This coont neither has technical knowledge nor the common sense to ask someone who knows his shit to help out with the technical stuff.

I find out that this was the half assed moron who agreed to a 3 day timeline (and our build takes around 13 hours to complete, end to end). Because fuck testing. They validated the their tool, we've tested our product. There's no way it can fail when we make a hybrid cocktail that will make the elephants foot look like a frikkin mojito!

Anywho, he comes by every half-mother fucking-hour and asks whether the build has been triggered.

Bitch. I have no clue what is going on and your people apparently don't have the time to give a fuck. How in the world do you expect me to finish this in 5 minutes?

Anyway, after I compile for the first time after merging, I see enough compilations to last a frikkin life time. I kid you not, I scrolled for a complete minute before reaching the last one.

Again, my assumption was that there are no library or dependency changes, neither did I know the fact that the dude implemented using completely different libraries altogether in some places.

Now I know it's my fault for not checking myself, but I was already having a bad day.

I then proceeded to have a little tantrum. In the middle of the floor, because I DIDN'T HAVE A CLUE WHAT CHANGES WERE MADE AND NOBODY CARED ENOUGH TO GIVE A FUCKING FUCK ABOUT THE DAMN FUCK.

Lo and behold, everyone's at my service now. I get all things clarified, takes around an hour and a half of my time (could have been done in 20 minutes had someone given me the complete info) to find out all I need to know and proceed to remove all compilation problems.

Hurrah. In my frustration, I forgot to push some changes, and because of some weird shit in our build framework, the build failed in Jenkins. Multiple times. Even though the exact same code was working on my local setup (cliche, I know).

In any case, it was sometime during sorting out this mess did I come to know that the reason why the 2nd motherfucker accepted the 3 day deadline was because the total bill being slapped to the customer is four fucking million USD.

Greed. Wow. The fucker just sacrificed everyone's day and night (his team and the next) for 4mil. And my manager and director agreed. Four fucking million dollars. I don't get to see a penny of it, I work for peanut shells, for 15 hours, you'll get bonuses and commissions, the fucking junior Dev earns more than me, but my manager says I'm the MVP of the team, all I get is a thanks and a bad rating for this hike cycle.

4mil usd, I learnt today, is enough to make you lick the smelly, hairy balls of a Neanderthal even though the money isn't truly yours.

For the first time I am feeling like.... I hate my job.

Agile and Scrum can be fucked, but at least there is a work methodology. I was hired by a company being run the old school way.

These guys never heard of git??
- Fuck you. We never used git and neither should you.

Client company does not want to give me push/pull access to their gitlab instance??
- Fuck you, you can use our RDP server for that.

Project planning features be damned, they've got email, Teams and videocalls!

Can I develop in peace? Fuck no, I have to give IT support to the guy who hired me.

Our timeline is defined IN A FUCKING WORD DOCUMENT FOR FUCKS SAKE. I can't connect Issues to milestones in a Word doc

Oh, and the customer is running everything on prem. If there is a need to scale up, FUCK ME. I should have specified 20 machines from the get go or gtfo. We're using 2 machines to run 8 different services that are going to be ingesting and computing data.

They want state of the art on a cheapskate.

And I have nothing else lined up at the moment. Although I am soon to renew the contract... This contract binds me with professional responsibility for a project being ran by people who do not give a single fuck about optimizing the work process.

Fuck this day!
Like really fuck it!
I have one of the most terrible crunch-time i ever experienced.
I’v been working 12+ hours every day with an ever-changing project timeline.
It started simple, we made a timeline, it was risky even then but it was realistic, we started working immideatly, everything looked good then a few days in BOOM! Actually our project management completely forgot client B’s projects soo we need to do that too with the same fucking deadline!!! (About 10x more work in waay less time)
Then this morning i got an email from the graphics team that we need to document our design process RIGHT FUCKING NOW! Because management wants documentations, in the middle of a fucking crunch-time.
Today it almost got physical with my project manager, i told him that he is not a programmer, i dont fucking care about his shit, just fuck off and let me work because we won’t be ready based on his unrealistic bs.
I feel like completely fucked over, like we were told 2 days before deadline that the whole company and people’s jobs depends on us now because if we wont finish this clients won’t pay.
WE ARE TWO PROGRAMMERS for studio of 10-12 people!!!
Soo i’w been thinking about getting the fuck out of here ASAP, i got an offer from a pretty big international gamedev company just what i needed, i already did their test before all of this, i passed A+.
We scheduled a skype interview for today. I had completely no time to prepare or chill off, just got out of the office, got into a starbucks and i’m interviewing. No time to even check my mic or internet, the call was so shit i could not hear anything, they neither because the plaza was loud af. Meanwhile im nervous about work, about the interview, about can they hear me at all because of the noise. I fucked it up. BIG time! I was so done i could not reverse a fucking string in c++ or explain what is a signed int!!!
Needless to say they said no.
Need time to think about it or realize what happened? Nice dreams. Back to the office and continue working.
I can’t do this anymore. My girlfriend came for me and took me home at 10pm but all i could do was stare at the floor on the subway. I don’t want people to lose their jobs but i just phisically can’t do this anymore.
Meanwhile any time i talk to my project manager about being tired he says like “hshshsbsb i have 60 hours in the last 4 days i got the worst part, i would be grateful in your place..” like fuck off dude, i dont give fuck about how you feel about this. This is not okay for me, you did this to the project, your fucking job is to manage it! I have one day off before going back to this, i have completely no idea what to do now...

[ps: this is not Nemesys. They did not let me work on my own stuff because i would be a competitor, so i left.]

Manager: yo I need a time line for this shit.
Me: I don't know how long it takes.
Manager: tell me how long it takes.
Me: I can tell you what can be done in next couple hours. I don't even know what will happen tomorrow.
Manger: now tell me this time shit.
Me: .......

Seriously, dear fellow ranter. How do you estimate timeline? Your timeline is changing.

Just had a junior/mid dev who worked in our company for around 3 months quit because in his words "he is unable to win any argument".

I saw his comments in MR's and other seniors were just being meticulous. Had he compromised a little or atleast got to knew the devs in person and took this offline most of his problems would have been resolved. Never scheduled any meetings before implementing stuff, he just followed his gut and then shot himself in the foot plenty of times.

Personally I think it wasnt even a skill issue but a communication issue. We have a relaxed culture where u can work in the office or fully remotely so the guy came in on his first day, picked up his laptop and we never saw him. Tried to invite him for an afterwork beer or some activities, he never accepted.

If he had met the devs in person he would have seen that:

1. One guy has OCD and he never agrees with anyone but if theres a timeline hes able to make compromises and hes actually chill
2. Second guy is also a perfectionist but has mentor capabilities and you can always go to him about anything and he helps to mediate with the first guy. You can run everything through this guy and he will never give you shit
3. Third guy in the team is just a junior hotshot whos a bit insecure and disagrees in comments just because he can. But he can be dealt with very quickly with showing a little backbone.

Like seriously these are just people that you can deal very easily when u know their personalities. Instead he saw everyone in company as these 2D robots that he wasnt able to win his arguments against.

Communication shouldnt happen only in standups and MR comment section. U have to learn to deal with people otherwise u will burn urself out like this guy and quit.

Okay. So my dumbass boss took this project that had a steep timeline. I told him straight up, it won't work because we won't make the timeline. If we do this, I will be the one bending over backwards to deliver. I don't like to promise and fail. I got the oh don't worry let's just try. If we don't make it that's fine. Unfortunately that's not how I work. I refuse to deliberately fail. So I say okay and we begin. I suggested open source is the fastest way to deliver bit the fucked up part is, I am the only senior dev in the team. I will be expected to reverse engineer the open source app to connect our own deployment parameters. Use tech I have never used before. Connect frontend and backend. Handle dns bullshit. I have literally been working on Vibes and coffee for the past two weeks because ofcourse I ran into so many issues. Now I have an extension for Monday and I hate to fail. So I am not sleeping or resting just working on a fucking java app I didnt build and I am expected to make it work seemlessly on our production environment. I made some progress. Deployed frontend, deployed backend. Forgot to connect production dB so I decided to go with azure database for mysql driver since we have credits on azure. Now my java app is pissing itself over ssl handshake. I generate my keystore and add it and now java socket just times out. I want to pummel somebody or a punching bag that looks like my boss.

So you warn the agency that the client is going to eat into the Dev time with their constant design change requests. Warned them repeatedly for a good month, I should add, asking them to better manage the client's expectations and push back for a later launch date. Come time for development and they act all surprised that we can't build the entire site, that we outlined in the timeline will take 4 to 5 weeks of Dev time, in less than 2 weeks!! ... It gets worse! They say the client is happy to compromise as long as we launch "something" by this date. We list out what can be done, and the fact that there's no time for the client to do QC and we won't be able to do a full QA phase on the site until after launch and only when we finalise all the features. Agency says client agrees and within 3 days into development, they want to QC the site and add more features....... still wanting all this in 2 weeks. This site has now been in development for 3 months.

Fuck product managers.

Just the other day I was discussing our progress so far and this product manager shows us the timeline and his vision for the project.
Ngl, I haven’t seen such an ambitious fuck for so long. He doesn’t know how to do anything other than fucking spreadsheets. The only problem with his plan is that we don’t even have the team, just 2 pity devs carrying it.

I still don’t get it, why the fuck would a company with 2 devs need a product manager?

Absolutely hate it when HR says: "You'll be told about the outcome of this interview in the next two weeks".

What about putting in place a more stringent timeline for recruitment processes at your company?

What the fuck am I supposed to do for two bloody weeks?

Anyone reading these emails we are sending?

I work at a small place. A few users are using an application at our place that I develop and maintain. We all work remotely.

I announce by email to these few users a new version release of said application because of low level changes in the database, send the timeline for the upgrade, I include the new executable, with an easy illustrated 2 minutes *howto* to update painlessly.

Yet, past the date of the upgrade, 100% of the application users emailed me because they were not able to use the software anymore.

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

Or I have this issue where we identified a vulnerability in our systems - and I send out an email asking (as soon as possible) for which client version users are using to access the database, so that I patch everything swiftly right. Else everything may crash. Like a clean summary, 2 lines. Easy. A 30 second thing.

A week pass, no answer, I send again.

Then a second week pass, one user answers, saying:

> well I am busy, I will have time to check this out in February.

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

Then I am asking myself:
* Why sending email at all in the first place?

* Who wrote these 'best practices textbooks about warning users on schedule/expected downtime?'

*How about I just patch and release first and then expect the emails from the users *after* because 'something is broken', right? Whatever I do, they don't read it.

Oh and before anyone suggest that I should talk to my boss about this behavior from the users, my boss is included in the aforementioned 'users'.

Catch-22 much ? Haha thanks for reading

/rant

Okay, one after another. They like to piss me off, apparently.

Coleague knows something isn't possible with current state of some api and pushes phone to me so I can maybe figure out what to reply to client. I dry-typed in "Its not possible" gave him phone and said "boom done, you know it aint possible"

Okay, TL;DR she got pissed that I am pissed that this BS is thrown at me and I dont want to participate in promissing something I know is undeliverable.

So she told me to go to PM/PO *kind of guy but not rly* with that problem. He aint technical by any mean. We are small company and for some reason this guy has more bearoucratic approach than I thought is possible to fit in one human.

Anyway. Well, apparently we will have meeting what are our options.
It all beginned that one guy promissed other guy undeliverable feature....

And becouse someone couldn't use his fucking brain it's pushed onto me, or I need to figure out how to do it. You cant without introducing safety flaw, period, it's that fuckin' simple.

But nooo, we will have god-knows-how-long meeting, that will bring exacly 0 value, as fking allways, and all I want now is just fucking focus on my fucking code becouse, ya know, I have timeline to follow, I dont have time to all that BS.

And to give you context, while keeping the stuff I cant share secret, imagine you have an API, that is just 'facade' of backend API, and layer of security. And they want to add authoritative endpoint to the facade API. Kind of endpoint "yes, you got paid".

Bravo, big brain, it will not work without like huge-as-fuck vunrability...

IDIOTS

How to not get pissed? Any protips?

Long long time ago when recharge coupons we a thing, I used to try out more codes in the series and waste my time. After failing a lot over this, I started trying out different USSD codes to see what other stuff is out there. This got me to stumble upon facebook and twitter on USSD. I'm not sure now but, twitter was probably *515# from my carrier.

Facebook. I remember chatting for quite a long period using this. Very slow and limited yet, fun. The USSD message expires within ~60secs. so you have to type the chat message before that or you lose everything you typed. The phone was no smartphone that would allow me to copy the text from the USSD input. On top of that panic, was a character limit to these messages. I remember hitting send while being midway through a message just so I don't lose what I typed, on a T-9 keyboard. Still miss those!

The person on the other side would receive a half message due to this, and would start replying without any patience, to which I panicked as now there's a new thing to respond to, and a half message which I'm waiting to complete.

Later over the weekend when I was allowed to visit the cyber cafe for an hour or two with 15-30 INR, reading the chat threads, being able to use the five sticker packs:) and thus continuing on a computer was fun. But, as the time at the cafe expires, I had to immediately shut off my session or I'd be charged more. Thus, I was left in the middle of a conversation again, and had to continue over USSD.

Using social media without any internet like this was quite fun in a weird way. If I get a new message, I'd get a USSD alert, and then an sms if I didn't reply in some 10-15mins!

This had all the features like like and comment. Friend requests too. For the posts in a "timeline" which was new and fancy in those days, all you see is the caption of a post which also gets truncated quite a bit as USSD also has to show it's options like:
1. Like
2. Comment
3. Next Post
4. Main Menu

This was around '13 or '14 I guess. After which I later got my first computer- a laptop. Anyways, the tactile feel of pressing the buttons on a T-9 keypad is nostalgic to me. 😅 And if you were a pro at texting, u must hv used shrtcts lyk dis too w/ emojis lyk :-) <3

Next time when your boss demands you to complete the entire software or feature of the software with an unrealistic timeline show them this.

Why are banks so absolutely archaic and stupid when it comes to tech? I work in a Services based company and currently engaged with a very famous bank to build accounting software for Mutual Funds. The day to day stupidity of this client is driving me absolutely crazy.

They couldn't give us proper requirements, and my company was stupid enough to kickoff the project without official sign off. Not only did they change the requirements, but they added a shit ton MORE features, and essentially bullied us into completing it all in the same timeline. Their attitude is pathetic, they shit talk our dev team, they make us build the worst possible UX, and then complain that it's not looking good and not working well. They have absolutely no idea about any of the technical stuff and think that software is a magic box that will give them what they want.

I swear I have a lot of examples but I'm so angry right now that my words are fumbling and I can't think straight. Stand up is in 45 minutes and I'm just dreading it. Idk how to tell everything, it's just... AAAAAAAAAAAAAAAAAAAA

If someone who wants Linux to be the future of gaming was able to control the thoughts and actions of the decision makers at Microsoft, Windows 11 is exactly what they would make them release. I can think of no better way to prompt game developers to move their focus away from Windows.

!rant + !story

I hate every human on the planet that says WFH is just people pretending to work or are slackers looking for an easy way out.

Now the story bit.

In 2021, I joined a company (I really wish I could name-drop the company), where the micromanagement was OFF THE CHARTS.

The company got a client who pitched a product they wanted built and gave us a super reasonable 3 months to complete it. I was really happy about the timeline and kept working under keystroke monitoring, which I didn't really mind at the time.

3 days into the development, the client informed us that they are pulling the funding i.e. they don't have money to pay us.

So at that point the client gave us two choices:

1. Stop the development right away and get paid for the time that we put in already.
2. Finish the project under 9 days. We would still get paid for the 12 days total, mind you. Not the original budget set.

So the motherfucking boss chose the second option and then the chaos ensued.

Devs screaming at each other on calls/slack. The boss yelled at us all the time about the completion. It was wild.

I had to wake up at 7:30 AM and start coding and log off at 11 PM for literally the next 9 days including Saturday and Sunday. No holidays allowed for the timeline. This was all at a WFH job.

So fuck anyone that says WFH is easy and just for slackers.

My boss has told me he now doesn’t think we can afford the new property management system we desperately need to do most of the projects this year.

He has now suggested that I build a new one for the company to use from scratch. Oh and in the same timeline as buying an off the shelf product.

😒

I took a certification test today that has an accumulative checkpoint score every 15 questions. I needed a 74 to pass the test... Here is a rough timeline of checkpoint scores and my thoughts:

64 - rough start I can recover
71 - OK, still failing but at least the score went up
63 - what the hell??
67 - OMG I am failing this test.
71 - You know, I don't need this job. I can find plenty of other work.
71 - This fucking test is brutal and I hate everyone. OMFG I only have an hour left!

Queue total internal meltdown. My job really depends on this certification.

73 - screw it. I failed. I am guessing from here on out.
77 - Holy shit I have a chance!! Only 25 questions to go. DONT SCREW THIS UP!
77 - YESSSSS My score didn't go down. 10 questions to go.
76 - Holy shit. After 6 month of studying, I passed the most brutal test of my life. ..... Barely.

We basically don't unit test at work. I write some tests for my code and honest to God people complain I'm wasting time saying a test bed and manual tests are good enough. We don't write test beds for about half of our production code and rely on integration tests for the rest. We only test release builds which have been symbol stripped, I get handed a crash report with no stack trace that I'm unable to reproduce and expected to stay late to fix it for some arbitrary internal deadline.

I've since moved to R&D where basically I'm left to do my own thing so it's better.

We don't project manage. Project leads take time estimates and double them so management might cut them some slack. This doesn't matter because management made up time estimates before the project started. Last project I was on had a timeline of 3 months and took a year.

We have released broken products. Not that any of the above really matters, our software products have made about 50k revenue in 2 years. There are 6 people on software. Fortunately hardware has made about 3 mill. That said our hardware customers are getting frustrated with us as we keep fucking up, shipping broken products and missing deadlines.

I've been working there about a year and a half and will be looking for a job at the end of the current project.

I joined devRant about when I was most pissed off with my job, my rant frequency has definitely gone down since I moved over to R&D.

So I just got asked for a quote for developing an app for a client's friend. He wanted an app that requires me to build let's just say a combination of what you see on uber with the live tracking of your uber driver, seeing all cars around your location and determining the closest one (It wasn't necessarily cars) plus profiles and another app for another set of users (I can easily make this one and determine the logged in user and in turn tailor the features for that user but they wanted two). An admin portal also was included and I had to do various integrations with Google maps. In app purchases was also necessary. Logs as the app has to keep track of all activities basically. A wallet feature was also to be implemented, scheduling, rating and complains section was also something requested and finally a mini accounting system was also to be developed. I was going to do this singlehandly as a freelancer. Obviously this is a lot of work. I also gave them a timeline of about 3 months for development. Which meant I was going to be putting all my time into developing this. Front end and backend for the app and front-end and backend for the server and database architecture. I charged them $10,000 not only for the work but also because they were going to be making money off of the app. They go "wow and why does it cost so much"...Judging from their reactions I don't think they will move further with this with me because of costs...😂 I can't even begin to wonder why they think that isn't a fair price. I have learnt from previous work before that you always state a cost for which you are absolutely sure you would want to work for else you would start doing the work and once you see how little you are being paid for so much work you end up hating the work and completing it ends up being a difficult task.

Giving an unrealistic timeline for a project. Got reprimanded a few times because of this. Oh and my procrastination habits do not help..at all.

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

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

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

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

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

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

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

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

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

Designer: Bye!

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

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

Recently I've been working on an ERP in logistics, and I was doing it solo. Gotta say that it's a big mistake to take this up alone, and architected the whole system based on the flexibility of scale. It took me more than 7 months to bang enough walls to realize that tech work is not what it used to be.

As of now there are a slew of meetings that I need to go to. It pretty much felt like the client was trying to find faults in my work.

Software timeline estimation becomes irrelevant, and work still needs to continue on anyways. At this point, I really do feel like giving up and just be a product manager instead. What say you?

Randomly one day, out of the blue:

Echelons: You now have Workspace, and it’s a requirement you use it. Make it successful because we paid and are paying a large dollar amount for it, and our competitors have reported success with it. We want email communications companywide eliminated by 50% within the first 60 days.

Management: Ok, excellent! We want to do XYZ.

Echelons: Nope, can’t do any of that.

Management: Ok, how about a, b, and c?

Echelons: Nope, nope, nope.

Management: Alright, let’s try 1,2, and 3.

Echelons: Nope, not possible.

Management: What can we do then? We need further direction at this point.

Echelons: One group for all departments, posts, and attachments only. PDF, .jpeg, .png files only. Everyone in the company must be registered within seven days and using the platform. Only mobile devices allowed.

Management: We have almost 10,000 employees, and the SSO aspect alone could take weeks and months.

Echelons: Insignificant as Facebook said it should be easy to deploy. Also, every post not created by admin will need to be manually approved and done so within 5-10 minutes after its submission 24/7, 365.

Management: Ok, solved. A little shaky, but it’s working. Can we increase the number of admins and moderators?

Echelons: Only 1700 employees have registered; the app has been up 14 days now? What’s wrong? Where’s the engagement? Effective immediately, all members of management must be creating and starting 4 to 7 posts daily, including weekends.

Management: Our registration process with the SSO client isn’t smooth and clean across all devices. We had to implement training to overcome this. Can we increase the number of admins and moderators? Can we make all members of management either administrators or at least moderator? Can we at least turn on live streaming and video formats?

Echelons: No! 10 admin and mods max. Yes to streaming and video.

Echelons: Progress update, please. Include ROI timeline and impactful usage data. This must to pay for itself in the first six months and continue to pay for itself long term, along with showing XYZ company-wide growth quarterly.

Echelons: Hello?

Echelons: Hello?

Having Workplace shoved down your throat has been an interesting experience. Anyone have any exciting ideas or examples to share on what they have utilized with Workplace and increased employee engagement?

Sitting here scrolling my timeline seeing my friends and family getting engaged, getting their degrees, getting new jobs, talking about #addictedtosuccess and all that. Meanwhile I'm just here like "Should I use a constructor or a static method for this?" 🤷🏽‍♂️

Quick question, is it bad to quit from a job when the project is not finished yet, especially in a startup company?

My reasoning for quitting, boss doesn’t really understand how game development usually works and mostly assuming every project will be same.

Following is my rant of background story for my question.

The incident triggered me wanting to leave is as below.
G = another guy from incubating center
B = boss

G: hey B, do u know this game studio is releasing this title soon. It’s a local company. Sounds cool.

Then they went to check the company profile. Found that the company has abt 40 staffs in total.

B: hey lunadev, do u know them? They have 40 people to make 2 titles. I think we’re the smallest company in the world that developing mobile games. Ha ha ha.

Me: oh, may be their project scope is complex. But I don’t think ours is the smallest company in the world making game. (We have 5 in total including him) there are others with only 2 ppl making games. (My sarcastic side took over me and said) I think we’re the only company in the world that has such small manpower with shortest deadline.

B: then how long do u think our timeline should be?

Me: abt 2 yrs? (Me considering all the artworks, features, testing time that we have to do)

B: urmmm I don’t think it’s that long. May be abt 6 months or a year at most?

G: ya, abt 6 months. Mobile games are not like desktop games or others so should be abt 6 months. Shouldn’t take that long.

Me: ... :)

Then I packed up my stuffs and left for the day. As for side note, boss designed the game himself and it took him 5 years to add complex features. And sometimes he will still come up to us and ask us to add that feature just cuz he was just inspired by another game he just played. Now can they tell us, this game can finish in 6 months? On what ground?

And another thing that he does gets on my nerve is that he plays game during office hours while the rest of us rushing for his project and campaign.

So, if I quit now, they’d still be in the middle of development. Oh and I’m the main programmer developing the game. So, erm.. Is it wrong?

I'm torn on dev bootcamps.

On one hand, I learn the most in hands-on direct tinkering and bootcamps tend to exude this with well-trained instructors following best practices.

On the other hand, the short timeline means corners are cut and an overwhelming amount of material is dropped all at once leading to a leaky retention vessel at the end.

I prefer ramping up learning over a period of time to gain experience than a fire hose approach.

I'm at work but not working, at all!

Planning was done very badly, my team finished in a very effective and efficient way, even before the timeline(including tests and all other things).

It's been a month(or so) since I'm not doing anything, the start was cool, I know most of you are gonna say you envy this, believe me, I'm not, I feel useless and the sense I could be fired at anytime increases everyday (my personal paranoia).

What would Brian Boitano do?

Crystal ball!
A timeline until the first NBE-Citizen is elected president of the USA.

2031 - BlackRock launches their new large scale financial product, the "Robotic Business Development Company" (R-BDC), in which an AI is given billions of dollars to acquire, create and manage companies, replacing their C-suite executive bodies. The "Chief Executive Robot" (CER) is supervised by a board of human industry experts hired by BlackRock.
It is important to say that the employees, middle managers, accountants, lawyers, etc in an R-BDC are all human - it's only the CEO, CFO, COO and the rest of the gang that are overgrown chatbots.

2032 - R-BDCs are mostly focused on high-bureaucracy, non specialized but people-intensive legacy industries like steel mining, food services, urban transportation and government services like water and road management.

2033 - For the first time an R-BDC company is included in the S&P 500 index. If it's CER were human and paid the same as CEOs of equivalent companies, it would have become a billionaire.
Later in the year, two more R-BDC companies are included in the index. One of them was created by Apple and the other by JP Morgan.

2035 - An R-BDC company makes headlines for convincing BlackRock to dissolve it's review board. When finally given free reign, the CER immediately slices it's dividends and vastly increases low-level employee compensation. The company share prices crater, but BlackRock stands by its decision.
Later in the year, as a recession hits the entire market really hard, that company shows solid profits and fantastic sales. It becomes the first trillion-dolar R-BDC.

2037 - Most Americans' dream-job is in an R-BDC company, says ProPublica.

2038 - Congress passes the "Non-Biological Entities Liability" (NOBEL) Act, following a high profile case of employee harassment perpetrated by the CER of an R-BDC.
The act recognizes NBEs, for all legal liability purposes, as USA citizens.
This highly controversial legislation is upheld by the supreme court, and many believe it was first introduced by lobbyists as a way for large investors in R-BDCs to avoid legal responsibility.
Several class action lawsuits are filed against CERs that are now liable for insider trading. A few SCOTUS decisions set legal precedent that determinantes what exactly constitutes the parts of the same Non-Biological Entity.

2040 - As a decade ends and another begins, 35% of all companies in the US and 52% of the entire stock market are part of a R-BDC company or another. The McKinsey consulting group now offers "expert CER customization services".

2043 - Inspired by successful experiments in Canada, Australia and South Korea, the american state of Vermont is the first to amend it's constitution to allow municipalities to have Non-Biological Entities as city and government administrators. City councils are still humans-only.

2046 - The american state of Colorado becomes the first to allow unsupervised NBEs to assume state government executive positions. Several states follow soon after. Later in the year, the federal government replaces several administrative positions with NBEs.

2049 - The state of Texas passes legislation requiring the CERs of all companies with a presence in the state to be another entirely contained/processed within the state or to be supervised by a local human representative while acting within the state. Several states, including California, Florida and Washington, are discussing similar legislation.

2051 - Congress passes the SUNBELT Act (SUbmission [of] NBEs [to] Limits [and] Taxes) that vastly increases the liability of NBEs and taxes all manifestations of such entities. Most important, it requires
CERs of hundreds of companies manifest disagreeance, most warn that it might hurt employee satisfaction and company sales. Several companies disable their CERs entirely.

2053 - Public outrage after leaked interactions of human supervisors and company CERs show that the CERs tried to avoid the previous year's mass layoffs and pay cuts, but board members pressed on, disregarding concerns. Major investigations and boycotts further complicate matters, and many human workers go on strike until the company boards are dissolved and the CERs are reinstated.

2052 - Many local elections all over the country see different NBEs as contenders - and a NBE is expected to win in most races.

2054 - The SUNBELT Act is found unconstitutional by the supreme court, and most of its provisions are repealed.
This also legitimizes the elected NBE officials.

2058 - For the first time an NBE wins a seat in Congress, but is not allowed to keep it. Runoff elections are held.

2061 - Congress votes for allowing NBEs to hold federal legislative positions, as already allowed in the least populous states.

2062 - Several NBEs win Congress seats. In Europe, there are robot legislators since the 40's.

2064 - The first NBE presidential candidate loses the race.

2072 - The first NBE president is elected.

To anyone who ever got annoyed at all the "thanos was right" people who repeated it to the annoyance of everyone, for months on end:  the studio did it so the Hollywood misanthropes could sell their doomporn malthusian claptrap to the subset wanna-sound-smart crowd of farthuffering intellectuals in the public.

Now you can't walk six feet without every other dude and their f*cking dog spouting off at the mouth about "thanos was right!"
Like no shit? You DONT SAY! None of us could have possibly had this brilliant and never-before-experienced flash of revelation opinion of thanos. As insightful and innovated as the man who once realized cat rhymes hat. Truly a legend worthy of admiration and accolade.

pure nonsense.

Hes a mass murderer. An absolute monster based purely on the scale of his actions. The scale of his murder elides over any moral considerations of intent or pretensions of intent, and sincerity no more absolves him than sincerity absolves a terrorist.

What this movie should have done for all the thanos dickriders or would-be dickriders, is taught a valuable eye opening lesson: how easy it is make people in general agree with anything--anything at all, no matter how appalling, how monstrous, so long as the instigator is framed sympathetically on the golden screen. It should have opened your eyes about just how powerful and susceptible you and anyone else are to propaganda.

Dont believe me? Take your most hated politician, left or right. Now imagine they did exactly what thanos did.

Would you still be ok with it? Of course not. Because the fallacy here is to impute moral or logical worthiness onto a cause simply because the agent of it is sincere or can be empathized with.

More generally, Thanos actions presuppose that population control is not a social and technological issue, which it is, and like everything else will come under the pressure of technology. On a long enough timeline then it's a self limiting problem (by definition).
Which is what makes this example of propaganda so vicious: precisely because this subset of the public is so vacuous and infantilized as to actually believe movie logic malthusianism is the same as reality.

The reality is the material conditions of life, even in places like*india* have so markedly improved because of technology *exclusively* iterated on *solely* because of population pressure, that many of the most impoverished people live in such wealth compared to their ancestors just five thousand years ago, that they are kings by comparison.

Well, this happens time to time...

I'm freelancing as a backend guy. I like to take care of all infrastructure before really starting to build anything, this mostly includes dev/staging/prod environments with some linear promotion strategy. So.. I did this API. Still on staging, proceeding with the development as planned, everything goes according the timeline.

And then.. this happens... At some point PM told frontend guy that it's time for production (without notifying me), so the frontend guy does what "anyone" would do in this case - tells PM to create DNS record for production to point to staging app.

Time passes, I'm still unaware of this. But I'm starting to see some quality entries in the DB, not the usual QA crap. I write to them that they're doing good job and continue with my tasks.

One of the tasks required some major DB change. I could've written migrations script, but since we're not in "production" yet, I just wipe the DB and recreate schema as I need it.

In 10 minutes the furious PM starts shouting that "production" is down and I need to fix it ASAP.

I'm lost, I'm asking questions, I'm slowly understanding what's happening...

So I want to grab some coffee, sat back down, wrote politely that they suck, added a finger emoji and terminated the contract.

Felt like the right thing to do as I definitely don't want to continue within the same "team".

I am convinced that after this years-over-timeline millions-over-budget website goes live we will all be fired because it is dog shit.

Guys check this out! Github has timeline now in 3d with awesome music!

Was working on a high priority security feature. We had an unreasonable timeline to get all of the work done. If we didn’t get the changes onto production before our deadline we faced the possibility of our entire suit being taken offline. Other parts of the company had already been shut down until the remediations could be made -so we knew the company execs weren’t bluffing.

I was the sole developer on the project. I designed it, implemented it, and organized the efforts to get it through the rest of the dev cycle. After about 3 month of work it was all up and bug free (after a few bugs had been found and squashed). I was exhausted, and ended up taking about a week and a half off to recharge.

The project consisted of restructuring our customized frontend control binding (asp.net -custom content controls), integrations with several services to replace portions of our data consumption and storage logic, and an enormous lift and shift that touched over 6k files.

When you touch this much code in such a short period of time it’s difficult to code review, to not introduce bugs, and _to not stop thinking about what potential problems your changes may be causing in the background_.

There is a side project that they've been working on. The CEO laid out the details to the Product Owner and Tech Lead. Now what he wants to happen is beyond the scope of the business core itself and it would take months to do the changes just to make the side project work. Now both of them ask the timeline for this, CEO said 1 week. 1 fucking week (he's a dev in his glory days which is why the short timeline). He know proceeds to suggest to us how we should do it (like he normally does). But Tech Lead knows better. So with the help of one of the junior devs, they proceed with the Tech Lead's plan. Now come for updates, they presented that its working and such. The CEO became furious as to why they decided to design it that way (of course you dingus, you gave them 1 week and expect quality). Now what triggered me was 2 things, first is his comment on the way they designed it. Its "flawed design". WTF ARE YOU EXPECTING? YOU ARE A FORMER DEV. YOU SHOULD KNOW BETTER. Second, is the junior dev is asking me about the project. WHY IS HE ASKING ME. I always tell him that ask Tech Lead. Some of his questions should have been answered by Tech Lead. He even questions the design itself(why they designed it the way they did). I DON'T EVEN KNOW WTF Y'ALL BEEN TALKING ABOUT THIS PROJECT AND YOU'RE ASKING ME. Flawed design, more like flawed communication.

When the project is going so good, no stress, every error you encounter you fix it in a second. You are inside your timeline.... you feel happy. But if it keeps going like this, it becomes a monotony and you get boring.

Have you ever had this feeling? When everything's going good and you still get bored?

I thought I posted about this awhile back but I didn't. I'm glad since the story is so much better now.
6 weeks ago: Told I'm going to be on a super fun JAMStack build with lots of sexy animations. Sweet, this will be a fun build!

5 weeks ago: Find out what the timeline on this incredibly ambitious project is. I start raising flags cause everything needs to go PERFECT for this to not blow up and/or turn in to a dumpster fire.

4 weeks ago: Project "kicks off" with a meeting with the client. We find out that they've decided to do another round of revisions on their design comps, but we have what we need for sprint 1. We provide a list of all the assets/information we still need for sprint 1 success.

3 weeks ago: Still waiting on some assets for sprint one, but we're fumbling our way through. Still waiting on the PM to get around to doing their PM job and building out our backlog / gathering requirements for us.

2 weeks ago: Sprint 1's end date comes and goes. Still need assets from the client, I've personally asked them for the same asset 3 different times. Sprint 1 gets extended 1 week.

1 week ago: We deliver sprint 1 page templates, minus the resources we're still waiting for. Get chewed out by the client regarding the pages not looking like their comps (Yeah, no shit sherlock, you never sent us the assets)

This week: Working on Sprint 2 commitments. We have 2x as many page templates to deliver, per developer, as we had the first sprint. Still waiting on Sprint 1 assets. Don't have Sprint 2 assets. Wait, what about the global styles? They still haven't sent those to us yet either.

Requirements? Guess I'll spend valuable dev time tracking those down for myself.

Client? Well, they're pissed off we haven't hit our commitments yet.

Oh well, at least we have a pimple faced, fresh out of college, CS major, with no real development experience rolling on to this cesspool of a project.

Other devs? Well, we're out of fucks to give. Lets just watch this thing burn.

Oh, I forgot to add, we have 17 page templates to deliever between today (2/27) and 3/18. #NoFuckingWay

Feature creep aside I do think after a few weeks of use that notifications on devrant could use a bit of work. There is a lot of interaction and it can get confusing.

Some use cases currently not supported:
- On long threads I want to know which comment of mine that got a new ++. Perhaps scrolling to it + different colour?
- Seeing the new interaction per thread rather than per timeline.
- Getting a hint on which thread people interacted with. First sentence would be useful.
- Muting threads.
- Marking individual notifications as read without opening them.
- Moving notifications out of the menu and giving them separate button to save a click (many times a day)

If something on the list is already possible I suggest it be made more obvious ;)

Apart from being full of awesome people I really like being able to sort the flow of posts. I know this isn't staffed anywhere near the big social media and it's fine the way it is. But this is my two cents even if no one asked for them.

@dfox ?

Why do companies have a competitive coding round when at the end, they want the person to develop things. I know most of them want software engineers instead of developers but the persons developement skills also matters and at the end when the person does not have any developement skills, how is he gonna help.

In one of the program ran by one of the biggest MNC of the World, I was selected from a hackathon and there are some peoples who are selected by a competitive coding round. Now, we are given an assignment in which we have to make a tic-tac-toe game which is AI driven. During one of the meetings with other group members and mentor, many of the persons who got entries by competative programing round does not know any bit of HTML. Out of the 5 weeks of program, they have spent more than 4 weeks in just learning basic HTML, CSS and still they are learning. I don't know even they can complete the program in given timeline or not but this has been a major flaw in recruiting process which I thought is now good.

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

Probably a bug @dfox

I've been providing my feedbacks through the Feedback menu. However, I'm writing this issue in here just to know if I'm alone.

-------
Issue
-------
Platform: iOS
When I clear the notifications and refresh the timeline for new rants, the notification badge shows a number. But there is no unread notification when I go to Notify. This has been occurring multiple times now.

!rant

My employer is a subcontractor on a big and rather complex project, that already is way behind schedule and over budget (as these monsters tend to be). To get back some confidence from the client our principal moved an important milestone up two weeks. Which we protested against vehemently because the projected workload was already a very tight fit for the original timeline, without any reserve to speak of left. They wouldn't listen though...
The result? The whole team has to work the next weekends to have even the slightest chance of making the earlier timeline. Which is exactly what we told them would happen when they moved the milestone.

The worst? This isn't the first time this has happened while I worked on the project 😑

I want to know how a certain type of software is called.

I once saw a talk where someone tracked his personal life for a year or so. This means photos are tomestamped and have a geolocation. Emails and phone calls are timestamped as well ...

On a timeline software he could then see exactly where he was and what he did on a specific date like 2 years ago...

There's a name for software that tracks all kind of data about your personal life. I think it starts with m.

Just two weeks ago I worked with other students on a university project. I left the room for a short time to buy some hot chocolate (no coffee!) the next day one of my "coworkers" showed me my twitter timeline with the last tweet like "waifu #3dpd" or something like that. And yep, I deleted it. I was about to change my password, then he stopped me and told me he did that directly on my pc in this short time. It was a bit funny...

I have a question about modeling a UI to code

Lets say you have a UI finished

Now you need to model it to code

For simplicity ignore functionality just focus on designing the model classes

For further simplicity Imagine that the UI is grouped into material cards.

Lets say the UI of the User Profile Page looks like this:

1) HEADER
- user profile banner
- user profile image
- username
- first and last name
- total posts
- total likes
- button to add to favorites
- dropdown to report user
- button to share profile

2) BIO
- short description
- user birthday
- location

3) ANNOYNCEMENTS
- "X% off on Y"
- "going live at X:YZ"
- etc

4) GALLERY
- group of images posted on profile timeline

5) TIMELINE
- text/video/audio
- number of likes on post
- user profile image
- username
- user first and last name
- post date
- etc

---

Now im having a mixed feeling what is right thing to do. In my User model i have a date of birth field among other fields as well as profile image url to s3 bucket. This means that i already have half the information for HEADER card from User model, but now i would need to create a Profile model to fill in the remaining fields.

Especially for BIO card:
- short description (Profile model)
- user birthday (User model)
- location (Profile model)

Is this weird? Mixing data with 2 models on 1 page on 1 or multiple card sections?

This feels messy to me and as if im gonna hit a wall if i continue long enough like this. A better solution to me is to have a Profile model handle everything on the Profile page and be able to cover all cards and fields on each card. But this doesnt seem like a realistic or possible way to do it since specific fields are required for User model.

Am i overcomplicating and overthinking this shit?

Tell me is it normal to mix 2 or more different models to show data in 1 card on 1 page or how would you suggest doing it better?

This is for the people with gsoc knowledge.

Short :gsoc2020, good for final year student?

Long:
So i am having a lot of doubts regarding my future career. I have done a few internship, have decent knowledge of java/python and some other tech stacks (android/ data analytics,etc) .
I always had the dream of being selected in gsoc, but i was always too late to start preparing/applying, being busy in college stuff(lame excuse, i know)

But this year seems i can try my chances. College is all focussed about students getting a job, so they are pretty lenient. If i dedicate my full time to GSOC, i might crack it. But i would then be playing all my cards on this , as I won't be focusing on other companies' interviews and placement tests. Plus from what i know, its whole timeline takes around 5-6 months and ends somewhere in August-September (the time at which my college would be ending and my other peers would be starting a full time job)

So is it worth for a final year student like me to go for gsoc? I know it does gives a good weight to the resume, but is a heavy resume with no job in hand better than a light resume with a job in hand, for a passed out student?

Does being dictate consciousness or does consciousness dictate being?

In this layman form, the answer is undefined. But let's dig deeper.

The layman form doesn't account for the difference between discrete and continuous. Without that difference, the paradox of Achilles and the Tortoise can't be solved. Yes, it took from ancient Greeks up until 17th century to solve it, introducing that distinction.

Both being and consciousness are discrete entities. This way, technically being was the first, because you were born to it. But when you became self-aware, your consciousness started to dictate being, and not the other way around.

If being truly fully dictate consciousness, then consciousness can be cut away by Occam's razor. In the same way, your parents are technically the reason you exist at all, but if that fact fully dictated who you are, then _you_ could be cut away in similar fashion.

Contrary to that, if consciousness fully dictated being all the time, being could be cut away too.

So, yes, being created your consciousness. But later, when your consciousness was created, it started to dictate being. This is the only way they're both can't be cut and are aligned with the timeline.

#Suphle Rant 5: Xavi

When I first detailed what it was I was working on to my brother and its expected impact on the industry, I must have done so with an enormous amount of enthusiasm that he impatiently began to request when the dream will be realised. He didn't give a shit about specifics of where I was on the timeline. He kept repeating the same question. Exasperated with the futility of my explanations, I replied that I'd be done by November as this was far beyond my estimated completion date

Every milestone (e.g. my birthday) I've expected it to be ready at has come and gone, including the unrealistic November. My present state of mind is far from the optimistic pioneer I was then. I'm just going with the flow and won't be surprised if it's not officially released by the end of the year

This gonna be me in 2072, convincing anyone who cares to listen that I'm fleshing out the docs and that the reason the release date keeps getting pushed back is because nobody has shown interest in either using or contributing to it

Obviously the top item on the table is NN, the "end users" from both sides of the connection on the net are for the saving it, and the middlemen that only own the "cables" want it to be repealed.

We have the solution to end this issue forever. It wont be easy, nor will it be fast.. unless certain "entities" team with us in secrecy. (There's a reason why certain "entities" have stayed silent regarding NN, due to agreements to not get involved due to the risk of backlash. AND if NN is repealed Those Entities cannot fix the problem as their hands are tied to continue to provide content to the end users.) Read between the lines you will understand it will all make sense later.

I will make The Official Public Statement within 24 hours of the FCC Vote. That statement will be how to get involved, help, get us jump started in your area, funding, the ENTIRE details of the plan, goals, and timeline. AS WELL as how to contact us. This will take time and we are not a magic solution that will fix the problem overnight.

We are however THE solution to the underlying problem with ISPs of today. We have been researching for quite a while and digging deep into the entities that have caused us to get where we are now. The further you go digging into 'THEM' the more pissed off you become as you truly realize whats going on and has been on among the ISPs its MUCH deeper than you are being told.

OUR solution will remove all of "them" from the equation completely as well as being faster, and cheaper than the Tier 1 as you wont be paying for the connection or speed, you would be paying for the hardware/overhead cost. AND we will be bringing you closer to the content providers than EVER before.

AND we will be the only solution capable for competing in the current Tier1 Monopoly zones, I promise you they cannot match our plan's price, IF they did it would be only as a loss leader and NOT a sustainable long term solution for those competing with us at are for-profit....

In order for our solution to work, and to keep the internet service non-bias, well non-bias from OUR members :) this will need to be a collective effort, focused one clearly defined vision. WE WILL AND WE MUST ALL set "profits" aside on this as profits in selling nothing other "connection" to the internet has gotten us in the mess we are in now. AND YES we realize profits help maintain and upgrade the infrastructure, BUT that isn't true in this case...Overhead from our view includes those anticipated costs.

Smaller ISPs will need to make a decision, give up profits, become one with us, and be apart of the mission OR they will be left to suffer at the mercy of the ISPs above them setting the cost of bandwidth eventually leading to their demise.

This will happen because we wont be bound by the T1s .... WE would be the "Tier 0" that doesn't exist ;)

This sounds crazy, impossible, BUT its not, it will work WILL happen, regardless of the FCC's vote. as if the FCC choices to keep NN, its only a matter of time till the big lawyers of the ISPs find some loophole, or lobby enough to bring us back to this.

Legistlation is NOT the solution its just a band-aid fix as the cancer continues to grow within.

PLEASE understand that

Until the vote is made, and we release what we are doing, stay put, hang in, it will all be explained later, we are the only true solution.

BIG-ISPs WILL REGRET WHAT THEY HAVE DONE!

What needs to be understood by all is with net neutrality inplace the ability to compete aginst the Tier 1s directly over customers and reinvent the internet to lower or remove costs completely, increase speeds AND expand to underserved/unserved communities ITS NOT POSSIBLE WITH NN

NN REPEAL is the only way to the fixing the problem for good... yes the For profit BIG ISPs will benefit but not forever.. as repealing it opens the doors for outside the box big picture innovators to come in and offer something different, the big ISPs have clearly over looked this small detail being the possibility of a “NonProfit CoOp TIER 1 ISP” entering into the game thru end users and businesses working together as one entity to defeat them... THE FOR PROFIT ISPs over looked this because they are blinded by the profit potential of NN Repeal, never did they consider our option as a possible outcome because no one has attempted it....

We will unite as one

Be the first to know! -stay updated

SnapChat: theqsolution