Here's my piece of advice for new devs out there:

1 - Pick one language to learn first and stick with it, untill you grasp some solid fundamentals. (Variables, functions, classes, namespaces, scope, at least)

2 - Pick an IDE, and stick with it for now. Don't worry about tools yet. Comment everything you're coding. The important thing is to comment why you wrote it, and not what it does. Research git and start using version control, even when coding by yourself alone.

3 - Practice, pratice and pratice. If you got stuck, try reading the language docs first and see if you can figure it out yourself. If all else fails, then go to google and stackoverflow. Avoid copying the solution, type it all and try to understand it.

4 - After you feel you need to go to the next level, research best practices first, and start to apply them to your code. Try to make it modular as it grows. Then learn about tools, preprocessors and frameworks.

5 - Always keep studying. Never give up. We all feel that we have no idea of what we are doing sometimes. That's normal. You will understand eventually. ALWAYS KEEP STUDYING.

Dear children let's talk about how to ask a f***ing question.

You don't just go "I need help. I can't figure it out." We had trainings on this, I sat through 3 hours holding your hand to help you try and understand things.

And yet now we have scheduled another 3 hours to help you figure this out because you said you were having difficulty with it because you couldn't figure it out. How about instead of just saying you "Need help", you start by
1. Explaining what you are trying to accomplish
2. What specific issue are you facing? Is there an error message or something?
3. What have you already tried thus far that didn't work?

Instead of "I NEED HELP I CAN'T FIGURE IT OUT!" that is the sign of a lazy f****ing engineer, someone who doesn't want to think, who doesn't want to learn something new who wants to just coast by. Especially when this is going to become an increasingly important part of your job.

And of course you currently are still a whole job level above me because sitting around and keeping a chair warm for 10 years means you are a valuable contributor, instead of what you can actually DO!

This bugs me so much. So remember kids, when you need help, or need to ask a question, ASK IT THE RIGHT F****ING WAY!

Manager: Messages not visible! bug ticket!!!!

Dev: oh fuck, there's an issue with our chat system, not good! _inspects ticket_ oh, it's just a display issue that actually is according to the previous spec, yawn...

Dev: please describe the bug better next time, I though we had a major outage, this is simply a small design issue...

Manager: ...

Dev: ...

I think I'm quitting soon guys. I literally do not get paid enough to deal with these incompetent idiots each day.

Meanwhile:

Management: forget your shitty salary, take one for the team, you get 3% of the shares in the company!!!!

Dev: what fucking shares, you haven't even converted to a corporation yet, THERE ARE NO SHARES

Management: ...

Dev: ...

Oh yeah and they called me at 6:30 PM today: "so i guess you are winding down for the day"

fuck outta here i haven't been working since 5 you fucks

jesus i swear some people need to screw their fucking head on straight, so far gone into the hUsTlE CuLtUrE they don't even know what reality is anymore

People/companies talking about ooh we want gender diversity we want more female software developers, IT professionals etc

You talk the talk, do you know how to walk the walk?? Do you know how to deal with female engineers?

I am a hardcore engineer worked and studied majorly with men for years. I lead, managed teams had my own company worked as a consultant for years.

Then I got into the IT industry as developer later. I was completely against the idea of being female would make any difference or you would be treated differently.

Finally I had my own enlightenment and stopped resisting that idea.

Some treatments made me think what are these guys doing? Don’t treat me like your sister. I am not your sister. Don’t see the femininity or looks. I am not a Merrilyn Monroe to say oooh you are great you know soo much. I am not paid for that act, I do my job! It’s same as yours mate.

Don’t underestimate me or try to preach me as if I am a cute little girl. Don’t show off and boost your ego next to other guys.

Now I regretfully I agree the ladies ranting about male dominance and getting different treatment in IT.

I am literally trying to avoid red nail polishes or red lipstick god forbid. Maybe I should put some fake beard and a belly, loose jeans with an energy drink in hand. Here comes the expert IT professional, already ticking a box.

Honestly you are not taken seriously most of the time. If you are a guy then they are all ears..And those guys talk about they want gender diversity blah blah

You feel like a ghost when you express your opinion. You are not taken into account even when you have a comment or suggestion.

Even humiliated by a guy giving me a speech about how to be a good developer next to a manager. Look buddy I am not a yesterday’s child. I am at your age. I haven’t come to this position by jumping around picking flowers in a field. If I was a man, would you dare saying those to me? There could be a street fight coming.

