fuck batteries. I'm going wired everything.

Programming

My new Mac Mini (which I bought begrudgingly for one project only) comes with a warning about a coin battery and how swallowing it will cause harm. Are we, as a species, getting dumber by the minute, or is it only Mac users?

My experience two weeks into being married:

1. Any other couple can fuck off. We're the protagonists now.

2. My sleep schedule has done a complete 180. I start my day at 7 am now, previously it was 12 afternoon. I also sleep early at 10 pm now. I feel a lot better about this schedule tbh.

3. My wife has an office job, so I get my work done in peace and am able to wrap up my day early to make time for her when she gets home.

4. She's serious about investments, stock market, SIPs, Gold prices or whatever and actively puts money into those things. Good for me.

5. Going out with her is actually fun, because we plan our Sunday ahead of time. I used to scoff at other couples before, but now I get it. It may look cringy from the outside but not to me it doesn't.

https://aprogrammerlife.com/top-rat...

Who wants to play a game?
Let's play....
Is This Sexual Harassment!?!?

I won't publicly reveal who is the other person in this convo. I just want genuine opinions.

For reference, the convo started in another language, and quick mention of their fondness for my eyes... i simply ignored with 'lol' and chatted on and off for some hours... next time it was in english with use of " darling", which I simply stated wasnt something anyone who knew me would say.

they claimed it was just british... it's not. I actually use UK spellings due to working for years for UK based companies.

back in the other language... ' angel' , 'princess', *some equivalent of a small rabbit*,...me once again, more directly, asking why and saying no/they are irrelevant to me, to each.

the next part was hysterical, but to not out the person or skew opinions, that's being omitted.

the following came after me running out of time so it needed to be a call or i needed to mute them. they got muted.

SOOO,,,,

IS THIS SEXUAL HARASSMENT???

my dev friend/partner and I can't find the right term for wtf this is... which is odd as we both have an extensive vocabulary and are highly specific.

It took 8 months, but my code finally broke production!

cold, wet and depressing autumn mornings/days.

Aaahhh, it's that time of the year again when you appreciate how hot your laptop and its charger get.

My feet enjoy my charger :)))

Fuck react!

This Monday, I have become a father.

It's a boy and he is awesome, in perfect health. We, as a couple could not be happier about that.

His name is Cyrus, named after Cyrus the second , the great.

https://en.wikipedia.org/wiki/...

However, all our happiness is overshadowed by a major blow.
My love of my life, the mother of my child, has been diagnosed with breast cancer , right before the labor.

We are in a rollercoaster right now and are torn between happiness and despair. Hard to deal with.

This is one of those things I am unable to manage with my knowledge and expertise. I can't just "configure cancer away". There is no flag that I can set as "absent" or "false".

Today we're going to hear what the strategy will be to battle this monstrosity. We're bracing ourselves for the worst.

When you fire a project manager

I got a job

I'm genuinely curious: Is there anyone here who is offended by the use of the name 'master' for a Git repository 'main' branch? If we all moved to 'main' and never used 'master' again (for anything, Git or not) would that make a difference to you?

The longer you work in tech, the stronger the urge to quit and start farming

Sleeping while coding is two days of debugging for me...

🎉 As of today, I can proudly count myself among the members of the "Killed Prod on A Friday Afternoon" club. 🎉

So its 6+ years of writing code, learning new things and I still find coding amaizing and kinda enjoy it
Thot I would be sick of it and doing somthing else

Yeap sometimes happen to me...

!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!

Lads, I will be real with you: some of you show absolute contempt to the actual academic study of the field.

In a previous rant from another ranter it was thrown up and about the question for finding a binary search implementation.

Asking a senior in the field of software engineering and computer science such question should be a simple answer, specifically depending on the type of job application in question. Specially if you are applying as a SENIOR.

I am tired of this strange self-learner mentality that those that have a degree or a deep grasp of these fundamental concepts are somewhat beneath you because you learned to push out a website using the New Boston tutorials on youtube. FOR every field THAT MATTERS a license or degree is hold in high regards.
"Oh I didn't go to school, shit is for suckers, but I learned how to chop people up and kinda fix it from some tutorials on youtube" <---- try that for a medical position.

"Nah it's cool, I can fix your breaks, learned how to do it by reading blogs on the internet" <--- maintenance shop

"Sure can write the controller processing code for that boing plane! Just got done with a low level tutorial on some websites! what can go wrong!"

(The same goes for military devices which in the past have actually killed mfkers in the U.S)

Just recently a series of people were sent to jail because of a bug in software. Industries NEED to make sure a mfker has aaaall of the bells and whistles needed for running and creating software.

