The board of death:

I need 10++ to build my avatar . Thank you so muchhh

I like documentations like this xD
It goes with the library name “psyco”pg2.

8 months ago, me and my teammate developed an API and a web application for one of our client. The API was supposed to be consumed by mobile app which another team was working upon. Now my suggestion for the mobile team was to use something like ionic or react-native. This was purely to keep technical debt on lower side since hybrid apps don't deviate too far for both Android and iOS platforms. But mobile team went with the native apps and developed two separate apps which both have some differences.

The client didn't even use the iOS app since past 6 months. Now all of a sudden she reported several bugs and the person managing the mobile devs put that all on us. I tested some of the bugs and seems like the same feature is working on Android but not on iOS.
Came to know later that the iOS developer who was working on the app had resigned and left the company exactly 6 months ago. Right after the apps first launch. And since then mobile team hasn't put any replacement person for the project. That fucker was trying to buy some time by putting it all on us.
And now here I am, experimenting again with Flutter. So far it seems quite decent.

I didn’t. I went for an interview and quizzed this multi-million £ business about their architecture: it sounded awful.
I made some diagrams on how I would’ve done it, how it would scale etc and why. They were blown away and wanted me to implement this structure including the job they wanted to hire me for.
They sent a contract over: had the wrong name on it
They corrected the name but I noticed the salary was incorrect
They sent a third and by this time I was offered an interview elsewhere so I went

The hirer then called me to say he was frustrated I hadn’t signed a contract yet making it sound like it was my fault for not wanting to sign an illegitimate contract. he then went on to say that the salary had been reduced, I asked why and they said they felt I wasn’t a senior developer.
So I took the other job and they kept their shitty architecture 💁🏼‍♀️

My dev colleagues, the ceo, a external designer and me (dev) are sitting in the meeting room
and we discuss the result from the designer. He designed a complete relaunch of a
small CRM for the logistics sector.

The designer is a designer as you know him, big beart, small macbook, chai late
and he designed nothing, he hired a freelancer from romania.

My boss studied software development in the 80s but didn't really developed a software
for about 20 years, but he thinks he knows all and everything.

My boss is constantly complaining about the colors in the design and he would like
a iOS approach. Our system should complete copy the styles from iOS.

The really funny thing happend in just 1 minute. My boss is complaining again about the
colors and told the blue color is way to dark and the designer meant thats not possible the
blue color very bright. My boss sat next to the designer and looked not on the wall where
the picture was thrown from a projector, instead he looks from the side in the macbook screen
of the macbook which was in front of the designer. Then the designer says "Oh my god, the color
changes if I look from the side or from the top of the macbook." The Designer was blown away. My
boss couldn't believe it and did the same movements with his head and said. "Wow, you are right
the color changes".

We all other people couldn't believe that they are so dumb and thought this must be a joke. But
that wasn't a joke. After the meetin my boss told everyone in our company his results regarding the screen.

I wrote every story in a document, and I'm planning to create a book with dumb shit like this.

I'm on a call collecting requirements to a feature request that was developed last year, deployed last month, and nobody has a fucking clue about what's going on.

I'm also getting told that my requirements won't work, when they clearly will.

What's fucking crazy? In the time that I have wasted on this topic, I could have already written the fix.

I look in the docs at the function send(..., copy=True, ...).

I want to understand what copy is for and I read the description of the parameter: "copy (bool) – Should the message be sent in a copying or non-copying manner."

BuT whAt DoES thAt MEAn ?!

It is the year 2022.
We have multiple robots on Mars.
We have mRNA vaccines.

JIRA does not yet have a dark mode.

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

Manager: We need to setup the security in the Mexico server

Dev: You mean that 3rd party firewall add on?

Manager: Yes

Dev: And set up the billing on the Mexico account?

Manager: Yes

Dev: lol, sure thing I’ll create the ticket

Manager: What’s so funny?

Dev: Nothing

Ticket: Build wall and get Mexico to pay for it.

Hey here we go:)
My first comic series - “DevStory”

