Bit of an essay. TLDR: come Monday I'm either getting fired or promoted. And the CTO is a dickhead. If you think you work with me or know who I am, no you don't, shut the hell up.

Was having a discussion with my team, went on for a bit, at one point my manager mentioned that the CTO wanted me to go into the office occasionally, same thing I've had since I joined when they literally wanted me to move hundreds of miles to be close to the office mid covid when the office was closed. I give a nondescript answer. He's a bit more persistent, I snap a little but the conversation moves on. Discussion of company and team dynamics, at one point he makes a comment about people at another company being told if they don't go into the office they won't be eligible for promotion.

I ask everyone else on the call to leave.

I point out that 2 years ago me and him were interviewing candidates. He on a few occasions introduces me to candidates as a _senior_ engineer. My job title does not contain the word senior. I let it slide the first time, not worth it for a slip of the toung. Happens a couple more times, I take him aside and privately point out my job title does not contain the word senior. He says he didn't realise and thought I was.

My take away then: I'm expected to do the work of a senior without being paid for it and without being given the acknowledgement of the appropriate job title. I remind him of this. My job title hasn't changed. Fuck, I took a low ball offer when I joined and have had a minimal pay rise in like, 3 years. My tone is "not happy".

His response? He discussed promoting me with CTO however budged constraints. I somewhat understand, however.

We have promoted several people in the last few years. We have grown by hiring new people in the last few years (5 in a company of 30). There are ways to compensate someone in ways that do not impact day to day budget (shares, TC, total compensation, is normal terminology in the tech field for this). I ask why the hell should I travel a few hundred miles to the office to get get to know people, put effort in to a company that demonstrably doesn't value me? Particularly as all levels of management have completely failed at developing a social atmosphere during covid? My first month, I had 3 5 minute meetings with my manager a week. That was all of the communication I had with people. I literally complained and laid out what they should do instead, they adopted most of it.

I also ask him if he genuinely thinks being here is in my professional interest? My tone has well passed pissed off.

I will say, I actually quite like my manager, we have a good working relationship and I've learned a lot from him.

He makes some mediocre points, tries to give advice about value of shares. To me, the value of shares is zero until they are money. The value to the company, however, is that it's a sizeable chunk on their balance sheet and shares sheet that they have to be willing to justify. If I wanted money, I'd go work at a high frequency trading bank and make 5x what I'm on now. No joke, that's what they pay, I could get a job, came close in the past but went to amazon. He understands.

He says will discuss with CTO. They were on a call for like an hour. His tone has changed to "you will be promoted ASAP, comp may be structured as discussed". Point made.

I'm in this job because it's convenient, is easy for me. Was originally lower challenge than previous, has a range of chances to learn and _that's_ the value to me. He's suitably nervous.

Point made I think.

So given I swore a few times, at least once about the CTO. Interesting to see how it goes.

Message from him to the effect that he spoke to CTO, has been told to write a proposal for promotion (kinda standard), will discuss with HR on Monday as they're on holiday.

So, maybe not getting fired today?

Blood pressure still very high.

A mac challenges a pc to an arm wrestle…

This isn't serious. I struggled with the order. The main point was that the smart ones left the industry. I thought about making JS Devs be lowest tier. Please contribute your own version if you can think of a better ordering.

We love each other so much.

One Microsoft way

Commented the code

save him ...

why does my project doesn't work on production...?

Or, why there are no web developer billionaires

!rant

After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:

1) Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.

2) Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)

3) Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.

4) Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get good corrections sent back. (remember the ego thing from tip #1?) Even if they have no critiques for me, sometimes they will see a technique I used and learn from that. Peer reviews are win-win-win.

5) When in doubt, do NOT BS your way out. Refer to someone who knows, or offer to get back to them. Often times, persons other than engineers will take what you said as gospel. If that later turns out to be wrong, a bunch of people will have to get involved to clean up the expectations.

6) Slow down in order to speed up. Always start a task by thinking about the very high level use cases, then slowly work through your logic to achieve that. Rushing to complete, even for senior engineers, usually means less-than-ideal code that somebody will have to maintain.

7) Write documentation, always! Even if your company doesn't take documentation seriously, other engineers will remember how well documented your code is, and they will appreciate you for it/think of you next time that sweet job opens up.

8) Good code is important, but good impressions are better. I have code that is the most embarrassing crap ever still in production to this day. People don't think of me as "that shitty developer who wrote that ugly ass code that one time a decade ago," They think of me as "that developer who was fun to work with and busted his ass." Because of that, I've never been unemployed for more than a day. It's critical to have a good network and good references.

9) Don't shy away from the unknown. It's easy to hope somebody else picks up that task that you don't understand, but you wont learn it if they do. The daunting, unknown tasks are the most rewarding to complete (and trust me, other devs will notice.)

10) Learning is up to you. I can't tell you the number of engineers I passed on hiring because their answer to what they know about PHP7 was: "Nothing. I haven't learned it yet because my current company is still using PHP5." This is YOUR craft. It's not up to your employer to keep you relevant in the job market, it's up to YOU. You don't always need to be a pro at the latest and greatest, but at least read the changelog. Stay abreast of current technology, security threats, etc...

