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.

What is the most ridiculous over-the-top "startup" thing you've been the victim of as a developer?

Alternatively, what kind of weird startup luxury would you absolutely love to have at your company?

For me, at various companies I've worked at/visited:

1. Hammocks & fatboy beanbags. Current employer has a "Netflix & Chill" corner with nice couches, and a small gym. I have encountered isolation/flotation tanks at the office of one of our partners... which is cool, but over the top in my opinion.

2. A fully automated aquaponics garden in the lunchroom. Was awesome, until some fish died and started to rot.

3. One hoverboard per employee, at previous employer. I splashed hot chocolate milk in an arc over three desks. A coworker broke his ankle while watching me spill chocolate milk.

4. Daily scrum standup meetings, on socks, in a big bouncy castle. Not kidding. Fucking ridiculous... (but secretly fun). That employer also had spiral slides between all floors, a tiny half-pipe with tiny skateboards, and someone who rode a unicycle way too much. It was a fucking circus. Stuck in the office of a Fintech company.

5. Soldering bench (at my current company), with drawers full of breadboards, servos and electronics components. Completely unrelated to my work, but it was my idea. It's just great to build a simple kits together with another random coworker while brainstorming platform features & refining specs... much better than meetings with bullshit slides.

6. Unlimited energy drink. Developed a serious caffeine habit (15-20 cans a day), and almost got a stomach ulcer. Not beneficial to employee health.

7. I really do love working from home + unlimited holidays. Just being able to honestly say "fuck you guys, I'm gonna get drunk and play games today", and at other times working until 4am and sleeping in the next day, or taking a week to work in a park in Rome... It makes work truly feel like my favorite hobby. Combined with a good sprints and curious/ambitious people, you can easily track productivity anyway.

Absolute asshat level clownly clownshipness:

Manager: Why is this like this? 🤡

fullStackClown: ...Because you defined the feature like this.

Manager: Hmmmmm ok... what about this? Why is this like this? 🤡

fullStackClown: ...Because you defined the feature like this.

Manager: Hmmmmm ok... and then this thing here? Why is this like this? 🤡

fullStackClown: Well, I hate to tell you, but it's a huge surprise. Guess what?! BECAUSE YOU DEFINED THE FEATURE LIKE THIS!!!

Manager: ... 🤡

fullStackClown: Any other absolute asinine questions to ask me to continue breaking me from flow?

Manager: ... 🤡

fullStackClown: ...

To those interested, I believe there is an evolution of my devRant career in order... I'm passing the clown phase... and entering the full-on circus phase...

Introducing my team's thought process, everyone!

#fullcirclefullcircus

BREAKING NEWS

A single full stack clown is far too forgiving for this world...

i'm now....

A FULL STACK CIRCUS!!!

🎟️🎪🤹‍♂️🎭🎡🤡

At 20 I thought my life would be an adventure. At 30 it seems like it's a rerun.

The reality is that life is full of grey areas, "good guys and bad guys" on all sides of most issues, and the story and excitement eventually end.

sometimes getting old feels like becoming comfortable with being numb and mediocre.

you are not the star at the center of your own story.

there is no story. there is only today, and then tomorrow, and then the day after that for as long as they happen to go on.

I can see no greater meaning or purpose behind this circus.

people think in months, seasons, years. maybe some of you even have five year plans.

but for me, rome was yesterday. and every rome to come. thats how near it is. It is so close, it and so many times before and after it, I cannot explain the sensation.

and in the vast gulfs of time, I see the wars, the conflicts, the narratives, and they unfold like dust or scum swirling on a pond, mechanistic, telling stories about nothing, algae struggling over territory on a rock.

as clearly as day, I see it all.

I saw your birth, and I saw your death. Your pain, and your greatest joy. How is it possible to love a total stranger and know them intimately because of their shared humanity? And still.

And from afar, in the stillness, I can't help being detached from the world and its problems.
And when we die, it is as if the world dies with us. Because it is not the end of the world, but the death of our own.

Softly go mortals, gently to their gods, like flowers in the fading summer. Never grasping that the permanence of the true identity and the temporality of the spirit are as fundementally distinct as the permanence of say "the G note", against the brief sound it makes when touched.

Eh. forget it. Sentimentality is a curse sometimes.

The joys of being a multi-project, multi-language developer! You think you'll juggle a couple of balls, but suddenly you're in a full-blown circus act, with chainsaws, flaming torches, and a monkey on your back yelling "more features!"

In the morning, you're all TypeScript: "Yes, of course, types make everything more reliable!" By lunch, you're neck-deep in Python and realize types are a vague suggestion at best, leaving you guessing like some bug-squashing mystic. And then just when you’ve finally wrapped your head around that context switch, FastAPI starts demanding things that make you wonder, "Why can’t we all just get along and be JavaScript?"

Oh, and don’t even get me started on syntax. One minute it’s req.body this and express.json() that. The next, Python’s just there with a smug look, saying, "Indentation is my thing, deal with it!" And don’t look now, because meanwhile, Stripe’s trying to barge in with a million webhooks, payment statuses, and event types like “connect” and “payment,” each a subtle bomb to blow up your error logs.

Of course, every language has its "elegant" way of handling errors—which, translated, means fifty shades of “Why isn’t this working?” in different flavors! But hey, at least the machines can’t see us crying through the screen.