A story of two devs aiming at changing the world’s impact about cryptos by their own token project.

Bugs, cheap scammers, money, flying unicorns and a lot of laughs!
(Episode 1)

It's possible that you should take a basic HTML and CSS course before you start a company based on teaching resources related to progressive web apps...

Redux is weird, and I don't like it because it violates the most basic principles of responsibility. The concept of expressing state changes as reducers is nice because it can be duplicated, saved and restored and compared for equality. So is creating isolated accessors and selectors. However, I really don't think a reducer should be aware of its own position in the hierarchy. When specifying an action you aren't addressing a reducer, you're addressing the tree. That the tree doesn't manage this addressing and expects reducers to identify themselves is a bit strange, especially considering that the whole point of having a tree is that reducers shouldn't be affected by their position in that tree because they're pure. Same goes for selectors, they should belong to the tree, not to any particular sub-reducer. Separating the slices is reasonable structure, but if you specify parts of the addressing in the slice and parts of it in the root you might as well just use separate reducers for each of your slices. It's functionally equivalent.

I had an old rant somewhere about the most unproductive meeting I’ve had.

It was when I joined a new team. I was asked to hold a meeting to solve the issue of why nothing gets done on time and nobody showed up to the meeting on time including the manager.

PM: Heyy team x, could we have a suuper quick 90 sec tops call?

B*tch, if the call is actually 1.5m there is no way we need that call. We can actually respond to your question in text quicker.

But I know you. You can't fool me that it would actually be 90 seconds.

It's also fucking Friday afternoon.

fml

Upon finding out that Visual Studio (not Visual Studio Code) had stomped on the file association for .TOML, and spending a good couple of minutes trying to shut it down..

What is this format? Spaces are separated by + sign and columns are separated by & sign and it’s value is followed by = sign. Can I directly convert it to Spark dataframe?

I'd like to extend my heartfelt fuck-you to the following persons:

- The recruiter who told me that at my age I wouldn't find a job anymore: FUCK YOU, I'll send you my 55 birthday's cake candles, you can put all of them in your ass, with light on.

- The Project Manager that after 5 rounds of interviews and technical tests told me I didn't have enough experience for his project: be fucked in an Agile way by all member of your team, standing up, every morning for 15 minutes, and every 2 weeks by all stakeholders.

- The unemployment officer who advised me to take low level jobs, cut my expenses and salary expectations: you can cut your cock and suck it, so you'll stop telling bullshit to people

- The moron that gave me a monster technical assignment on Big Data, which I delivered, and didn't gave me any feedback: shove all your BIG DATA in your ass and open it to external integrations

- the architect who told me I should open my horizons, because I didn't like React: put a reactive mix in your ass and close it, so your shit will explode in your mouth

- the countless recruiter who used my cv to increase their db, offering fake jobs: print all your db on paper and stuff your ass with that, you'll see how big you will be

To all of them, really really fuck you.

A normal popular post on this platform has about 20 "++". How tf did y'all get to 10,000+ points? Just how often were y'all posting? Was there a great exodus from this platform before I joined that I don't know about?

I think it related to the app crashes, but now, instead of crashing, the app thinks it has no internet and loads forever things. Usually happens when I put the app in the background and don’t force close it.

Closing the app multiple times and switching to other apps fixes it, most of the time, not always.

But it still crashes. Less... but it still does, no specific patterns to see.

iPhone 6S

That's a unique skill

Had to share it

After a long work, I finally found the bug!!!

Dumbest arrow key design ever.

Rule 1: You are the best programmer.

Rule 2: Others are acting to be good programmers or are in a fixed match.

I'm so full of myself that's not an issue. Confidence is key.

Whisky 🥃 !

I ignore it.

I remind myself that nobody knows everything, and even the most knowledgeable people have their gaps in knowledge.
For whatever I'm not doing well right now, I'll keep an open mind, and be willing to accept advice and work on it.
In the end, just because I'm not doing something right once, doesn't extrapolate to the rest of my life. I still try to be the best version of myself.

Geez, I'll be getting out of this quarantine as a stoic mindful person