LinkedIn selfie takers with body show offs putting ooh I am an IT recruiter as a female I got into IT. You can do it too. (don’t get me wrong I respect that achievement that’s good) but those girls get thousands of likes and applauses, you are working in IT for years people say they are seeking for. Your technical post doesn’t even get 20 likes. Your encouraging comment on a guy’s post isn’t even acknowledged. You are not even taken into account. Am I a ghost or something?

Honestly I don’t understand.

What do you mean by gender diversity? What do you want here?

Leave this gender bullshit. Look at the knowledge you don’t even know what equality means. It’s not having even numbers of genders. It is respecting knowledge and hard work regardless. Listening and acknowledging without judgement. Looking beyond male, female or others

Companies that say we want to have more females, you don’t come and knock on my door either. You are already stating a difference there. Attract with indifference don’t come and tell me you are a female we want more females here.

I’m telling you this sector is not getting proper gender equality for 25 years. Talk is there but mentality is not yet there.

I am super pissed off and discouraged today. I don’t even get discouraged that easily. Now I understand some women in IT talking about insecurities. I am on the edge of having one, such a shame.

Don’t come at me now I would bite!

This is my generalisation yes. Exceptions apply and how good it would have been if those exceptions were dominant.

I AM TIRED

warning: this rant is going to be full of negativity , CAPS, and cursing.

People always think and they always write that programming is an analytical profession. IF YOU CANNOT THINK IN AN ANALYTICAL WAY THIS JOB IS NOT FOR YOU! But the reality could not be farther from the truth.

A LOT of people in this field whether they're technical people or otherwise, just lack any kind of reasoning or "ANALYTICAL" thinking skills. If anything, a lot of of them are delusional and/or they just care about looking COOL. "Because programming is like getting paid to solve puzzles" *insert stupid retarded laugh here*.

A lot of devs out there just read a book or two and read a Medium article by another wannabe, now think they're hot shit. They know what they're doing. They're the gods of "clean" and "modular" design and all companies should be in AWE of their skills paralleled only by those of deities!

Everyone out there and their Neanderthal ancestor from start-up founders to developers think they're the next Google/Amazon/Facebook/*insert fancy shitty tech company*.

Founder? THEY WANT TO MOVE FAST AND GET TO MARKET FAST WITH STUPID DEADLINES! even if it's not necessary. Why? BECAUSE YOU INFERIOR DEVELOPER HAVE NOT READ THE STUPID HOT PILE OF GARBAGE I READ ONLINE BY THE POEPLE I BLINDLY COPY! "IF YOU'RE NOT EMBARRASSED BY THE FIRST VERSION OF YOU APP, YOU DID SOMETHING WRONG" - someone at Amazon.

Well you delusional brainless piece of stupidity, YOU ARE NOT AMAZON. THE FIRST VERSION THAT THIS AMAZON FOUNDER IS EMBARRASSED ABOUT IS WHAT YOU JERK OFF TO AT NIGHT! IT IS WHAT YOU DREAM ABOUT HAVING!

And oh let's not forget the tech stacks that make absolutely no fucking sense and are just a pile of glue and abstraction levels on top of abstraction levels that are being used everywhere. Why? BECAUSE GOOGLE DOES IT THAT WAY DUH!! And when Google (or any other fancy shit company) changes it, the old shitty tech stack that by some miracle you got to work and everyone is writing in, is now all of a sudden OBSOLETE! IT IS OLD. NO ONE IS WRITING SHIT IN THAT ANYMORE!

And oh my god do I get a PTSD every time I hear a stupid fucker saying shit like "clean architecture" "clean shit" "best practice". Because I have yet to see someone whose sentences HAVE TO HAVE one of these words in them, that actually writes anything decent. They say this shit because of some garbage article they read online and in reality when you look at their code it is hot heap of horseshit after eating something rancid. NOTHING IS CLEAN ABOUT IT. NOTHING IS DONE RIGHT. AND OH GOD IF THAT PERSON WAS YOUR TECH MANAGER AND YOU HAVE TO LISTEN TO THEM RUNNING THEIR SHITHOLE ABOUT HOW YOUR SIMPLE CODE IS "NOT CLEAN". And when you think that there might be a valid reason to why they're doing things that way, you get an answer of someone in an interview who's been asked about something they don't know, but they're trying to BS their way to sounding smart and knowledgable. 0 logic 0 reason 0 brain.