These are just a few quick tips from my experience. Others may chime in with theirs, and some may dispute mine. I wish you all fruitful careers!

> Advice to new coders

Don't worry over picking language A or B.
Just pick A, use it for a month, then move on to B.
In a normal 3 year college degree you'll try multiple languages, some of which you'll never use again, and they'll each teach you something.

I had classes in Java, C, C++, C#, Prolog, Assembler, F#, JS.

Never used F# again and no one uses Prolog. But they were great for learning recursion and logic.

It's not like you take "a step down a bad path" if you pick a language you're never gonna use again.

You'll also learn new stuff on the job. We have one team that uses Go and one that uses Rust. None of the devs ever studied those languages. They were mostly former Java devs who leaned on the job.

Try to learn stuff instead of copying stuff together that may work but you don't know why or how. If you don't care about the why and how, look for another career/hobby.

You will have a first phase when you will do everything on your own.

Then you will have a second phase when you will totally rely on external libraries found on the internet.

Then you will have a phase when you will use libraries only for the stuff you don’t want to bother because, never reinvent the wheel but do not get too much tech debt.

Then the hyper simplification phase when you will refuse modern solutions for good old robust stuff as they used to do back then

Then I don’t know… but I am getting interested in agriculture

Anyway try always to learn new stuff and don’t be afraid of change as it is normal. And learn other skills not related to code, those will keep you alive

Compromise.

I think that sums up development pretty much.

Take for example coding patterns: Most of them *could* be applied on a global scale (all products)… But that doesn't mean you *should* apply them. :-)

Find a matching **compromise** that makes specific sense for the product you develop.

Small example: SOLID / DRY are good practices. But breaking these principles by for example introducing redundant code could be a very wise design decision - an example would be if you know full ahead that the redundancy is needed for further changes ahead. Going full DRY only to add the redundancy later is time spent better elsewhere.

The principle of compromise applies to other things, too.

Take for example architecture design.

Instead of trying to enforce your whole vision of a product, focus on key areas that you really think must be done.

Don't waste your breath on small stuff - cause then you probably lack the strength for focusing on the important things.

Compromise - choose what is *truly* important and make sure that gets integrated vs trying to "get your will done".

Small example: It doesn't really matter if a function is called myDingDong or myDingDongWithBells - one is longer, other shorter. Refactoring tools make renaming a function an easy task. What matters is what this function does and that it does this efficiently and precise. Instead of discussing the *name* of the function, focus on what the function *does*.

If you've read so far and think this example is dumb: Nope... I've seen PR reports where people struggled for hours with lil shit while the elephant in the room like an N+1 problem / database query or other fundamental things completely drowned in the small shit discussion noise.

We had code design, we had architecture... Same goes for people, debugging, and everything else.

Just because you don't like what weird person A does, doesn't mean it's shit.

Compromise. You don't have to like them. Just tolerate them. Listen. Then try to process their feedback unbiased. Simple as that. Don't make discussions personal - and don't isolate yourself by just working with specific persons. Cause living in such a bubble means you miss out a lot of knowledge and insight… or in short: You suck because of your own choices. :-)

Debugging... Again compromise: instead of wasting hours on debugging a problem, ASK for help. A simple: Has anyone done debugging this before or has some input for how to debug this problem efficiently?... Can sometimes work wonders. Don't start debugging without looking into alternative solutions like telemetry, metrics, known problems etc.
It could be a viable, better long term solution to add metrics to a product than to debug for hours ... Compromise. Find a fitting approach to analyze a problem instead of just starting a brute force approach.

....

Et cetera et cetera.

Advice for new coders - tell me and we’ll both know!!!

Thought hard for dem advice and dem advice is about softskills / collaboration:
- do dem ticket administration right
- prepare dem standups
- use dem dem where needed

Don’t be cynical and prideful. Respect people older than you in the profession, even if in your judgment they are “dinosaurs”. Even if they’re not as well-versed in what you consider “The New Shiny Thing”, they’ve seen some shit and can teach you a thing or two.

> Advice for new coders?

How much do you hate yourself?

.

(The code itself can be very rewarding)

Facebook Messenger's latest update wanted to do something with my Google Drive, and I got a prompt asking "Do you trust Facebook?"

Unfortunately, there was no option to say I trust Hitler with the Tsar Bomb more than I trust Facebook and Google talking to each other.

Life at work these days:

Manager: we’re not getting enough done
My calendar: 1/3 week filled with scheduled meetings

Manager: we need to use ChatGPT intensively. We'll go a lot faster.
Me using ChatGPT to get it to write an automation script: 2 hours wasted with no success
Me starting again from scratch to write the script: 15 minutes to achieve the desired result.

Thanks for your advice boss

The purpose of AWS free tier is to trick people into attempting to stay within its completely unmarked limits. It's like trying to hunt for mushrrooms in a forest split with a hostile country based on a verbal definition of where the border lies with border control waiting to ambush tourists for ransom money.

Birth.

"It depends..."

Death.

Do you ever encounter websites that are so horribly misdesigned that you just have to

*Now that's what I call a Hacker*

