!rant
Has anyone been paying attention to what Google's been up to? Seriously!

1) Fuchsia. An entire OS built from the ground up to replace Linux and run on thin microcontrollers that Linux would bog down — has GNU compilers & Dart support baked in.

2) Flutter. It's like React Native but with Dart and more components available. Super Alpha, but there's "Flutter Gallery" to see examples.

3) Escher. A GPU-renderer that coincidentally focuses on features that Material UI needs, used with Fuchsia. I can't find screenshots anywhere; unfortunately I tore down my Fuchsia box before trying this out. Be sure to tag me in a screenshot if you get this working!

4) Progressive Web Apps (aka Progress Web APKs). Chrome has an experimental feature to turn Web Apps into hybrid native apps. There's a whole set of documentation for converting and creating apps.

And enough about Google, Microsoft actually had a really cool announcement as well! (hush hush, it's really exciting for once, trust me)...
Qualcomm and Microsoft teamed up to run the full desktop version of Windows 10 on a Snapdragon 820. They go so far as to show off the latest version of x86 dekstop Photoshop with no modifications running with excellent performance. They've announced full support for the upcoming Snapdragon 835, which will be a beast compared to the 820! This is all done by virtualization and interop libraries/runtimes, similar to how Wine runs Windows apps on Linux (but much better compatibility and more runtime complete).

Lastly, (go easy guys, I know how much some of you love Apple) I keep hearing of Apple's top talent going to Tesla. I'm really looking forward to the Tesla Roof and Model 3. It's about time someone pushed for cheap lithium cells for the home (typical AGM just doesn't last) and made panels look attractive!

Tech is exciting, isn't it!?

> In office for first time in awhile
> Run into group of 4 people I don’t recognize in far cubicle corning laughing in hushed voices eating of an impressive spread of food
> See me and immediately look at each other with panicked expressions
> Confused, I put my hands up to indicate I come in peace
> They relax a little and say they thought I was from HR since they didn’t recognize me
> Ask why HR seeing them would be such a big deal
> They say their potluck is not “sanctioned”
> …?

So apparently HR just could resist ruining one of the only good things about coming into the office and one of the coolest things about the company’s culture. At least once a month there would be a giant potluck where everyone would bring some home cooked dish and share it. I can’t tell you how amazing these are in Canada, 50+ plates of authentic food from all over the world.

Unfortunately HR didn’t agree as 1. They didn’t cook so felt bad taking food. 2. Nobody asked them permission to put on these events they just happened organically. 3. Some people were bringing in food that they felt was culturally inappropriate (ie. caucasian guy bringing in homemade sushi).

HR recently banned all “unsanctioned” potlucks and all future potlucks needed to be approved through them with the following stipulations. 1. You could participate without bringing something by donating to HR $10 2. If you brought something you still had to give HR $10. 3. Things you brought in had to be approved by HR

Naturally the first and only potluck under these rules only 4 people brought something in as many couldn’t get their dishes approved because HR didn’t like what they were planning to bring (started out as being because culture and turned into HR just being picky), most just brought $10 so there wasn’t enough food to go around and so after HR took a giant group photo to post on the company’s social media accounts to show off how good the company’s culture is most everyone had to go out for lunch. HR sent out an email later that day exclaiming what a huge success for charity and the company brand the potluck was and they can’t wait for the next one. (I have the HR communications email marked as spam so I never saw the email). Nobody ever organized a sanctioned potluck after that.

However people still missed cooking and sharing their favourite recipes with one another so potlucks still occur but they are now very small, secret, invite-only, hush-hush affairs.

…What in the ever loving fuck

My friend, Gavin, an air steward (a job that he had done for decades), told me about an incident at work. He said that (shockingly to me) passengers occasionally die on a flight (particularly long-haul), just as a matter of course. This can be because people sometimes travel to visit loved ones BECAUSE they are dying, people sometimes find travelling itself stressful (so it can exacerbate an existing medical condition), or simply that, if you took a large number of people and shut them up in a space together for some considerable time, some of them would pop off through sheer statistical probability. Cabin crew are, apparently, fully trained to deal within this eventually in a calm, almost routine manner.