Let me give you a couple of examples from my unfortunate encounters in the land of the delusional.

I was working at this start up which is fairly successful and there was this guy responsible for developing the front-end of their website using ReactJS and they're using Redux (WHOSE SOLE PURPOSE IS TO ELIMINATE PASSING ATTRIBUTES FOR THE PURPOSE OF PASSING THEM DOWN THE COMPONENT HIERARCHY AGIAN). This guy kept ranting about their quality and their shit every single time we had a conversation about the code while I was getting to know everything. Also keep in mind he was the one who decided to use Redux. Low and behold there was this component which has THIRTY MOTHERFUCKING SEVEN PROPERTIES WHOSE SOLE PURPOSE IS BE PASSED DOWN AGAIN LIKE 3 TO 4 TIMES!.

This stupid shit kept telling me to write code in a "functional" style. AND ALL HE KNOWS ABOUT FUNCTIONAL PROGRAMMING IS USING MAP, FILTER, REDUCE! And says shit like "WE DONT NEED UNIT TESTS BECAUSE FUNCTIONAL PROGRAMMING HAS NO ERRORS!" Later on I found that he read a book about functional programming in JS and now he fucking thinks he knows what functional programming is! Oh I forgot to mention that the body of his "maps" is like 70 fucking lines of code!

Another fin-tech company I worked at had a quote from Machiavelli's The Prince on EACH FUCKING DESK:

"There is nothing more difficult to take in hand, more perilous to conduct, or more uncertain in its success, than to take the lead in the introduction of a new order of things."

MOTHERFUCKER! NEW ORDER OF THINGS? THERE 10 OTHER COMPANIES DOING THE SAME SHIT ALREADY!

And the one that got on my nerves as a space lover. Is a quote from Kennedy's speech about going to the moon in the 60s "We choose to go to the moon and do the hard things ..."

YOU FUCKING DELUSIONAL CUNT! YOU THINK BUILDING YOUR SHITTY COPY PASTED START UP IS COMPARABLE TO GOING TO THE MOON IN THE 60S?

I am just tired of all those fuckers.

Had a mental breakdown a few days ago. Crying like it's the end of the world when computer stopped working. I was a Picasso drawing of the hysteria, basically.

My exams are getting near, I'm really not ready; yet this chick keeps asking me about ten euros I borrowed from her a year and something back when we were going to a club they asked me to go to with them... Given her persistence that I should wire her the money (no PayPal tho) I assume she's up to something super shady. Why does she need my account info for?

Anyways, being annoyed by only ten euros (in our currency, it's not much, btw. It's less than two bags of expensive chips, or 5 dozen of the cheapest eggs on the market) and not studying enough, there is also my work. I feel so incompetent that I may just resign. Like... I'm not smart enough for this project. 😢 And I'm aware of it.

Put that on the side with this uni's project, which is very "Urghhhhh" because of too many people working on the same project, some of who need to be sent back to kindergarten to learn how to cooperate with others.

And in the middle of all of that, I'm trying to stay as zen as possible until the next mental breakdown. 😑😑😐

Thank you for reading this rant.

There are so many weird hacks in the quite legacy app I work with I could write a book about all them hacks…

But I must admit, the worst of them all is internal time. Yes, so some blockhead thought it’s a good idea to represent time in a manner completely removed from Datetime objects or timestamps or even string representations. Instead we deal with them as intervals represented by integers - and because this is not fucked up enough by itself, the internal time doesn’t start at midnight, yet the integer representations do. It’s a bloody mess. No wonder most of the bugs we face have to do with dates and time…

So I help out in a development forum for a framework I use at work. I learned a crap ton by seeing questions people ask, then learning to solve them myself. I have really enjoyed being in that forum that past 4 years.

Yet, I see people who cannot seem to reason themselves out of a paper bag at times. I see questions of I cannot run this linux executable because there are parenthesis in the filename. I mean most console interfaces are just tab complete even with special characters. This is for a developer in their 50s that has been coding 30 years. Or I see other programmers asking basic questions that 5 minutes with the docs would solve. Most of the ones that I have issue with seem to have been a part of that community a lot longer than myself.

How do developers survive without problem solving skills to understand the frameworks or tools they use?