MOTHER OF ALL AUTOMATIONS

This seems a long post. but you will definitely +1 the post after reading this.

xxx: OK, so, our build engineer has left for another company. The dude was literally living inside the terminal. You know, that type of a guy who loves Vim, creates diagrams in Dot and writes wiki-posts in Markdown... If something - anything - requires more than 90 seconds of his time, he writes a script to automate that.

xxx: So we're sitting here, looking through his, uhm, "legacy"

xxx: You're gonna love this

xxx: smack-my-bitch-up.sh - sends a text message "late at work" to his wife (apparently). Automatically picks reasons from an array of strings, randomly. Runs inside a cron-job. The job fires if there are active SSH-sessions on the server after 9pm with his login.

xxx: kumar-asshole.sh - scans the inbox for emails from "Kumar" (a DBA at our clients). Looks for keywords like "help", "trouble", "sorry" etc. If keywords are found - the script SSHes into the clients server and rolls back the staging database to the latest backup. Then sends a reply "no worries mate, be careful next time".

xxx: hangover.sh - another cron-job that is set to specific dates. Sends automated emails like "not feeling well/gonna work from home" etc. Adds a random "reason" from another predefined array of strings. Fires if there are no interactive sessions on the server at 8:45am.

xxx: (and the oscar goes to) fuckingcoffee.sh - this one waits exactly 17 seconds (!), then opens an SSH session to our coffee-machine (we had no frikin idea the coffee machine is on the network, runs linux and has SSHD up and running) and sends some weird gibberish to it. Looks binary. Turns out this thing starts brewing a mid-sized half-caf latte and waits another 24 (!) seconds before pouring it into a cup. The timing is exactly how long it takes to walk to the machine from the dudes desk.

xxx: holy sh*t I'm keeping those

Credit: http://bit.ly/1jcTuTT

The bash scripts weren't bogus, you can find his scripts on the this github URL:
https://github.com/narkoz/...

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

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

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

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

Unpopular opinion.

TOML sucks

* it does not claim to care about indentation but it actually does
* nested datastructures are a nightmare, especially 'inline' for 'readability'
* oh fuck me everything must be "double quotes"
* booleans always lowercase, there is no "truthy" here.
* Tables are not intuitive at all.

And all this from working with it first time because I had the silly idea to modernize a python project to use pyproject.toml

Oh and don't get me started on pyproject.toml files. The documentation sucks!

There is a place in Saint-Petersburg, Russia. A very, very weird place. Its name roughly translates to “The Board of Wards of the Russian Ministry of Defense”.
It’s an ultra-modern, beautiful facility situated near two most important (and evil) buildings of the Putin’s epoch — Gazprom Arena (a.k.a. Death Star, left bottom on the map), and Lakhta Center (a.k.a. The Oil Bottle, the tallest skyscraper in Saint-Petersburg), completing the trifecta of evil architecture. Its official governmental website is vague. Its objectives are unclear. You can’t enter it — it’s surrounded by water.

Their official mission is, and I quote: “Gender-based approach in education and gender role socializing of young women.”

It houses roughly 800 girls. It has no English Wikipedia page. Its Russian page says there is nothing quite like it anywhere in the world. It only accepts young girls as its students. Allowed visits from parents are rare. Girls aren’t seen much during “the training”.
They tell this place changes people. Mobile phones are strictly forbidden. They train, eat and sleep on site. They’re not allowed to leave.
Its reviews written on Yandex Maps (the go-to app for maps in Russia) are, again, vague and oddly positive. Mothers tell this facility is the best place to be for a young girl — they teach them “right”. The only extensive negative review tells of a girl that was able to get out because of “medical reasons”, and tells about how the on-site doctor wasn’t really allowed to do such a thing.
The facility is very secretive. Photos of girls published by them are eerie and highly curated. No one truly knows what happens there.

They are wrong, however. There _were_ places quite like it — they were called “Reich Bride Schools”, and they operated in Nazi Germany (https://en.wikipedia.org/wiki/...).

Welcome to the Putin’s harem.

if people are curious of the PTSD baggage i'm carrying and why i rage so much at everything, see attached picture

granted, this was partly my fault, as i said, i was far too nice, and stayed for far too long

also note this job was AFTER a 2+ previous e-commerce job with ultimately failed project and little pay

UG i mean LOOK at this... i could go on and on for hours "push notifications must run" - yeah a casual bullet point that needs to be finished by end of day? hahahaha

hilarious to me that people will resent a language or framework for a handful of quirks or "unique" patterns

yeah, give me a language or framework that doesn't

🤡🤡🤡🤡🤡🤡🤡

what an absolute condescending garbage post...

"brilliant coder who can't meet a deadline"? well, you're the idiot right there, you just admitted it - they are brilliant and you don't know how to set deadlines

imagine labeling someone who can't meet a workload DIFFICULT! god this is making me fucking fume

"normal management" - yeah this is normal management alright, treating everyone like they don't know what they are doing and expecting them to follow you blindly, sounds pretty normal to me

it's shit like this that leads to cocky ass young dumb managers who actually don't know shit about building a product themselves, but then turn around and think they instead have the ability to manage a team to do it... incredible