//////

Say it. Just say it

caution: just some dude sharing a random story.

started my own small business around half a year now. a month earlier from that my cousin also started his career as a self employed dev with his own small business and we work together.

next year we we will start a company together, where we merge our existing small businesses into one. we are developing software on our own and we design and implement software for our customers.

seems like we are doing something right because we are reaching our capacities almost all of the time.

we plan to hire apprentices (hope it's the right word) and to teach them all we know to be able to then increase our possible workload.

you know, I do not have a degree or some form of education in the field of IT. And here in germany it was almost impossible to land a job as a dev. needed my cousin who studied cs to get me my first position in that field - and even with his reputation it was not easy.

this shit will not happen on my watch. If I see someone with fire for development I will give them a chance, irrespective of their background. And I will be more than happy to let that person grow and to give every kind of support I can.

we also plan to have something like "if the employee has a good idea for software that sells, we will support it and share revenue". got to figure out the details on that one, but I want to give the employee the possibility to grow some passive income out of their normal job - because for me this was never an option. and I think that this will motivate in some way 😅

just wanted to get this out of my head 😣

The nightmare continues.

Currently dealing with a code review from a “principal” dev (one step above senior), who is unironically called a “legendary dev” by some coworkers. It’s painfully obvious he didn’t read the code, and just started complaining and nitpicking.

It’s full of requests to do things that make absolutely no sense, and would make the code an unmaintainable mess.
• Ex: moving the logic and data collection from the module’s many callers into the module instead of just passing in the data.
• Ex: hiding api endpoint declarations by placing them in the module itself, and using magic instance variables to pass data to it. Basically: using global functions and variables instead of explicit declarations and calls.
• Ex: moving the logic to determine which api endpoint to use, for all callers, into the view.

More comments about methods being “too complex” (barely holds water) right next to comments saying “why are these separate? merge them together!”

Incredulously asking how many times I’m checking permissions and how ridiculous it all is. (The answer? Twice.)

Conflating my “permissions” param and method names with a supposedly forthcoming permissions system overhaul, and saying I shouldn’t use permissions because my code will all have to get rewritten. Even if that were true, and it’s likely not, the ticket still needs to use the current permissions. I can’t just ignore them because they might be rewritten someday.

Requests to revert some code cleanup because the reviewer thought the previous heavily-nested and uncommented versions (with code duplication) were easier to read. Unsurprisingly, he wrote them.

On the same ticket, my boss wants me to remove all styling and clientside validation, debouncing, and error messages from a form. Says “success” and “connection failed” messages are good enough. The form in question sends SMS and email using arbitrary user input for addresses. He also says it shouldn’t be denounced on the server, and doesn’t want me to bother checking permissions. Hello, spam!

Related: the legendary dev reviewer says he can’t think of a reason why we would want to disable the feature for consumers, so I should remove the consumer feature flag.

You can’t make this stuff up.

"Knock Knock"

"Who's there?" 

"Knock Knock"

"Who's there?" 

"Knock Knock"

"Who's there?" 

- DoS Attack

USB sounds like a backup in case the USA fails

Girl: we need to talk

Me: OK

Girl: you seem to have more time for your computer than me. I want to know how important I am to you.

Me: You are the number 1 in my life.

Girl: *smiles and hugs me*

Me: (thinking)...Just that I start counting from 0

Developer: We have a problem.
Manager: Remember, there are no such things as problems, only opportunities.
Developer: Well then, we have a DDoS opportunity.

My girlfriend dumped me after I named a class after her. She felt I treated her like an object.

Just my opinion, but Code reviews are a shit practice. In my previous company, we used to have one every Saturday. I presented my code and when everyone couldn't find anything to bitch/moan about, they said my code isn't "aesthetic" to look at. It's because I wrote this

if(condition)
do_thing;

instead of

if(condition) {
do_thing;
}

I cringe everytime I remember that incident.

How to get rich being a programmer?

"A different error message! Finally some progress!"

A young guy I work with burst into tears today, I had no idea what happened so I tried to comfort him and ask what was up.

It appears his main client had gone nuts with him because they wanted him to make an internet toolbar (think Ask.com) and he politely informed them toolbars doesn't really exist anymore and it wouldn't work on things like modern browsers or mobile devices.

Being given a polite but honest opinion was obviously something the client wasn't used to and knowing the guy was a young and fairly inexperienced, they started throwing very personal insults and asking him exactly what he knows about things (a lot more than them).

So being the big, bold, handsome senior developer I am, I immediately phoned the client back and told them to either come speak to me face-to-face and apologise to him in person or we'd terminate there contract with immediate effect. They're coming down tomorrow...

So part my rant, part a rant on behalf of a young developer who did nothing wrong and was treated like shit, I think we've all been there.

We'll see how this goes! Who the hell wants a toolbar anyway?!