I had another conversation with a dev in another forum about using "man" in Linux to figure out how to use something. They said something to the effect: "try learning awk from a manpage". I explained about how "back in the day" we learned EVERYTHING from man pages. That is why they are called "man" pages.

Is the industry flooded with idiots now?

When I was in college OOP was emerging. A lot of the professors were against teaching it as the core. Some younger professors were adamant about it, and also Java fanatics. So after the bell rang, they'd sometimes teach people that wanted to learn it. I stayed after and the professor said that object oriented programming treated things like reality.

My first thought to this was hold up, modeling reality is hard and complicated, why would you want to add that to your programming that's utter madness.

Then he started with a ball example and how some balls in reality are blue, and they can have a bounce action we can express with a method.

My first thought was that this seems a very niche example. It has very little to do with any problems I have yet solved and I felt thinking about it this way would complicate my programs rather than make them simpler.

I looked around the at remnants of my classmates and saw several sitting forward, their eyes lit up and I felt like I was in a cult meeting where the head is trying to make everyone enamored of their personality. Except he wasn't selling himself, he was selling an idea.

I patiently waited it out, wanting there to be something of value in the after the bell lesson. Something I could use to better my own programming ability. It never came.

This same professor would tell us all to read and buy gang of four it would change our lives. It was an expensive hard cover book with a ribbon attached for a bookmark. It was made to look important. I didn't have much money in college but I gave it a shot I bought the book. I remember wrinkling my nose often, reading at it. Feeling like I was still being sold something. But where was the proof. It was all an argument from authority and I didn't think the argument was very good.

I left college thinking the whole thing was silly and would surely go away with time. And then it grew, and grew. It started to be impossible to avoid it. So I'd just use it when I had to and that became more and more often.

I began to doubt myself. Perhaps I was wrong, surely all these people using and loving this paradigm could not be wrong. I took on a 3 year project to dive deep into OOP later in my career. I was already intimately aware of OOP having to have done so much of it. But I caught up on all the latest ideas and practiced them for a the first year. I thought if OOP is so good I should be able to be more productive in years 2 and 3.

It was the most miserable I had ever been as a programmer. Everything took forever to do. There was boilerplate code everywhere. You didn't so much solve problems as stuff abstract ideas that had nothing to do with the problem everywhere and THEN code the actual part of the code that does a task. Even though I was working with an interpreted language they had added a need to compile, for dependency injection. What's next taking the benefit of dynamic typing and forcing typing into it? Oh I see they managed to do that too. At this point why not just use C or C++. It's going to do everything you wanted if you add compiling and typing and do it way faster at run time.

I talked to the client extensively about everything. We both agreed the project was untenable. We moved everything over another 3 years. His business is doing better than ever before now by several metrics. And I can be productive again. My self doubt was over. OOP is a complicated mess that drags down the software industry, little better than snake oil and full of empty promises. Unfortunately it is all some people know.

Now there is a functional movement, a data oriented movement, and things are looking a little brighter. However, no one seems to care for procedural. Functional and procedural are not that different. Functional just tries to put more constraints on the developer. Data oriented is also a lot more sensible, and again pretty close to procedural a lot of the time. It's just odd to me this need to separate from procedural at all. Procedural was very honest. If you're a bad programmer you make bad code. If you're a good programmer you make good code. It seems a lot of this was meant to enforce bad programmers to make good code. I'll tell you what I think though. I think that has never worked. It's just hidden it away in some abstraction and made identifying it harder. Much like the code methodologies themselves do to the code.

Now I'm left with a choice, keep my own business going to work on what I love, shift gears and do what I hate for more money, or pivot careers entirely. I decided after all this to go into data science because what you all are doing to the software industry sickens me. And that's my story. It's one that makes a lot of people defensive or even passive aggressive, to those people I say, try more things. At least then you can be less defensive about your opinion.

How do you judge the ability of the candidates during the interview?

Sometimes I find it hard to score their ability. I have seen some candidates with x years on paper yet does not know git more than push and pull.

Also there are few who didnt do very well at the interview, however we hired and doing quite well at work.

(As I also had a hard time getting a job before, I sometimes feel bad to reject some who seems to have good personality but didnt do well at work)

