4:04

Sleep not found.

I started working at a software company two weeks ago. Today I learned that their web app only runs so smoothly because of a single JS function called specialSnowflakeHandler()

Google's first result for "a-successful-git-branching-model" should be a mandatory read before you can get your git credentials established.

Tomorrow Halloween is being celebrated in many nations as you might know. So we do in germany. Given that in Germany tomorrow is a national Holiday, the company skipped work today, with me being on call.
My On-Call time almost was over so I got ready to party (getting into my costume), not expecting any further calls.
I finished dressing up, still had some time, so I dug into coding a bit, as a costumer called. A customer from china. As I got told later on China does not celebrate Halloween in October and they do in another way.
So I set there, accepting the call, with my Camera set to autostart (Company policy).
Camera. On.
In. Costume.
As a monk.
With a bleach white face.
I was greeted by a man starring me "into the eyes". Took a good 1-3 secs til we bursted out in laugher. One of the funniest calls I had so far 😂 (and a short one, thanks China-Man)

Today my boss granted the intellij Ultimate license. It's a good day.
(even though eclipse isn't that bad I like intellij more)

So it's 2 weeks past launch day... And we are still not close to launching.

Sigh...

I feel old now....

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

If a new drug would be called VIM, noone would be able to quit

When people call something a bug, but it's just not finished yet.

Yes, Mr. Client. It is extremely wise of you to demand changes on release-day. Of course it won't go smoothly, untested and buggy as it will be.

Hmm....

Management proposed to work with external freelancers, to "pick up speed so we can release these new designs sooner". We agreed, but of course we (the home team) can't have time to review their work because we need to develop other new features and bugfixes and such...
Weeks later, turns out that their changes are largely incompatible with the work we have been doing on the main branch. We are now rebasing/rewriting huge chunks of their work, probably taking as much time as it would have cost us to develop the design ourselves in the first place.

An entirely typical exchange at work:

PM: How long would it take to build an application that collates Gubblefluffs and exports them as a PDF?

ME: Hard to say. What’s a Gubblefluff?

PM: Nothing complex. Its basically an object with some stuff in.

ME: Erm, okay. So I’ll define a Gubblefluff object plus methods to add edit and delete, then for each Gubblefluff have it write a line to a PDF.

PM: It will need to email that PDF to somebody.

ME: Okay, cool. “Gubblefluffs-by-email” should take about a day.

6 hours later…

ME: I’ve done Gubblefluffs-to-pdf, I’m not clear on what’s in a Gubblefluff but I’ve made it flexible so it can take almost anything.

PM: No, a Gubblefluff can ONLY be one of 4 Snigglefingers plus a timestamp and some JSON.

ME: What? Right. Okay. What’s a Snigglefinger?

PM: (sighs) A Snigglefinger is the collection of relevant Babelsets.

ME: Babelsets?

PM: Yeah, a user can have any number of Babelsets but they must correspond to one of the four types of Snigglefingers.

ME: There are users!?

PM: Of course!

ME: But I’ve not coded anything for users.

PM: Shit. I’ve told the client they can have it today. How long to add in users?

ME: And Babelsets, and Snigglefingers and the new Gubblefluff rules?

PM: Yeah.

6 days later…

ME: This is done now. It’s a beast but it works. Who should it email the PDFs to?

PM: Client X, plus cc to Y and bcc to Z.

ME: What? It doesn't support CC and BCC!

1 hour later…

ME: This is done. I’ve tested it and sent you a copy of the PDF it generates.

PM: Okay thanks. Is the cron running daily?

ME: What cron?

…

ME: Okay, so the cron’s running once a day at 8pm.

PM: Oh, it’ll need to be at 3:15pm. That’s when we’ve told the client they’ll get it.

ME: Right. I’ll change it...

PM: Also, the PDF you sent me looks nothing like the visual.

ME: What visual?
...