This particular flight, Gavin was working with another gay man: Peter, who was actually a VERY funny personality. Camp, extravagant and loud, Peter really lit up the place. But naturally, when the very elderly male passenger in seat 38b died peacefully in his sleep halfway across the Atlantic, Peter acted (like the entire crew), with decorum and dignity. As per the protocol, all the lights in the cabin were dimmed. A hush fell over the passengers (Gavin told me that, although no announcement is ever made, the other passengers nearly always instinctively know what's happened, with the news spreading via the media of hushed whispers and nudges). Then, as per standing instructions, two of the crew carefully lifted the deceased out of his seat and gently carried him to the crew station where he was laid down on a bed for the remainder of the flight.

After the late gentleman disappeared behind the discreetly drawn curtain, you could have heard a pin drop. There was a demure pause during which, slowly, the lights went back up.

Suddenly Peter's cheery face appeared, poking through the gap in the drapes. He looked around, blinking brightly with curiosity at the seated passengers, and said, in a voice that echoed around the whole cabin:

"SO! Anyone else have the fish?"

He narrowly avoided getting sacked.

A plain computer illiterate guy rings tech support to report that his computer is faulty.

Tech: What's the problem?

User: There is smoke coming out of the power supply.

Tech: (keeps quiet for the moment)

Tech: You'll need a new power supply.

User: No, I don't! I just need to change the startup files.

Tech: Sir, the power supply is faulty. You'll need to replace it.

User: No way! Someone told me that I just needed to change the startup and it will fix the problem! All I need is for you to tell me the command.

Tech support: 10 minutes later, the User is still adamant that he is right. The tech is frustrated and fed up.

Tech support: (hush hush)

Tech: Sorry, Sir. We don't normally tell our customers this, but there is an undocumented DOS command that will fix the problem.

User: I knew it!

Tech: Just add the line LOAD NOSMOKE <nosmoke> at the end of the CONFIG.SYS. Let me know how it goes.

10 minutes later.

User: It didn't work. The power supply is still smoking.

Tech: Well, what version of DOS are you using?

User: MS-DOS 6.22.

Tech: That's your problem there. That version of DOS didn't come with NOSMOKE. Contact Microsoft and ask them for a patch that will give you the file. Let me know how it goes.

1 hour later.

User: I need a new power supply.

Tech: How did you come to that conclusion?

Tech: (hush hush)

User: Well, I rang Microsoft and told him about what you said, and he started asking questions about the make of the power supply.

Tech: Then what did he say?

User: He told me that my power supply isn't compatible with NOSMOKE.

developer makes a "missed-a-semicolon"-kind of mistake that brings your non-production infrastructure down.

manager goes crazy. rallies the whole team into a meeting to find "whom to hold accountable for this stupid mistake" ( read : whom should I blame? ).

spend 1-hour to investigate the problem. send out another developer to fix the problem.

... continue digging ...
( with every step in the software development lifecycle handbook; the only step missing was to pull the handbook itself out )

finds that the developer followed the development process well ( no hoops jumped ).
the error was missed during the code review because the reviewer didn't actually "review" the code, but reported that they had "reviewed and merged" the code

get asked why we're all spending time trying to fix a problem that occurred in a non-production environment. apparently, now it is about figuring out the root cause so that it doesn't happen in production.

we're ALL now staring at the SAME pull request. now the manager is suddenly more mad because the developer used brackets to indicate the pseudo-path where the change occurred.
"WHY WOULD YOU WASTE 30-SECONDS PUTTING ALL THOSE BRACES? YOU'RE ALREADY ON A BRANCH!"

PS : the reason I didn't quote any of the manager's words until the end was because they were screaming all along, so, I'd have to type in ALL CAPS-case. I'm a CAPS-case-hater by-default ( except for the singular use of "I" ( eye; indicating myself ) )

WTF? I mean, walk your temper off first ( I don't mean literally, right now; for now, consider it a figure of speech. I wish I could ask you to do it literally; but no, I'm not that much of a sadist just yet ). Then come back and decide what you actually want to be pissed about. Then think more; about whether you want to kill everyone else's productivity by rallying the entire team ( OK, I'm exaggerating, it's a small team of 4 people; excluding the manager ) to look at an issue that happened in a non-production environment.
At the end of the week, you're still going to come back and say we're behind schedule because we didn't get any work done.
Well, here's 4 hours of our time consumed away by you.

This manager also has a habit of saying, "getting on X's case". Even if it is a discussion ( and not a debate ). What is that supposed to mean? Did X commit such a grave crime that they need to be condemned to hell?

I miss my old organization where there was a strict no-blame policy. Their strategy was, "OK, we have an issue, let's fix it and move on."
I've gotten involved ( not caused it ) in even bigger issues ( like an almost-data-breach ) and nobody ever pointed a finger at another person.
Even though we all knew who caused the issue. Some even went beyond and defended the person. Like, "Them. No, that's not possible. They won't do such dumb mistakes. They're very thorough with their work."
No one even talked about the person behind their back either ( at least I wasn't involved in any such conversation ). Even later, after the whole issue had settled down. I don't think people brought it up later either ( though it was kind of a hush-hush need-to-know event )

Now I realize the other unsaid-advantage of the no-blame policy. You don't lose 4 hours of your so-called "quarantine productivity". We're already short on productivity. Please don't add anymore. 🙏

Laziest thing ever done - Launched a website without a big feature I had to work on.

Neither my superiors nor the client have realised it yet. And by the time they do, it will be too late 😈

Management has bequeathed that it shall hit prod tomorrow, the developers cry 'but it's not ready`. Hush little dev for tomorrow we hit another payment milestone

Checking out a project on GitHub:

> Using advanced condition-based AI logic, Compactor can skip over files that have been previously found to be incompressible, making re-running Compactor on a previously compressed folder much quicker.
> (Yes, it's an if statement and a trivial hash database, hush)

So I'm on one project which was previously developed (I mean poorly developed) by another firm.

So this fucking guy who has done all the coding, I just fucking hate that guy because he has the shittiest logic and he doesn't know things should always be dynamic.

So he has written code(in PHP) where he has calculated the difference between DateTime and he is adding days, hours and minutes to another DateTime.

And it took me fucking 5hours to realize that he just forgot there is a thing called month which should be considered while doing this, I mean WHAT THE ACTUAL FUCK?

It was calculating like the difference between
2018-07-12 and 2018-09-18 are FUCKING 6 DAYS WTF!!!! SERIOUSLY? HOW COULD SOMEONE MISS THIS?WTF?!!!! FUCKING 5 HOURS FOR THIS?

Hush!! I think it is my bad that I thought it is DateTime issue and focused on that. I feel good now. Thanks.

I got my current job in the most standard manner,
1. Saw an ad for the job in the local newspaper.
2. Called the boss and had a chat with him. He sounded nice and the job sounded interesting.
3. Submitted my application and resumé
4. Boss called and we set up an appointment for an interview.
5. Met with boss and HR, had a cup of coffee and an interview.
6. Boss called and told me I'm one of two, and that he would like me to do a DISC personality analysis.
7. Met with HR and did the analysis, a bunch of questions that I answered as thoroughly as I could.
8. Boss called and said, congrats! Can you start next month? Yes, I could and it's been more than three years since :)

To make a boring story a bit more funny: Half-way through my first day, I noticed my zipper was open =:O And today I'm wearing two exactly identical socks...save for the colour, different shades of grey on left and right foot. Hush, don't tell my colleagues, maybe they won't notice ;) Well, I guess it's alright as long as I'm not wearing nothing but underwear, or being butt naked, like in some nightmares.