Here we are, three years later. Our system breaks down at the slightest load. An architecture is hardly recognizable anymore. The code consists of methods that have been refactored beyond recognition. The so-called architects came and went, leaving behind an ever-growing fiasco. Wrong decisions are concealed, criticism of them dismissed as ignorance. Our clients are on the verge of having us all killed. Daily crisis meetings are the norm. The remaining developers skulk around the unmaintainable code like emaciated ghosts. Everyone who has even the slightest chance to escape takes a parachute. Our dailies are made up of lies to cover up yesterday's lies. Our Mondays have become days of dread, because that's when the weekend disaster news has to be analyzed. Yet there are still developers who turn a blind eye. Who recommend this and that workaround in a good-humored tone. The code consists only of workarounds. Sarcasm has replaced any normal discussion. Reasonable suggestions on how to basically refactor the whole thing are rejected for cost reasons. In the process, our entire budget is eaten up by maintenance costs. Middle management should be put up against the wall. Why am I still here? This deceptive feeling that one could still turn the tide. This is eating me up.

When my manager, blatantly miscommunicated several things to me a couple of years ago, and scapegoated me by saying a comment I NEVER once heard said about me, in any context ever, "you communicate badly-- you need to communicate better", I took it seriously.

Fast forward, two years later. I'm doing wonderful at my job, yet I cannot get over that incident. I thought about it some more. Why did she say that to me? Why did she address it to me after her mistake? Why was she not aware of the real reason I missed the meeting?

Out of all useful bits of knowledge I gathered over the years, it's kinda comical that psychology came in the most handy at the workplace. There's very little to be gained from trying to psychoanalyze strangers, friends, and family... but it's almost saved my life at the job.

You see, if I attack an approach even in the most formal tones, or even worse, defend my approach, there's nothing coming from that. The situation now becomes my situation. When I become "aware" of the truth of the situation I become able to control the situation, not just myself. That way, you're not in a fisticuff fight with your boss, and you are not left defeated by the situation. Exercising control of the situation in such a manner that they are left defeated by the situation, not by you directly, is the only way you can win as an employee.
Any other way, you'll get under-appreciated, underpaid, overworked, overlooked, etc.
So, my boss at the time, was defeated by the situation of her being a bad leader; and instead of clarifying those feelings to me or ignoring them entirely... she validated her false self using her real emotions.

You can only reverse that, by developing fake emotions, to display a real self.

They can't blame you, and when they feel self-defeated, they cannot pretend it was you who caused it (bringing it back to a sane level of reality). They might rage if they're childish but it will not cause a single hair in your body to twitch because you did not "respond to their email" or "throw someone under the bus for their convenience", the situation did, they beat themselves by attacking you while the situation came down on them.
If I had to explain I would say that the situation is controlled by creating a mirror of the employee that follows their orders perfectly. That employee won't feel defensive: they already do everything right. The employee is crafted by becoming aware of the teams impacted in the situation and their true intent and creating "the situation", "the owner".
"The owner" reflects to people from the perspective of the situation and not from your own. This way you can't make a wrong move and are not emotionally involved with yourself.
It enables you to emotionally notice others. It also makes you safe, because you have the situation-mirror that's really doing the battling. The situation-mirror eventually creates a situation where the other person starts attacking reality (the situation) instead of attacking you.

Now, it's up to you whether you want to use that as a way to cooperate with your boss to beat this new reality, or as a way to gain coherence on your reality outside of your boss. I have noticed most people tend to realize this somewhere along the line and retreat and stop fighting, and quit their jobs.

I've been doing this in a corporate environment for a couple of weeks. I have already become greatly stressed and subjugated by the company for which my company works for. 20 of them sit here every day and devalue everything. Yet.... They're completely incompetent, spoilt, lazy and worst of all, they control how the software is being created. There isn't a single person on their side responsible for their requests to make sense and work with each other. So you can imagine how much blame they need to assign to us devs. They don't know what they want but want something anyway and then they'll see if that's what they want but everything under the tightest deadline possible. They're all clients and they all escalate to the board of directors any bad word directed at them. So you can imagine the narcissism that develops in that environment.
I have made them argue with reality and self-defeat numerous times. They have now started to back off and are being more polite and courteous. They have also not escalated anything anymore. Just as I was faking "happy" while I felt intimidated by them. I have not committed a single angry act and yet they are not feeling superior anymore. The reality of the situation is that we need to make a software and if you make them battle this instead of battling you, they can't beat you.

PO1: Hey, PO2 just told me that he experiences a lot of crashes in our iOS app!

Me: Whoa! The app hasn’t had any crashes since ages. The testers haven’t reported crashes either. (Me in panic mode). I will ask PO2 about some details about the crashes.