During my masters degree, it fucking FASCINATED me how many mfkers were absolutely completely NEW to the concept of testing code, some of them with years in the field.

And I know what you are thinking "fuck you, I am fucking awesome" <--- I AM SURE YOU BLOODY WELL ARE but we live in a planet with billions of people and millions of them have fallen through the cracks into software related positions as well as complete degrees, the degree at LEAST has a SPECTACULAR barrier of entry during that intro to Algos and DS that a lot of bitches fail.

NOTE: NOT knowing the ABSTRACTIONS over the tools that we use WILL eventually bite you in the ASS because you do not fucking KNOW how these are implemented internally.

Why do you think compiler designers, kernel designers and embedded developers make the BANK they made? Because they don't know memory efficient ways of deploying a product with minimal overhead without proper data structures and algorithmic thinking? NOT EVERYTHING IS SHITTY WEB DEVELOPMENT

SO, if a mfker talks shit about a so called SENIOR for not knowing that the first mamase mamasa bloody simple as shit algorithm THROWN at you in the first 10 pages of an algo and ds book, then y'all should be offended at the mkfer saying that he is a SENIOR, because these SENIORS are the same mfkers that try to at one point in time teach other people.
These SENIORS are the same mfkers that left me a FUCKING HORRIBLE AND USELESS MESS OF SPAGHETTI CODE

Specially to most PHP developers (my main area) y'all would have been well motherfucking served in learning how not to forLoop the fuck out of tables consisting of over 50k interconnected records, WHAT THE FUCK

"LeaRniNG tHiS iS noT neeDed!!" yes IT fucking IS

being able to code a binary search (in that example) from scratch lets me know fucking EXACTLY how well your thought process is when facing a hard challenge, knowing the basemotherfucking case of a LinkedList will damn well make you understand WHAT is going on with your abstractions as to not fucking violate memory constraints, this-shit-is-important.

So, will your royal majesties at least for the sake of completeness look into a couple of very well made youtube or book tutorials concerning the topic?

You can code an entire website, fine as shit, you will get tested by my ass in terms of security and best practices, run these questions now, and it very motherfucking well be as efficient as I think it should be(I HIRE, NOT YOU, or your fucking blog posts concerning how much MY degree was not needed, oh and btw, MY degree is what made sure I was able to make SUCH decissions)

This will make a loooooooot of mfkers salty, don't worry, I will still accept you as an interview candidate, but if you think you are good enough without a degree, or better than me (has happened, told that to my face by a candidate) then get fucking ready to receive a question concerning: BASIC FUCKING COMPUTER SCIENCE TOPICS

* gays away into the night

Company: we care about work/life balance (as long as shit gets done)

Company: we care about mental well-being (except when shit has to be done "now!")

Company: we help each other (we push work around until someone finally do it)

Company: management is here to help you do your work (as long as you don't ask them to help you to solve a real problem)

Company: we are agile (except we have more sub-processes than ever)

Company: we only hire best (and then put them in the team of morons)

Company: we are customer centric (that's why we are delivering bugged features)

Company: we constantly rise the bar (deliver more shit in shorter time)

... did I forget about something?

People who say "hi" on slack and then take 50 years to say what they actually want to say.

People who sit on the table beside yours to play games on their phones.

People who call you dad.

People.

It's 2021.

Bluetooth still sucks balls.

That's all.

Motherfucker if the project uses Eslint to enforce code standards, please don't start every fucking file with 20 lines of /*eslint-disable*/s

It's there to fucking help you and all the new devs who have to deal with your shitty code. I'm sorry that you're too fucking lazy to make a few small tweaks so that future developers don't have to deal with your sad braindead 1337speak JavaScript

Just use the fucking tool like everyone else, you don't have to fucking disable it so that your sad ego can continue to think you're the Bill Gates of JavaScript

There is a fine line between being a genius and psychopathy, and I’ve just snorted that line.

Fuck pair programming
Fuck mob programming
Fuck all that hipster shit!

Found out my wife is pregnant with twins. Had to give up my office for an alcove in the kitchen. Finished getting everything made/installed last week.

Stay safe

Back in the soul-eating depression abyss

I was today years old when I discovered the CSS property column-count.

Do you have any fucking idea how many times I’ve used CSS grid or flex box or BOTH when all I wanted was to make a layout with a set number of columns?

Why the fuck didn’t I know about this thing?

Did you know about this thing?

I've hit my quota for this month for social interaction. Unfortunately I have a very busy weekend coming up and already super anxious and stressed. I hate being an adult sometimes.