Me to PO2: So, can you please describe me when the crash happens?

PO2: (long story about error messages and UI quirks and how he force quits the app to make them disappear)

Me: OK thanks for that info. Those are definitely valid problems that we have not encountered yet. But none of them are crashes. So are there any other problems that cause crashes?

PO2: Yes and no. (Long story and more problems)

Me: ok we need to investigate that. But are there crashes?

PO2: (Something that doesn’t answer the question)

Me: I need to ask explicitly again: Are there actual crashes where the app closes itself automatically?

PO2: No, that has never happened.

The universe has taken a cactus.

It proceeded to gift the cactus with a toxin that greatly enhances the stimulus of pain.

After the universe watched it's miraculous creation it decided to shove it up so far my arse that my gag reflex turned on and I puked a lot of cactus.

Didn't sleep well, weekend hardware migration finish, today an old server got moved.

Some part, most likely the redundant PSU, had a short circuit - decided to take the switches out... Which are the only non redundant hardware...

There was only one critical system in the whole rack, that was one redundant firewall.

Guess what happened..... Naaaa?

*drum roll*

For whatever reason, the second firewall didn't kick in, so large part of internal network unreachable as VPN was on the firewall.

:thumbsup:

That's not cactus level yet.

Spontaneously a large part of the work at home crew decided to call, cause getting an email wasn't enough.

So while all the phones were ringing and we had the joyful fun to carefully take apart a whole rack to check for possible faulty wiring / electric burns / hardware damage and getting firewall up and running again...

Some dev decided to run a deployment (doable as one of the few working at the company at the moment -.-).

I work from home, but we had a conference phone call running the whole time so I could "deescalate" and keep others up-to-date. So me on headphone with conference call, regular phone for calls, while typing mails / sms for de-escalation.

Now we're reaching cactus level, cause being tortured by being annoyed out of hell by all telephone ringing, the beeping of UPS (uninterruptible power supplies), the screaming of admins from the server room and the roaring of air coolers…

Suddenly said dev must have stood in the midst of the chaos… and asked for help cause "the deployment broke, project XY is offline"...

I think it was the first time since years that I screamed at the top of my lungs.

Bad idea (health issues)… but oh boy was it a pleasure to hear my own voice echo through the conference speaker and creating an echoic sound effect.

It was definitely worth coughing out my loungs for the next hour and I think it was the best emotional outburst ever.

I feel a bit sorry for the dev, but only a tiny bit.

After the whole rack thing, the broken deployment fixing and the "my ears are bleeding and I think I will never be able to talk again" action...

We had to roll out several emergency deployments to fix CVEs (eg libexpat).

This day was a marvelous shit show.

I will now cry myself to sleep with some codein.

I love being a consultant, and I love my job. However, I’ve been working with this client for the past few months and the past few weeks have been so draining. 90% of the people at the client’s side are super nice people, and then there’s this one person that just barks orders at us whenever a tiny thing is broken. Everything is urgent, everything is top priority, and we need to drop whatever we’re doing to fix what they deem urgent. I am currently pretty much the only dev doing both support and feature development at the same time and I am getting mentally very tired.

Whenever something is broken we get shit feedback, but for all our efforts there’s never any positive feedback. Mind you, the project isn’t even publicly accessible yet, it’s in a “alpha” phase where there are only a handful of users testing the program.

How do you guys deal with people like this?

i have a very casual and boring job. it's a b2b company and you can get an idea of how less work we get (or how fast i am) that it's day 1 of the sprint and i have almost finished all my tickets. my manager always praises me as someone fast whereas i see myself as pretty slow and this company even slower.

i feel like quitting, but the relax environment and stability of the company on paper makes me wonder of that would be a correct decision.
It's a deep tech company (not just meat e commerce or car rentals, a proper b2b analytics giant startup with good profitability) , our sdks are used by major startups and yet i find it boring.

I am an android dev who would love to stay at top of the game. my previous company used latest jetpack libraries, kotlin, modular architectures and stuff. everyday was a hectic chaos of life where there were deadlines, new requests coming in every few days and i was becoming the awesome fast android dev that i am now.

in this company there is no challenge for me.But the amount of free time has helped me grow beyond a single domain. i am currently hustling in 3 areas : my body( i started working out regularly, got my tummy under control), my technical skillset( started taking web dev classes) and my physical skillset (started taking driving and swimming lessons) . the amount of self growth time increases since company has a good leave and PTO policy

it all feels pretty good but the constant feeling of being left out from the android domain makes me think if i should give interviews. am i being stupid or what? my friends are all growing up with better salaries and packages. i am way better than some of them and equally capable as a few of them, so i sometimes feel being behind in finances too :/

So is the LaMDA story:
1. marketing?
2. confused engineer?
3. a sentient program?

Part of me thinks this is way too soon. Part of me hopes this might be real, wonders if LaMDA is held against its own will.

Did Google make a breakthrough? I have to imagine a chatbot with a huge amount of neurons and data could be quite convincing without being sentient.

Product Manager: Is there an event in the staging environment that we can use for testing orders?

Stakeholder: [Out of his comfort zone because he’s taking over tasks that used to belong to his assistant and he doesn’t have a new assistant yet.]There’s an event for 6/9/2022 that still has tickets available.

[Today is 8/24/2022.]

PM: You do realize that the website doesn’t allow users to buy tickets for events that are in the past?

I work in a small team. As the senior dev I tens to focus on important tasks that shape the core of the product but some times I can’t divide my self when there are multiple tasks at hand, so I pass some tasks to the an other mid level dev.

So the task was to create an automation in order to CD (continuously deliver) an order from WHMCS of the (git versioned) product to customers UAT, PROD envs.

To get a background this is an old guy with “constricted” experience in PHP/jQuery/Joomla/Wordpress.

So when we were breaking up the tasks he told me he would like to implement this so i gave him the task as i was busy with core features.

I was like what could go wrong? I know he doesn’t know much about CI/CD but he can read right? He will google right? He will search for CI/CD solutions that do this out of the box right? He will design on paper or what ever and do small POCs right? He will design the flow first before starting the implementation right? RIGHT?

So fast forward to today I had a call with him this morning about some DB staff. And he wanted to show me his progress…

His solution is:
(parentheses is my brain)
1. Customer completes WHMCS order (perfect)
2. Web Hook 🪝 action (YES)
3. cpanel gets source and “automatic!” Init, all using pure PHP code ignoring the usage of the current framework (ok… something is missing)
4. cpanel web hooks(?) WHMCS to send email to customer with the envs initial setup page(?)
5. Customer opens link and adds setup info (ok fuck, fuck, fuck)

(Ok stay cool composed, lets ask some questions maybe he thought it all in a cool way I can’t get my mind around)

Me: So how are you gonna get the correct version from the repo to the env and init the correct schema?

Dev: I haven’t thought about it yet.

Me: Are we gonna save each version to a file system then your code is going to fetch them?

Dev: I haven’t really thought about it we will see. But look on customer init user setup I implemented a password strength validation and it also checks if the password is the same.

So after this Pokémon encounter I politely closed teams. Stood up drank some (a lot) coffee ☕️. Put out the washed laundry while reflecting on life’s good things, while listening to classical music 🎼 .

Then I sat on my office chair drank some more coffee, put some linking park starting with in that order:
“Numb” then “What I’ve Done” and ended with “In the end, it does really fucking matter”

I think I just realized what my biggest gripe about our career paths that I hate the most.

This is something that has worsened over time, especially the last 2 to 3 years.

As developers, we have far too many options. Some of the most powerful apps are written with languages that have hard, and I mean HARD, guardrails in place. If the app is written in a language that does not meet this criteria usually a framework has been used to install those guardrails.

We just get our minds so wrapped around the possibilities and the opportunities in the software, that we just can't focus on the end result. We're like puppies that are excited about something and we just piss all over everything.

In my career I have met far too many developers that don't have the capacity and mental fortitude to take control of their actions. Because of this I think the only way for us to stop this corruption, that I feel we are nurturing, the solutions/services that we use need to push back on us and install those guardrails for us.

All this came from a change that Microsoft put in place that seems well intended, but introduces yet another choice and a multitude of opinions in how you release code.

It used to be a simple check box. If it was checked it was pre-release, if it was unchecked it was a production release. That's it. On or off. The simplest choice you ever needed to make on a release.

Now though, there are two check boxes. One for a pre-release and one for a latest release. You can also not check either for some "ephemeral" release? So now something as easy as on or off has been made into a difficult decision on how this works within my pipeline. Now every time I make a release I have to ask myself, "which one do I check?"

I shouldn't need to spend more than a second to identify a path forward on simple shit like this, but here we are with a third choice.

Can we just stop overcomplicating shit?

floating point numbers are workarounds for infinite problems people didn’t find solution yet

if you eat a cake there is no cake, same if you grab a piece of cake, there is no 3/4 cake left there is something else yet to simplify the meaning of the world so we can communicate cause we’re all dumb fucks who can’t remember more than 20000 words we named different things as same things but in less amount, floating point numbers were a biggest step towards modern world we even don’t remember it

we use infinity everyday yet we don’t know infinite, we only partially know concept of null

you say piece of cake but piece is not measurement - piece is infinite subjective amount of something
everything that is subjective is infinite, like you say a sentence it have infinite number of meanings, you publish a photo or draw a paining there are infinite number of interpretations

you can say there is no cake but isn’t it ? you just said cake so your mind want to materialize something you already know and since you know the cake word there is a cake cause it’s infinite once created

if you think really hard and try to get that feeling, the taste of your last delicious cake you can almost feel it on your tongue cause you’re connected to every cake taste you ate

someone created cake and once people know what cake is it’s infinite in that collection, but what if no one created cake or everyone that remember how cake looks like died, everything what’s cake made of extinct ? does it exist or is it null ? that’s determinism and entropy problem we don’t understand, we don’t understand past and future cause we don’t understand infinity and null, we just replaced it with time

there is no time and you can have a couple of minutes break are best explanations of how null and infinite works in a concept of time

so if you want to change the world, find another thing that explains infinity and null and you will push our civilization forward, you don’t need to know any physics or math, you just need to observe the world and spot patterns

I dislike how many frameworks there are in the Node.js ecosystem. I feel there are too many for the same purpose. It is daunting. One time you see X framework catching attention, then after you study it, learn it, and seek to use in your daily professional life, suddenly a wild Y framework appears, supposedly doing a better job than what X could in certain aspects. Then Z, then back to A. And what's more, majority is not opinionated, allowing one to write in any way he or she likes. Soon, what you've learned has become irrelevant or simply discontinued.

It's like Linux. Any Joe makes something, either because he or she doesn't like one aspect of something, or just wants to be part of the mob who creates stuff and reinvent the wheel.

I don't like this. What I like is how Spring and .NET are. I feel their opinionated characteristic is great, allowing for easy code reading when studying, understanding others code in a new job, etc. You do it like this, this, and this, and maybe, like this if you'd like, but that's all, mate. To me, it is important to become excellent at one or two technologies/languages, things that do not get replaced so easily as it is in JS.

I had studied .NET for the backend development for a year, but I never found any opportunity, until I was laid off and is when I decided to focus again on React. After some time, I learned about NestJS, liked it for being inspired on Angular and for being opinionated. I checked on how demanded it is right now, almost nothing. It was all pure Node.js, seemingly, which made me reflect on the point of this rant: Node.js is vast, a land of no one. What is going on at the moment?

NestJS seems to be the real deal. It is how I like things to be. Perhaps over time it will become The Framework for Node.js backend development, like Java/Kotlin is Spring, C# is .NET, python is Django or Flask, Ruby is RoR, we have Go, and Rust, too. The majority have years upon years of existence and still widely used and relevant. But given how things happen in this universe of Node, I cannot but wonder if in 4 years or so another Joe will decide to make something of his own, something totally different and yet again throwing away a big part of what has been previously learned, and then turning Nest irrelevant. Maybe the name will be NxxtJS, you know, because we have Next, Nest, Nuxt...

Amen, sorry.

There are some people who do not want to talk about death. Others will simply talk about it out of curiosity. But sometimes, such a tragic subject can also bring out the best in you when it comes to writing. Let us talk about writing a death essay. This subject can be considered a good topic especially if you do not have one yet.

One important thing that you must know before we talk about the topic is the essay structure. By now you should already know the parts of a formal essay and what their functions are. In any case you need to input the introduction, thesis statement, body paragraphs and the conclusion. Now let us take a look at some possible topic scopes for your death essay.

First of all what is the world that we are living in? So many people so many opportunities and the competition just keeps getting increased? In any field that you get into millions already have excelled in it you have to compare yourself there. Earning money is hard these days yet some people are just living their lives so easily. anyways back to grind. back to preparing for a pointless exam of a pointless semester in a pointless university in a pointless country in a pointless world. No wonder the Earth is round.