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

Got assigned an intern to mentor him, with an explicit order not to do any of the legwork for him.

We start out with some fuzzy requirements. Intern starts overengineering a generic solution, so I make out a best architecture that conforms to the business requirements and I explain it to the intern why are we going to use such approach and tell him how we are going to do it in three phases.

I explain the intern the first phase, break it down in small tasks for him and return to my projects...

After a couple of days of no words from the intern, I decide to check up on him to see how is he progressing, only to hear him complaining the task is boring. So, instead of doing the assigned tasks, he decided he should do a "design" for a feature I told him explicitly not to do, since it is going to be designed by the design team later on.

I explain it to the intern that we have to do the boring task first because we can't proceed with the next phase of the implementation without the necessary data from the phase one.

Intern says okay and assures me he got it now. Few days later, I check up on him, and he tells me he feels he is doing all the work and that I don't contribute to the project. I call up my boss and tell him intern wants a meeting. Since I was working from home, I quickly pack my things and head to the office. Boss talks to the intern before I managed to get to the office. Once I got there, I meet the intern, and he tells me everything is okay. I ask what did the boss say to make things okay all of a sudden, and he tells me he said we are a team now. Our company has a flat hierarchy model, so he tells me he doesn't feel he needs a mentor, that we are both equal, and that I have no idea how to work in a team, and then proceeds to comfort me on how human interaction is hard and that I will learn it one day... I was like wtf?

I tell him to finish the phase one of the project and start with the phase two, and I leave home again.

I call up my boss and ask him what did he say to the intern, and he says: "nothing much, just explained the project a little bit and how it fits in the grand scheme of things.". I ask about the equal team members thing, and me not being a mentor any longer, the boss goes wtf, saying he never said anything about that to him.

So the kid can't focus on a single task, over-engineers everything and doesn't feel he can learn anything from developers with more experience, doesn't want to obey commands, and also likes to lie to manipulate others.

Tomorrow we'll decide what to do with him...

Sorry for the long rant, it was a long stressful day.

There's this guy where I work who's one of the senior linux engineers. To me, he's like a linux god. He knows how to solve the most difficult problems and somehow copes with all the stress/workload. Next to that, he's only one year older than me!

Whenever I'm at work, I consider myself a junior, which I actually am. I also, as said earlier, see this senior guy as a fucking linux god and consider myself to be an absolute newbie around him but he is the most kind/friendly guy ever.

But then, today, something happened which made me feel like a god in front of him, a very, very weird feeling.

For him, doing his stuff is the most normal thing in the world while for me, it's still a learning process.

For me, programming is the most normal thing in the wold, while for him, it's still something he just knows the very basics of.

He asked me if I knew something about javascript/jquery. Said yes as I often program/script in javascript.

Explained me what he wanted to get done, it was a very simple thing for me but after hours of online searching, his lack of javascript knowledge still got him nowhere.

Told him I'd give him a working script in 30 minutes. Emailed it to him in 10.

He seemed/reacted the way I always do when he solves something I have no clue how to solve.

It was really weird to witness *him* being amazed of something that *I* made/did.

Today was a good day where I saw that one person's limitations can be anothers' most easy thing, even if that another person sees that one person as a god.

When our sales guy came by for the 200000000000th time on a day to boast about how good he advised someone on a sales related matter.

Mate, we're Linux engineers and currently trying to fix shit up so why don't you get yourself a cup of shut the fuck up.

A group of ten top software engineers is sent to a class for aspiring managers. The teacher walks in and asks this question:

"You work for a software company which develops avionics (software that controls the instruments of an airplane). One day you are taking a business trip. As you get on the plane you see a plaque that says this plane is using a beta of the software your team developed. Who would get off?"

Nine developers raised their hands. The teacher looked at the tenth and asked, "Why would you stay on?"

The tenth said, "if my team wrote the software, the plane would not get off the ground, much less crash.

So i've been a dev manager for a little while now. Thought i'd take some time to disambiguate some job titles to let everyone know what they might be in for when joining / moving around a big org.

Title: Senior Software Engineer

Background:
- Technical
- Clever
- Typically has years experience building what management are trying to build

Responsibilities:
- Building new features
- Writing code
- Code review
- Offering advice to product manag......OH NO YOU DON'T CODE MONKEY, BACK TO WORK!

Title: Dev Manager

Background:
- Technical
- Former/current programmer
- knows his/her way around a codebase.

Responsibilities:
- Recruiting / interviewing new staff
- Keeping the team focused and delivering tasks
- Architecture decisions
- Lying about complexity of architecture decisions to ensure team gets the actual time they need
- Lying about feature estimations to ensure team gets to work on critical technical improvements that were cancelled / de-prioritised
- Explaining to hire-ups why we can't "Just do it quicker"
- Explaining to senior engineers why the product manager declined their meeting request

Title: Product / Product Manager

Background:
- Nothing relevant to the industry or product line what so ever
- Found the correct building on the day of the interview
- Has once opened an Excel spreadsheet and successfully saved it to a desktop

Responsibilities:
- Making every key decision about every feature available in the app
- Learning to ignore that inner voice we like to call "Common sense"
- Making sure to not accidentally take some advice from technical staff
- Raising the blood pressure of everyone below them / working with them

Title: Program Lead / Product Owner

Background:
- Capable of speech
- Aware of what a computer is (optional)

Responsibilities:
- Sitting down
- Talking
- Clicking random buttons on Jira
- Making bullet point lists

Title: Director of Software Engineering

Background:
- Allegedly attended college/university to study computer science
- Similar to a technical product manager (technical optional)

Responsibilities:
- Reports directly to VP
- Fixes problems by creating a different problem somewhere else as a distraction
- Claiming to understand and green light technical decisions, while having already agreed with product that it will never happen

Tech industry: "We need thousands upon thousands of engineers!"*

* With a minimum of 5 years+ experience in about 30 technologies, able to do magic and ride unicorns while working 28 hours pr day just for the lolz of it. We do not provide training, courses or certifications of any kind. You are supposed to be able to pull those out of your ass yourself!

At my previous job we had the rule to lock your PC when you leave. Makes sense of course.
We were not programmers but application engineers, still, we worked with sensitive data.

One colleague always claimed to be the most intelligent and always demanded the "senior" - title. Which he obviously did not deserve.

multiple times a day forgot to lock his workstation and we had to do it for him.
My last week working there, I've had it. He forgot it again... So I made a screenshot of his current environment. Closed everything. Set his new background with the screen shot and killed explorer (windows). Then finally I locked his PC.

When he came back he panicked that his PC froze. He couldn't do shit anymore. Not knowing what to do... 😂
Which makes him a senior of course.

But seriously, first thing I would do is open the task manager and notice that explorer wasn't running... Thus my background with the taskbar isn't real.... My colleagues must be pranking me!

Nope... The "senior" knew little

At work today, a colleague was talking to a customer. Only maccer in the building (every other Linux (support) engineer uses Linux).
CW: ahhh we understand eachother, Mac is the way to go!
*Gets nasty looks from about all Linux engineers*
CW: I'm going to retract that since I want to make it to the end of this day alive 😅

*Everyone laughing*

Imagine if a structural engineer whose bridge has collapsed and killed several people calls it a feature.

Imagine if that structural engineer made a mistake in the tensile strength of this or that type of bolt and shoved it under the rug as "won't fix".

Imagine that it's you who's relying on that bridge to commute every day. Would you use it, knowing that its QA might not have been very rigorous and could fail at any point in time?

Seriously, you developers have all kinds of fancy stuff like Continuous Integration, Agile development, pipelines, unit testing and some more buzzwords. So why is it that the bridges don't collapse, yet new critical security vulnerabilities caused by bad design, unfixed bugs etc appear every day?

Your actions have consequences. Maybe not for yourself but likely it will have on someone else who's relying on your software. And good QA instead of that whole stupid "move fast and break things" is imperative.

Software developers call themselves the same engineers as the structural engineer and the electrical engineer whose mistakes can kill people. I can't help but be utterly disappointed with the status quo in software development. Don't you carry the title of the engineer with pride? The pride that comes from the responsibility that your application creates?

I wish I'd taken the blue pill. I didn't want to know that software "engineering" was this bad, this insanity-inducing.

But more than anything, it surprises me that the world that relies so much on software hasn't collapsed in some incredible way yet, despite the quality of what's driving it.

HR made a day long inclusiveness meeting. About why there are so few women in the department. Basically the conclusion the HR rep was looking for was “toxic masculinity” and it was super uncomfortable.

The engineering teams couldn’t actually participate much because most of them worked on teams without any women and have absolutely nothing to do with hiring. The male engineers were trying to play along and give the right answers. We had to do flip charts and beak into teams and etc.

The HR kept singling out the same three women in engineering and telling the men to “shut up and listen to them”. The female engineers were like, “i don’t know. I don’t have much to say about it.” The HR rep continued to drill those three women to the point that it was uncomfortable.

The engineering hiring manager lost it before noon. He went to his desk and grabbed a stack of resumes. “You gave me a stack of 60 resumes. Looking at names only four applicants are female. Those applicants don’t have education or experience for engineering. If you want more female engineers in the office you have to put qualified applicants into the stack. Forcing these three engineers to talk in front of our department over and over and saying the men have to shut up is not making the workplace less toxic.” Then he told the three engineers, “This meeting is now optional for you three and you are welcome to do anything you want with your time.”

After lunch, all the female engineers went back to their desk and worked. The HR continued to shame the men in an angrier tone for the rest of the day telling everyone “how men can be” from personal experience because they were the ones now representing all women.

Eight bloody hours of that.

A group of ten top software engineers is sent to a class for aspiring managers. The teacher walks in and asks this question:"You work for a software company which develops avionics (software that controls the instruments of an airplane). One day you are taking a business trip. As you get on the plane you see a plaque that says this plane is using a beta of the software your team developed. Who would get off?"Nine developers raised their hands. The teacher looked at the tenth and asked, "Why would you stay on?"The tenth said, "if my team wrote the software, the plane would not get off the ground, much less crash."

Servers down.....
Everyone : Best day ever. 😎 Screw you guys , I'm going home.
Network Engineers : 😭😲😰

A room full of mostly old male stressed out engineers sat in chairs, and the presenter said:

"So who watched Judging Amy last night?"

The presenter went on to express her surprise that nobody in the room had seen last night's episode of Judging Amy.... and wasn't going to drop the topic.

The meeting, if it ever had any, now had no chance of going anywhere good.

By the end of the meeting someone would walk out and "retire" shortly there after, and it certainly wasn't going to be the presenter....

Backstory:

The company built on the IBM model of sell pricey custom hardware (granted it worked really well) and sell expensive support contracts wasn't doing as well as it had hoped. Granted it was still doing better than most of its neighboring companies, but it was clear that with the .com bust the days of catered lunches every day were over.

The company had grown fat and everyone knew that while the company had a good enough product(s) to survive, there weren't enough lifeboats for everyone to survive.

In the midst of this an HR department that took up nearly 20% of the office space at HQ felt it needed to justify its existence / expenses.

They decided to do this in the same way they always had, by taking funding from other departments, this time not by simply demanding more direct budgets for themselves.... they decided to impose mandatory 'training' on other departments ... that they would then bill for this training.

When HR got wind that there were some stressed out engineers the solution was, as it always is for HR.... to do more HR stuff:

They decided to take these time starved engineers away from their jobs, and put them in a room with HR for 4 days. Meanwhile the engineer's tasks, deadlines and etc remained the same.

Support got roped into it too, and that's how I ended up there.

It would be difficult to describe the chasm between HR and everyone else at that company. This was an HR department that when they didn't have enough cubes (because of constant remodeling in the HR area under the guise of privacy) sat their extra HR employees next to engineering and were 'upset' that the engineers 'weren't very friendly and all they did was work'.

At one point a meeting to discuss this point of contention was called off for some made up reason or another by someone with a clue.

So there we all sat, our deadlines kept ticking away and this HR team (3 people) stood at the front of the room and were perplexed that none of these mostly older males in this room had seen last night's episode of Judging Amy.

From there the presentation was chaos, because almost the entire thing was based on your knowledge of what happened to poor stressed out Amy ... or something like that.

We were peppered with HR tales of being stressed out and taking a long lunch and feeling better, and this magical thing where the poor HR person went and had a good cry with her boss and her boss magically took more off her plate (a brutal story where the poor HR person was almost moved to tears again).

The lack of apparent sympathy (really nobody said much at all) and lack of seeming understanding from the crowd of engineers that all they should do is take a long lunch, or tell their boss to solve their problems ... seemed to bother the HR folks. They were on edge.

So then they finally asked "What are your stressers?" And they picked the worst possible person they could to ask, Ted.

Ted was old, he prickly, he was the only one who understood the worst ass hell of assembly that had been left behind.

Ted made a mistake, he was honest with folks who couldn't possibly understand what he was saying. "This mandatory class is stressing me out. I have work to do and less time because of this class."

The exchange that followed was kinda horrible and I recall sitting behind Ted trying to be as small as possible as to not be called on. Exactly what everyone said almost doesn't matter.

A pedantic debate between Ted and the HR staff about "mandatory" and "required" followed. I will just sum it up that they were both in the wrong for how they behaved for a good 20 minutes...

Ted walked out, and would later 'retire' that week.

Ted had a history and was no saint. I suspect an email campaign by various folks who recounted the events that day spared ted the 'fired' status and he walked with what eventually would become the severance package status quo.

HR never again held another 'training', most of them would all finally face the axe a few months later after the CEO finally decided that 'customer facing, and product producing' headcount had been reduced enough ... and it was other internal staff's time for that.

The result of the meeting was one less engineer, and everyone else had 4 days less of work done...

My start at one of the Big Four (accounting firms).

The first two days of each month they organise "onboarding days" for the new starters of that month. (I so hate upper management buzzwords!) They sent me a formal invitation that looked like I was being invited to a ball with the royals, and they included the following super-smarty-pants line: "Dress code: would you wear jeans and t-shirt when you meet a client?"

And I thought: "I'm an effing hardware and software engineer for internal services. I will never meet a client." But I dressed formally nonetheless, and I went to the onboarding, and I hated every second I spent in those effing high heels, and don't get me started on how I managed to get a run on my stockings in the first hour.

The first day of the onboarding we sat through eight hours of general talks from senior employees who wanted to explain the "culture" and "values" of our company, but the worst of all was the three-hour introduction to IT services where they "helped us set up our new laptops" and taught us how to send e-mails and how to use the Company Portal.

On the second day, they divided us into groups depending on our speciality (assurance, taxes, legal, etc) and exposed us to further 8 hours of boredom related to our speciality. However, since the "digital services" thing was still new to them, we didn't have a category of our own, and we had to attend the introduction to one of the other categories, and I didn't understand one word of what was being said.

On the third day I finally went to my office and they provided me with a second laptop. It turns out that we engineers got different laptops and were allowed to manage it ourselves instead of letting central IT manage it for us. So I simply returned the laptop they had given me the first day and started working. However, for some reason, the laptop I returned was not registered, and two weeks later they started pestering me with emails asking where was the laptop "I had stolen". It took me 3 weeks of emails and calls to make them understand that I had returned the laptop immediately.

Also, on the two onboarding days we had to sign attendance, and since I forgot to sign the paper list on the second day, they invited me to the event the next month again. I explained to them that I had already attended the onboarding and didn't go, so they invited me again on the third month, and they threatened me with "disciplinary action" if I didn't go. After a week of lost time writing emails and calling people, I ended up going to the onboarding again just to sign the effing list.

In the end, I resigned during the probation time. That company was the worst experience of my life. It was an example of corporate culture so absurdly exaggerated that it sometimes reminded me of Kafka's Trial. I think they have more "HR representatives" than people who do actual work.

Once upon a time, there were a restaurant called "iEat.tech.com".
It was a small single-location place, where the sufficient number of patrons could be served by the cozy number of employees.
In fact, headcount was so lean that the cook was also the one who washed all the dishes.

But then came the suits and their "VC"(daddy) money and scaled shit up.
Soon, there were so many patrons that the dishes started to pile up the sink, never washed.
"We need someone to wash the dishes!" said the cook
"Fuck you, you wash the dishes!" said the s*its
Naturally, the cook left soon after.

The s*its had a problem now. They could not replace the cook fast enough - all other cooks were either young, inexperienced and mediocre (but did clean the dishes), or refused to waste their time on the sink.
So the suits did what $*its always do - they got a fucking consultant. Who told them to get a fucking dishwashing machine and billed them the GDP of Ireland.

The s*is, of course, did not want to buy a dishwashing machine. "Our fucking process is too fucking disruptive for us to use a fucking store-bought mass-produced metal servant!" (s*its don't know what "machines" are. For them, it's all in terms of "servants", employees and machines alike).

So the s*its hired an engineer to "solve the fucking dish problem, once and for all".
The engineer quickly started measuring and drawing and calculating. The engineer was about to prepare a budget when the s*its came screaming "What the fuck are you doing? There is a fucking pile of dishes in the sink!"
The engineer replied that "I'm designing the machine!", to what the s*its responded "don't bring me fucking problems, bring me solutions!" (or some other s*it blabber)

So the engineer quickly designed an efficient dishwashing assembly line to be done in half the time most people would. And then went back to designing the machine.
But the s*its were having none of it. They kept expanding and expanding and doing what they could so that the engineer never had a moment to work on the machine. They dit it so surreptitiously that no one barely even noticed, but one day they were paying a team of engineers to be fucking human dishwashers.

Now replace "dishes" with "Jira tickets" or "quick fixes" or "tiny changes" and fix other terms accordingly.
Fucking s*its.

One of our newly-joined junior sysadmin left a pre-production server SSH session open. Being the responsible senior (pun intended) to teach them the value of security of production (or near production, for that matter) systems, I typed in sudo rm --recursive --no-preserve-root --force / on the terminal session (I didn't hit the Enter / Return key) and left it there. The person took longer to return and the screen went to sleep. I went back to my desk and took a backup image of the machine just in case the unexpected happened.

On returning from wherever they had gone, the person hits enter / return to wake the system (they didn't even have a password-on-wake policy set up on the machine). The SSH session was stil there, the machine accepted the command and started working. This person didn't even look at the session and just navigated away elsewhere (probably to get back to work on the script they were working on).

Five minutes passes by, I get the first monitoring alert saying the server is not responding. I hoped that this person would be responsible enough to check the monitoring alerts since they had a SSH session on the machine.
Seven minutes : other dependent services on the machine start complaining that the instance is unreachable.

I assign the monitoring alert to the person of the day. They come running to me saying that they can't reach the instance but the instance is listed on the inventory list. I ask them to show me the specific terminal that ran the rm -rf command. They get the beautiful realization of the day. They freak the hell out to the point that they ask me, "Am I fired?". I reply, "You should probably ask your manager".

Lesson learnt the hard-way. I gave them a good understanding on what happened and explained the implications on what would have happened had this exact same scenario happened outside the office giving access to an outsider. I explained about why people in _our_ domain should care about security above all else.

There was a good 30+ minute downtime of the instance before I admitted that I had a backup and restored it (after the whole lecture). It wasn't critical since the environment was not user-facing and didn't have any critical data.

Since then we've been at this together - warning engineers when they leave their machines open and taking security lecture / sessions / workshops for new recruits (anyone who joins engineering).

My most intense day as a dev was when we had a product announcement day (with 70 engineers from dozens of companies invited) and the night before the app still didn't run all of the way through.

My team and I worked all night and had our first successful run-through at 10am when the announcement presentation and demo was at 1pm. All I can say is that I didn't breath when that demo was running live... But it worked flawlessly.

After that experience I realized that I had enough of non-tech management setting unrealistic deadlines, quit that job, and am now helping to build a startup. It has been so much more fulfilling and now I set the deadlines. 😎

Around 45 days ago after years of burnout and abuse I finally quit my job when I finally realised that all the promises of greener pastures and reinforcements were nothing but tales of sugar candy mountain.

I had no idea where or what I wanted to work on or even have any leads for work but I knew if I kept recursively burning out soon there wouldn't be anything left of me to give.

Flashforward 45 days and I am the proud owner of Sane software solutions which I am currently the only full time employee of.
My old company has become my customer since no one else knows the legacy system, 11 days after quitting their invoice exceeded my previous salary with a quarter of the work and I just landed an awesome contract with some engineers I feel privileged to listen to working on some neat IOT stuff, I've quadrupled my income and now work an 8 hour day.

Don't be despondent, there are better things in life to bleed for than another mother fuckers ambitions ✌

Our customers are fucking incredible QA Engineers, holy fuck tits. Every single day, some fucking fuckface finds a way to break this garbage can legacy application that I've spent the last year combing over and patching as I find problems or are otherwise made aware of them.

Honestly, I have some QA background myself, but these types of issues would just absolutely never in a bajillion shitting farting years occur to me to do.

They are masters of breaking shit, I am so FUCKING IMPRESSED. Almost as impressed that this application hasn't been replaced after ten years of bullshit, and that the two massive fucking retards that preceded me didn't just do it the right way by accident or fucking kill themselves out of shame.

“I Pay $900 A Month for student loans.”

Not sure why there’s a video about this but let’s watch it...

*Sad music is playing*

“My name is _____ and I pay $900 a month for student loans..”

Yeah so what?

*Sad music continues*

??

*Woman makes a call and asks about when they’re going to make a student loan reform aggressively*

????

Then I realized my family was eligible for low income and I received Cal and Pell grants to pay for my tuition and living.

Then I realized that the salary for my computer science degree has numbed me to a point where $900 a month doesn’t seem too bad. Or awful. I mean I just leased a new car for my mom! And didn’t hesitate (only when having fun negotiating though).

Back then, I would be shocked. But it’s a surreal feeling to see now that I don’t. I was literally confused at the basis of this video. And now I’m surprised at my disconnect from it.

I also realized that they make videos based on how society should react to it. Am I an outcast to society because of this? Why am I not reacting the same way?

Maybe society (nowadays) would disdain me because I’ve come into high income like we all will because of our passion (and the demand for it).

But fuck society. It’s full of the very same people who use technology each and every day. Protesting for things they found trending on Twitter. The ones who refused to learn even though it’s a huge part of their lives. They’re the ones holding us back for an Engel’s Technological Utopia (idk if I’m even correct about the philosopher but anyways..)

We’re above them. We make things they’ll use and in massive numbers.

Don’t let them dictate what you should like. How you should act. Whether or not you should feel lonely while they’re posting pictures of fun times on Facebook.

We should be the ones doing that. Because we are the ones doing that.

That’s why we’re given the best to perform what we love most.

So devs, continue what you’re doing. Small or big, you’re still driving the world forward. Opening pull requests and contributing to open source projects. Answering questions on Stack Overflow not only for the person intended but for the beginner or even experienced professional who may stumble upon it later in a Google search.

And be highly rewarded for it. How society feels doesn’t matter any more when it comes to your passion. You’re important. Your work helps others in ways you can’t even imagine. We’re like one big fucking hivemind of engineers with the accessibility of the internet.

I love drinking on a Sunday!

Fuck startups.

Back when I was an wee lad I interviewed for an startup, not knowing that startups are not real companies. The scumbag interviewer, who was also the owner of the outfit, asked me what I was looking in a company. I said "fair wages, a non-antagonic environment and projects with real roadmaps".
He asked me to elaborate. I said, "You know, if today your product is a sales platform, I do not want to come into work next week and discover it is now an air travel tickets marketplace, or come back the very next day and discover it is now an automated pizza factory, or in the next day and it is now a crypto exchange..."

The scumbag looked PISSED. "Sorry, but we are looking for someone who likes the challenges of a dynamic environment (read: we do not have a business model and we hate the very idea of trying to make money out of our company), and you do not fit the profile"

Startups are not real companies, i.e. they do not systematically charge money in exchange for goods or services in amounts that exceed the cost of providing said goods or services. Most startups are just tax fronts for money laundering schemes. The rest are just playthings for rich assholes who can't get a real output-producing job. Those two categories are not mutually exclusive.

Take Facebook, for example. The poster child of startups. The Zucker that owns it just announced they are setting impossible performance targets on purpose, not even attempting to hide the fact that it is just a way to lay off large quantities of employees without using the words "massive lay offs". Companies, real thin-margin, lots-of-regulation profit-driven companies do not do that. They are not some sort of "capitalist woke", real CEOs just know that if their companies largely miss performance targets on their tenure, purposely or not, next it will be their neck on the chopping block. Because they can be fired if the KPI charts say they suck. But the Zucker cannot be fired, not even after commanding their beanbag and tap beer offices to be heated exclusively by burning hundred dollar bills.
So the Zucker is not interested in performance. Not even in lay offs as expense cutting measures - investors are an infinite source of free money for startups. The Zucker just wants to project power, especially now that engineers are not so confident in the stability of they high-paying jobs.

So are irrelevant 500-souls-or-less self-aggrandizing startups. Their owners are there because it is in vogue to have a startup or ten. And will have that startup pivot to whatever sounds fancy that season. After all, only poor people care about things like EBITDA and profit margins repeatability - A.K.A. "getting more money".

Fuck startups.

Biggest challenge I overcame as dev? One of many.

Avoiding a life sentence when the 'powers that be' targeted one of my libraries for the root cause of system performance issues and I didn't correct that accusation with a flame thrower.

What the accusation? What I named the library. Yep. The *name* was causing every single problem in the system.

Panorama (very, very expensive APM system at the time) identified my library in it's analysis, the calls to/from SQLServer was the bottleneck

We had one of Panorama's engineers on-site and he asked what (not the actual name) MyLibrary was and (I'll preface I did not know or involved in any of the so-called 'research') a crack team of developers+managers researched the system thoroughly and found MyLibrary was used in just about every project. I wrote the .Net 1.1 MyLibrary as a mini-ORM to simplify the execution of database code (stored procs, etc) and gracefully handle+log database exceptions (auto-logged details such as the target db, stored procedure name, parameter values, etc, everything you'd need to troubleshoot database errors). This was before Dapper and the other fancy tools used by kids these days.

By the time the news got to me, there was a team cobbled together who's only focus was to remove any/every trace of MyLibrary from the code base. Using Waterfall, they calculated it would take at least a year to remove+replace MyLibrary with the equivalent ADO.Net plumbing.

In a department wide meeting:

DeptMgr: "This day forward, no one is to use MyLibrary to access the database! It's slow, unprofessionally named, and the root cause of all the database issues."
Me: "What about MyLibrary is slow? It's excecuting standard the ADO.Net code. Only extra bit of code is the exception handling to capture the details when the exception is logged."
DeptMgr: "We've spent the last 6 weeks with the Panorama engineer and he's identified MyLibrary as the cause. Company has spent over $100,000 on this software and we have to make fact based decisions. Look at this slide ... "
<DeptMgr shows a histogram of the stacktrace, showing MyLibrary as the slowest>
Me: "You do realize that the execution time is the database call itself, not the code. In that example, the invoice call, it's the stored procedure that taking 5 seconds, not MyLibrary."
<at this point, DeptMgr is getting red-face mad>
AreaMgr: "Yes...yes...but if we stopped using MyLibrary, removing the unnecessary layers, will make the code run faster."
<typical headknodd-ers knod their heads in agreement>
Dev01: "The loading of MyLibrary takes CPU cycles away from code that supports our customers. Every CPU cycle counts."
<headknod-ding continues>
Me: "I'm really confused. Maybe I'm looking at the data wrong. On the slide where you highlighted all the bottlenecks, the histogram shows the latency is the database, I mean...it's right there, in red. Am I looking at it wrong?"
<this was meeting with 20+ other devs, mgrs, a VP, the Panorama engineer>
DeptMgr: "Yes you are! I know MyLibrary is your baby. You need to check your ego at the door and face the facts. Your MyLibrary is a failed experiment and needs to be exterminated from this system!"

Fast forward 9 months, maybe 50% of the projects updated, come across the documentation left from the Panorama. Even after the removal of MyLibrary, there was zero increases in performance. The engineer recommended DBAs start optimizing their indexes and other N+1 problems discovered. I decide to ask the developer who lead the re-write.

Me: "I see that removing MyLibrary did nothing to improve performance."
Dev: "Yes, DeptMgr was pissed. He was ready to throw the Panorama engineer out a window when he said the problems were in the database all along. Didn't you say that?"
Me: "Um, so is this re-write project dead?"
Dev: "No. Removing MyLibrary introduced all kinds of bugs. All the boilerplate ADO.Net code caused a lot of unhandled exceptions, then we had to go back and write exception handling code."
Me: "What a failure. What dipshit would think writing more code leads to less bugs?"
Dev: "I know, I know. We're so far behind schedule. We had to come up with something. I ended up writing a library to make replacing MyLibrary easier. I called it KnightRider. Like the TV show. Everyone is excited to speed up their code with KnightRider. Same method names, same exception handling. All we have to do is replace MyLibrary with KnightRider and we're done."
Me: "Won't the bottlenecks then point to KnightRider?"
Dev: "Meh, not my problem. Panorama meets primarily with the DBAs and the networking team now. I doubt we ever use Panorama to look at our C# code."

Needless to say, I was (still) pissed that they had used MyLibrary as dirty word and a scapegoat for months when they *knew* where the problems were. Pissed enough for a flamethrower? Maybe.

Told by Gerald Weinberg in various incarnations:

A group of ten top software engineers is sent to a class for aspiring managers. The teacher walks in and asks this question:

"You work for a software company which develops avionics (software that controls the instruments of an airplane). One day you are taking a business trip. As you get on the plane you see a plaque that says this plane is using a beta of the software your team developed. Who would get off?"

Nine developers raised their hands. The teacher looked at the tenth and asked, "Why would you stay on?"

The tenth said, "if my team wrote the software, the plane would not get off the ground, much less crash."

Do you know what's better than getting work done. HAVING ANOTHER F****ING MEETING ABOUT WHAT WORK NEEDS TO BE DONE!

I COULD'VE HAD MOST OF THIS SHIT DONE BY NOW BUT I HAVE TO SPEND 1/2 OF EVERY DAY JUST EXPLAINING WHAT THE F***K I'M DOING, WHAT THE F**K EVERYONE ELSE IS DOING, AND THEN EXPLAINING WHY IT HASN"T BEEN F***ING DONE!

YOU WANT TO KNOW WHY EVERYONE IS LEAVING WHY YOU CAN'T RETAIN ANYONE? YOU HIRED THEM AS FREAKING ENGINEERS PROMISING THEM THEY WOULD BE ABLE TO DO THINGS AND THEY SPEND ALL DAY IN F***ING MEETINGS WASTING THEIR IQ AND WISHING FOR DEATH!

GGAAAHHHHH! BY THE EMPEROR PLEASE COMMISSAR END ME!

After mass layoffs my team went from 10 engineers to 4 with no drop in expectations. This was a ridiculous ask, everyone was burnt out and could not keep up. For some reason the geniuses in management gave me a bad performance review despite me doing 2 to 3 full time workloads.

That day I put in applications and got an offer in less than a month from one of them. Put in my notice and suddenly it was surprised Pikachu face. Now they are down to 3 engineers and admitted it would be months before they had the revenue to even backfill my position.

Good riddance.

First, they came for those who Open Source'd code.
And I did not speak out, because my code could never be used by anyone out of the company, anyway.

Then, they came for the Trade Unionists.
And I did not speak out, because I was not in a union.

Then, they came for those who worked from home.
And I did not speak out, because I was granted an exception.

Then, they came for Scrum Masters and other Agile practitioners.
And I did not speak out, because fuck those spreadsheet jockeys productivity thespians.

Then, they came for in-house Data Analysts and Data Engineers.
And there was no one left to speak out for us.

Yeah, folks. The day finally came. I'm officially updating my LinkedIn and putting a ridiculous sash under my picture, "open to work". The Layoffs came for me, too.

In the before time (late 90s) I worked for a company that worked for a company that worked for a company that provided software engineering services for NRC regulatory compliance. Fallout radius simulation, security access and checks, operational reporting, that sort of thing. Given that, I spent a lot of time around/at/in nuclear reactors.

One day, we're working on this system that uses RFID (before it was cool) and various physical sensors to do a few things, one of which is to determine if people exist at the intersection of hazardous particles, gasses, etc.

This also happens to be a system which, at that moment, is reporting hazardous conditions and people at the top of the outer containment shell. We know this is probably a red herring or faulty sensor because no one is present in the system vs the access logs and cameras, but we have to check anyways. A few building engineers climb the ladders up there and find that nothing is really visibly wrong and we have an all clear. They did not however know how to check the sensor.

Enter me, the only person from our firm on site that day. So in the next few minutes I am also in a monkey suit (bc protocol), climbing a 150 foot ladder that leads to another 150 foot ladder, all 110lbs of me + a 30lb diag "laptop" slung over my shoulder by a strap. At the top, I walk about a quarter of the way out, open the casing on the sensor module and find that someone had hooked up the line feed, but not the activity connection wire so it was sending a false signal. I open the diag laptop, plug it into the unit, write a simple firmware extension to intermediate the condition, flash, reload. I verify the error has cleared and an appropriate message was sent to the diagnostic system over the radio, run through an error test cycle, radio again, close it up. Once I returned to the ground, sweating my ass off, I also send a not at all passive aggressive email letting the boss know that the next shift will need to push the update to the other 600 air-gapped, unidirectional sensors around the facility.

Once upon a time, one or two jobs ago, a really awesome engineer specced out a distributed search application in response to a business need. This company was managed pretty oldschool and required a ton of paperwork and approvals.

The engineer spent many weeks running tests and optimizing the hell out of this app cluster. It flew, and he had the data to prove it could handle production workloads (think hundreds of terabytes of data being processed every single day)

Part of the way he achieved this was having RAID0 on all of the servers to maximize I/O throughput. He didn't care much about data loss, since the application itself was fault tolerant on a much more granular level.

Management, hearing about this, absolutely flipped their shit and demanded RAID6 instead. This despite the conclusive data that the engineer had that proved RAID6 couldn't keep up.

He more or less got told to STFU.

Even this despite the fact that a RAID restripe would actually take many times longer than rebuilding the failed node from scratch (a process that took about 30 minutes by hand, and could probably be automated to be done in less than five), causing a longer exposure to actual data loss throughout the length of the days-long array rebuild time.

The ill-thought-out requirement added about 50% to the cost of the project (*many* more hard drives now required), beyond the original budget, and the subsequent bureaucratic wrangling resulted in a late product launch.

6 months or so later, after real customers were using this product, the app was buckling under around half of its expected workload. A friend of the engineer suggested to management to try RAID0. Sure enough, that resolved the I/O bottleneck.

This rage-inducing story has a happy ending, though! Said engineer left the company not long after this incident, citing it as a reason for his departure. He was immediately hired by another company, making integer multiples of his prior salary.

The product the company botched the launch of by ignoring his spec? It died a few months later. Maybe the poor customer experience was to blame? Maybe the late launch? Maybe it was another reason entirely.

Either way, millions of dollars of hardware now sat fallow. This was a black eye on the company all the way up to the C-level.

tl;dr: Listen to your engineers. You hired them for their expertise.

Four engineers and a broke down car

One day, mechanical engineer, electrical engineer, chemical engineer, and computer engineer were driving down the street in the same car when it broke down.

The mechanical engineer said, “I think a rod broke”.

The chemical engineer said, “The way it sputtered at the end, I think it's not getting enough gas”.

The electrical engineer said, “I think there was a spark and something's wrong with the electrical system”.

All three turned to the computer engineer and said, “What do you think?”

To which, the computer engineer replied, “I think we should all get out and then get back in”.

!rant
With all the people around here ranting about their PM's, I'm really curious to see how a PMRant app would look like. What are they complaining about?
Devs that listen to music all day long and never want to be disturbed?
Engineers who talk in long, incomprehensible words?
...TDD taking too long?

A group of ten top software engineers is sent to a class for aspiring managers. The teacher walks in and asks this question:

"You work for a software company which develops avionics (software that controls the instruments of an airplane). One day you are taking a business trip. As you get on the plane you see a plaque that says this plane is using a beta of the software your team developed. Who would get off?"

Nine developers raised their hands. The teacher looked at the tenth and asked, "Why would you stay on?"

The tenth said, "if my team wrote the software, the plane would not get off the ground, much less crash."

We don't have to be afraid of AI becoming self-concious and eradicating entire humanity in the near future.

Example 1: Amazon ads. You buy a TV and start receiving ads for YET ANOTHER FUCKING TV. Just in case you'd need a second/third/∞ TV on the same day.

Example 2: Recruiter bot Mail. I HOPE it's a mass mail bot and not a real human being ;)

"we're looking for PHP developers"

SELECT * FROM candidates WHERE experience IN ('PHP')
Gives
+10 to intelligence
+5% to skynet training speed

"we're looking for Java developers"

SELECT * FROM candidates WHERE experience IN ('Java')
Gives
+20 to intelligence
+10% to skynet training speed

"we're looking for frontend developers working with Angular."

SELECT * FROM candidates WHERE projects IN ('frontend') AND experience IN ('Angular')
Gives
+40 to intelligence
+20% to skynet training speed

"we're looking for QA Engineers ready to relocate to Ukraine or Cyprus"

SELECT * FROM candidates WHERE experience IN ('QA') AND location NOT IN (any country with higher living standard, lower living costs and no war)
Gives
+80 to intelligence
+40% to skynet training speed

Example 3: Alexa understands me only if I'm drunk.

IF YOU UPDATE AN ADM PLATTFORM FOR FUCKS SAKE DON'T DO THE FOLLOWING THINGS:

1. ONLY DOCUMENTATE IT IN A POWERPOINT

2. WRITE DOWN IPs AND PORTS ONLY ON A WHITE-BORD

3. MOVE TOOLS TO OTHER SUBNETS OR DOMAINS WITHOUT PROPERLY KNOWING THE WAYS OF COMMUNICATION BETWEEN THEM

4. USE YOUR PERSONAL EMAIL ADDRESS AS RESET OPTION FOR LICENCE-MANAGEMENT ACCESS IF NO ONE KNOWS THE PW

5. LEAVE THE COMPANY THE DAY AFTER THE UPGRADE IS DONE

Because the guy who has to take care of the upcoming problems is not going to like you!

BUT having to deal with all of this at once would not be a problem if your, so called team (30 People who work with those applications e.g. as test-engineers) would actually work together instead of having that "not my daily business, I am going to drink coffee" attitude.

Apparently I am the only one who has enough balls to see, admit, and report a problem to our leadership.
This always leads to Me fixing the issue...
....that's alright I am learning a lot...
...BUT IF A TEAM-MATE, WHO HAS THE SAME DEGREE AS I AM GOING TO GET, LEAVES EARY BECAUSE: "HE DOES NOT KNOW WHATS WRONG", IT TRIGGERS ME!!!

- The apprenticeship guy

PS Needless to say hundreds of clients have access to those systems and I worked through a shittload of official tool docs just to get to know the tools first...

"For me, it means..."

For me it was not one specific meeting, but rather a series of meetings with a customer over some years.

It was like the movie "groundhog day", it was the same all over again.

We had this technical term, and our customer had his own definition of what it meant and what it's supposed to be. No need to say that his definition did not match the one the engineers and developers of the world had agreed on.

At least a dozen times, i convinced him, but as soon as the meeting ends, it's all reset and we start at zero next time with his new or old definition of what a definition should mean. Sometimes i was just sick and tired of it so i let him explain how it is while i just stared into the void. Didn't matter he told me once, it will happen again next time again, like it never happened before.

One of those days when i feel like complete shit and wish i hadn’t woken up.
I heard back from an interview i did last week (one of the faang type) and the recruiter started with “You didn’t impress any of your interviewers”. Man that hurt. I can’t unhear that. He went ahead to say they all recommended a mid-level role for me (they apparently said i had potential and could easily grow into a senior eng) instead of the senior lead i applied for. This is also subject to getting approval to hire mid-level engineers because the team needs more people but they only got approval to hire senior engineers. This cunt also added “dont worry about it. Just go about your usual business and i’ll call you next week if we have gotten the approval”. Ass! All i can do is worry because that is what i do best.
I think i am more sad and disappointed in myself because i thought the interviews went well. Wrote decent code and came up with good solutions on time. Had a good conversation with interviewers. Apparently for a senior, you cannot make mistakes which i did but once the interviewer gave me a clue, i got back on track.
Anyway, i slept with this anxiety, then woke up with tummy ache. On the drive out this morning to go to the bank, i drove my car into a pole and broke off my side mirror. Then my fucking power generator stopped working. And on my way to go and get my fixed mirror from the mechanic, my exhaust pipe broke in half due to a possible pothole i drove into.

Those fucking days where all that could go wrong goes wrong. My head is fucking pounding i can barely move my head without wincing. I am running out of money fast (i support my entire family) and i am worried about not getting a job. This blow to my confidence makes me feel worthless like i am not good for anything. Recruiter suggested i do another senior engineer interview for a different team which i passed the test for but i know the outcome would most likely be the same and i wanted the first team really bad. I just want to lie in bed and cry all day but this fucking headache won’t let me.

I am this die hard fan of  House, MD. A medical Based Drama TV series.

I find soo many similarity between how doctor House diagnosis patients and how we coders debug code.

Why the flying-fuck is there not a similar show for engineers?

Where engineer is followed closes as he debugs a problem? And saves the day?

Why god why.

I just pray for this miracle to happen.

(To start with Dr.House abused vicodin, we coders abuse caffeine and sudo chmod 777 :P )

Engineers day

Tbh my current job is as close to perfect as I can imagine ever existing. The best and smartest engineers I've ever met (better than Google, better than anywhere), all working on something we think is really really important (autonomous cars), and solving hard problems every day (some of which no one else has ever solved before).

Only downside is an internal sense that when I'm not working I'm delaying a product that will save people's lives.

There are a couple of them to list! But to sum my main ones(biggest personal heroes):

John McCarthy, one of the founding fathers of Artificial Intelligence and accredited with coining such term(sometimes before 1960 if memory serves right), a mathematical prodigy, the man based the original model of the Lisp programming language in lambda calculus. Many modern concepts that we have in programming where implemented in one way or another from his systems back in the day, and as a data analyst and ML nut.....well I am a big fan.

Herb Sutter: C++ programmer extraordinaire. I appreciate him more for his lectures and published articles than anything else. Incredibly smart and down to earth and manages to make C++ less intimidating while still approaching it with respect.

Rich Hickey: The mastermind behind Clojure, the Lisp dialect for the JVM. Rich is really talented and his lectures behind his motivations and reasons behind everything he does with Clojure are fascinating to see.

Ryan Dahl: Awww shit y'all know how it is. The man changed web development both in the backend and the frontend for good. The concept of people writing their own servers to run their pages was not new, but the Node JS runtime environment made it more widely available to people by means of a simple to use language that was already popular with web developers. I would venture to say that Ryan's amazing contributions to JS made the language better, as it stands, the language continues to evolve and new features that make it overall better keep being added. He is currently building Deno, which would be a runtime environment for TypeScript, in Rust.

Anders Hejlsberg: This dude was everywhere man....the original author of Turbo Pascal and the lead of Delphi back in the day. These RAD tools paved the way for what would be a revolution in the computing world. The dude is also the lead architect and designer of the C# programming language as well as TypeScript.
This fucker is everywhere and I love it.

Yukihiro "Matz" Matsumoto: Matsumoto san is the creator of the Ruby programming language. Not only am I a die hard fan of Ruby, but of the core philosophies that the man keeps as the core of his language design: Make the developer happy, principle of least surprise. Also I follow: minswan which is a term made by the Ruby community that states Mats is nice so we are nice. <---- because being cool to others is better than being a passive aggressive cunt.

Steve Wozniak: I feel as if the man does not get enough recognition...the man designed the Apple || computer which (regardless of how much most of y'all bitch and whine) paved the way for modern micro computers. Dude is also accredited with designing one of the first programmable universal remotes(which momma said was shitty) but he did none the less.

Alan Kay: Developed Smalltalk and the original OOP way of doing things. Smalltalk as a concept is really fucking interesting. If you guys ever get the chance, play with Pharo, which is a modern Smalltalk. The thing is really interesting and the overall idea of Smalltalk can be grasped in very little time. It sucks because the software scales beautifully in terms of project building, the idea of hoisting a program as its own runtime environment and ide by preserving state through images is just mind blowing to me. Makes file based programs feel....well....quaint.

Those are some of the biggest dudes for me. I know that the list is large, but I wanted to give credit to the people that inspired me the most. Honorary mention goes to other language creators and engineers of course, but it would be way too large to list!

Just my luck.

I was supposed to sign a new contract last week and get paid 2x more than now + get a lot of benefits. The day before, obviously, they just HAD to stop signing contracts with new people because of COVID.

Also my engineers exam is postponed indefinitely. They are thinking about making it online, which would be awesome, but again - it was supposed to be last week. A lot of stress and time wasted.

I know, those problems are really miniscule when compared to other, but it still is annoying as fuck.

Thank for listening to my Ted talk.

Hmm...recently I've seen an increase in the idea of raising security awareness at a user level...but really now , it gets me thinking , why not raise security awareness at a coding level ? Just having one guy do encryption and encoding most certainly isn't enough for an app to be considered secure . In this day an age where most apps are web based and even open source some of them , I think that first of all it should be our duty to protect the customer/consumer rather than make him protect himself . Most of everyone knows how to get user input from the UI but how many out here actually think that the normal dummy user might actually type unintentional malicious code which would break the app or give him access to something he shouldn't be allowed into ? I've seen very few developers/software architects/engineers actually take the blame for insecure code . I've seen people build apps starting on an unacceptable idea security wise and then in the end thinking of patching in filters , encryptions , encodings , tokens and days before release realise that their app is half broken because they didn't start the whole project in a more secure way for the user .

Just my two cents...we as devs should be more aware of coding in a way that makes apps more secure from and for the user rather than saying that we had some epic mythical hackers pull all the user tables that also contained unhashed unencrypted passwords by using magix . It certainly isn't magic , it's just our bad coding that lets outside code interact with our own code .

Depressed since yesterday.

Updated all our clients Dialers. Stellar performance. Suddenly one of 15 can’t hang up three way calls.

It’s one of our biggest clients. And they just started. We upgraded the dialers so the answering machine detection would improve for them and it did, along with vast performance upgrades as well. Suddenly, this issue.

2 days in they pull the plug until we fix it. The issue is sporadic and we cannot reproduce. No one else is having the issue. I can’t even debug it properly as it’s a third party dialer with no customizations on it. I found out where the error is, but no idea the workflow they got it to happen with or why. It’s so frustrating. It happens using the dialer native interface, and our integration via api calls. The channel doesn’t get sent to the command for some random reason, and only sometimes.

So even if it’s fixed they don’t trust the system. Now they are losing the full integration we have with the crm and dialer and it’s going to be a mess of data for them. All because of this one issue. They love the CRM though...

If they had just stayed on one more day I’m sure I could have found it. Now I have to play forensic scientist and look through old data, without being able to see the client code that was causing the issue.

Just threw some cash down to be able to talk to the dialer engineers and hopefully see what’s up. What a nightmare. And I have so many other projects for the platform due so soon...

Sigh. Super depressing.

A group of ten top software engineers is sent to a class for aspiring managers.

The teacher walks in and asks this question:"You work for a software company which develops avionics (software that controls the instruments of an airplane).

One day you are taking a business trip. As you get on the plane you see a plaque that says this plane is using a beta of the software your team developed. Who would get off?"Nine developers raised their hands.

The teacher looked at the tenth and asked, "Why would you stay on?

"The tenth said, "if my team wrote the software, the plane would not get off the ground

Positive story ahead.

Had to try and make a new system on my own in a company with no tech staff. I was scared shitless of the responsibility. About a year later we got 2 new devs and people are somehow paying for our very flawed and incomplete mvp.
It's fulfilling and fun. Taking something from zero and suddenly having an actual application with customers.

The other 2 engineers are fun and we talk shit while coding and teaching each other. We also study new tech every day to keep getting better.

I'm even getting some stocks soon.

Long road ahead but honestly, life's good.

This isn't a funny rant or story. It's one of becoming increasingly unsure of the career choices I've made the path they've led me down. And it's written with terrible punctuation and grammar, because it's a cathartic post. I swear I'm a better writer than this.

The highlights:
- I left a low-paying incredibly stable job with room to grow (think specialized office worker at a uni) to become a QA tester at a AAA game studio, after growing bored with the job and letting my productivity and sometimes even attendance slip
- I left AAA studio after having been promoted through the ranks to leading an embedded test tools development team where we automated testing the game (we got to create bots, basically!) and the database, and building some of the most requested tools internally to the company; but we were paid as if we were QA testers, not engineers, and were told that wouldn't change; rather than move over or up, I moved out to a better paying, less fabulous web and tools development job for a no-name company
- No-name company offered one or two days remote, was salaried, and close to home. CTO was a fan of long lunches and Quake 3 Arena 1-2 hours at the end of every day. CTO position was removed, I got a lot of his responsibilities, none of his pay, and started freelancing to learn new skills rather than deal with the CFO being my boss.
- Went to work as a freelancer for an email marketing SaaS provider my previous job had used. Made loads of money, dealt with an old, crappy code base, an old, cranky senior dev, and an owner who ran around like the world was on fire 24/7; but I worked without pants, bought a car, a house, had a kid, etc;

Now during ALL of this, I was teaching game dev as an adjunct at my former uni. This past fall, I went full time as a professor in game dev. I took a huge pay cut, but got a steady schedule (semester to semester anyway) and great benefits. I for once chose what I thought was the job I wanted over more money and something that was just "different". And honestly, I've regretted it so much. My peer / diagonally above me coworker feels untrustworthy half the time and teaches the majority of the programming courses when he's a designer and I've been the game programming professor for 8 years (I also teach non-game programming courses, but those just got folded into the games program...); I hate full-time uni politics; I'm struggling with money for my family; and I am in the car all the time it feels like. I could probably go back to my last job, which had some benefits, but nowhere near as good; my wife doesn't want me back to working in the house all the time because that was a struggle unto itself once we had a kid (for all of us, in different ways); and I have now less than 24 hours to tell my university I want to not pursue longer term contracts for full-time and go back to adjunct next Fall (or walk away entirely), or risk burning a bridge (we are reviewing applicants for next year tomorrow, including my own) by bailing out mid-application process.

I'm not sure I'm asking for advice. I'm really just ranting, I guess. Some people I know would kill to have the opportunities I have. I just feel like each job choice led me further away from a job I liked, towards more money, which was a tradeoff that worked out mostly, but now I feel like I don't have either, and I'm trapped due to healthcare and 401k and such. Sure, I like working more with my students and have been able to really support them in their endeavors this semester, but... that's their lives. Not mine. The wife thinks I should stay at the university and we'll figure out money eventually (we are literally sinking into debt, it's not going well at all), while most people think I should leave, make money, and figure out the happiness factor once my finances are back on track and the kid is old enough to be in school.

And I have less than 24 hours it feels like to make a momentous decision.

Yay. Thanks for reading :)

Hey this is the first time i post here.

I just started working part-time for this company last week. What i have to do is to change some windows from Win32 to WPF. As i was reading the legacy code i just had to sigh man. They have like 100 projects in a single solution, from C++ to C#, everything acctached to each other, with almost NO comments or docs. Wtf man? I don't know how it actually works in the industry (this is my first dev job) but when you write fucking 20 classes with each one contains bunch of attributes, methods, properties, you can't just leave all the code's semantics in their names. And by the way the app is so fucking ugly i bet they have appointed part-time developers as UX engineers... Even i have little knowledge about UX/UI, i just can't bear with this kind of ugly and confusing and unintuitive production with a cost of a good photo editting software.

Ok there may be much more to rant in the future but let me try through this and tell you more. Have a good day. :)

Tomorrow's my first day as an SRE intern.. wish me luck fellow devs and engineers :)

More DevOps rants coming in the future with my best mate @tahnik who is also starting his software engineering internship on the same day coincidentally in a different company

Happy engineers day friends

Do ++ all engineers.

We support a system we inherited from another company, it’s an online document store for technical specifications of electronic devices used by loads of people.

This thing is the biggest pile of shite I’ve ever seen, it wasn’t written by developers but rather by civil engineers who could write vb...so needless to say it’s classic asp running on iis, but it’s not only written in vbscript oh god no, some of it is vb other parts is jscript (Microsoft’s janky old JavaScript implementation) and the rest is php.

When we first inherited it we spent the best part of 2 months fixing security vulnerabilities before we were willing to put it near the internet - to this day I remain convinced the only reason it was never hacked is that everything scanning it thought it was a honeypot.

We’ve told the client that this thing needs put out of its misery but they insist on keeping it going. Whenever anything goes wrong it falls to me and it ends up taking me days to work out what’s happening with it. So far the only way I’ve worked out how to debug it is to start doing “Response.AddHeader(‘debug’, ‘<thing>’) on the production site and looking at the header responses in the browser.
I feel dirty doing that but it works so I don’t really care at this point

FUCK I hate this thing!

I remember when this person I worked for suggested all the engineers get on a day long call with the product owner pointing out problems and the engineers fixing them on the call. It was absolute chaos when i told my team 😂

Has anyone else ever encountered such??

MySQL 5.5 end of life’d in 2010. In 2021 my company started an upgrade to 5.6. The outdated dependencies meant we needed 25 engineers for 2 months full-time to make the upgrade as invisible to users as possible. We still took about 90 minutes of downtime on cutover day. Not upgrading MySQL on time meant we paid way more in terms of engineering hours. The reason we call it debt, is because you pay interest when you don’t tKe care of it right away.

Is it okay for software engineers like us to go out to eat every day? I just don’t find the time to cook for myself. And honestly the time spent cooking would be better spent learning (judging by our hourly rate). Do you think it’s okay for devs to have such a luxurious life style (eating out is a privilege!) because our minds are so taxed on learning and creating?

I know I’ll get mixed views for this one...

So I’ll state my claim. I agree with the philosophy of uncle bob, I also feel like he is the high level language - older version of myself personality wise.. (when I learned about uncle bob I was like this guy is just like me but not low level haha).

Anyway.. I don’t agree with everything because I think he thinks or atleast I get the vibe he thinks everything can be solved by OOP, and high level languages. This is probably where Bob and I disagree. Personally I don’t touch ruby, python and java and “those” with a 10 foot pole.

Does he make valid arguments, yes, is agile the solve all solution no.. but agile ideas do come natural and respond faster the feedback loop of product development is much smaller and the managers and clients and customers can “see things” sooner than purly waterfall.. I mean agile is the natural approach of disciplined engineers....waterfall is and was developed because the market was flooded with undisciplined engineers and continues to flood, agile is great for them but only if they are skilled in what they are doing and see the bigger picture of the forest thru the trees.. which is the entire point of waterfall, to see the forest.. the end goal... now I’m not saying agile you only see a branch of a single tree of the forest.. but too often young engineers, and beginners jump on agile because it’s “trendy” or “everyone’s doing it” or whatever the fuck reason. The point is they do it but only focus on the immediate use case, needs and deliverables due next week.

What’s wrong with that?? Well an undisciplined engineer doing agile (no I’m not talking damn scrum shit and all that marketing bullshit).. pure true agile.
They will write code for the need due next week, but they won’t realize that hmm I will have the need 3 months from now for some feature that needs to connect to this, so I better design this code with that future feature in mind...

The disciplined engineer would do that. That is why waterfall exists so ideally the big picture is painted before hand.

The undisciplined engineer will then be frustrated in the future when he has to act like the cool aid man thru the hard pre mature architectural boundaries he created and now needs links or connections that are now needed.

Does moving to agile fix that hell no.. because the undisciplined engineer is still undisciplined.

One could argue the project manager or scrum secretary... (yes scrum secretary I said that right).. is suppose to organize and create and order the features with the future in mind etc...

Bullshit ..soo basically your saying the scrum kid is suppose to be the disciplined engineer to have foresight into realizing future features and making requirements and task now that cover those things? No!
1 scrum bitch focuses too much on pleasing “stake holders” especially taken literally in start ups where the non technical idiots are too involved with the engineering team and the scrum bastard tries to ass kiss and get everything organized and tasks working so the non technical person can see pretty things work.

Scrum master is a gate keeper and is not needed and actually hinders the whole process of making a undisciplined engineer into a disciplined engineer, makes the undisciplined engineer into a “forever” code grunt... filling weekly orders of story points unable to see the forest until it’s over because the forest isn’t show to the grunt only the scrum keeper knows the big picture..... this is bad this is why waterfall is needed.

Waterfall has its own problems, But that’s another story for another day..

ANYWAY... soooo where were we ....

Ahh yess....

Clean code..

Is it a good book, yes.. does uncle bobs personality show thru the book .. yes lol.
If you know uncle bob you will understand what I just did with this post lol. I had to tangent ( at least mine was related to the topic) ...

I agree with the principles of the book, I don’t agree with the extreme view point. It’s like religion there’s the modest folks and then there are the extremists. Well he’s the preacher of the cult and he’s on the extreme side.. but that doesn’t mean he’s wrong.. many things he nails... he just hits the nail thru the wall just a bit.

OOP languages are not the solution... high level languages do not solve everything.. pininciples and concepts can be used across the board and prove valuable.. just don’t hold everything up like the 10 commandments of which you cannot deviate from.. that’s the difference here I think..

Good book, just don’t take it as the Bible as a beginner, actually infact DONT read this book as a beginner. Wait a bit learn then reflect by reading this.

I work for an investment wank. Worked for a few. The classic setup - it's like something out of a museum, and they HATE engineers. You are only of value if work on the trade floor close to the money.

They treat software engineering like it's data entry. For the local roles they demand x number of years experience, but almost all roles are outsourced, and they take literally ANYONE the agency offers. Most of them can't even write a for loop. They don't know what recursion is.

If you put in a tech test, the agency cries to a PMO, who calls you a bully, and hires the clueless intern. An intern or two is great, if they have passion, but you don't want a whole department staffed by interns, especially ones who make clear they only took this job for the money. Literally takes 100 people to change a lightbulb. More meetings and bullshit than development.

The Head of Engineering worked with Cobol, can't write code, has no idea what anyone does, hates Agile, hates JIRA. Clueless, bitter, insecure dinosaur. In no position to know who to hire or what developers should be doing. Randomly deletes tickets and epics from JIRA in spite, then screams about deadlines.

Testing is the same in all 3 environments - Dev, SIT, and UAT. They have literally deployment instructions they run in all 3 - that is their "testing". The Head of Engineering doesn't believe test automation is possible.

They literally don't have architects. Literally no form of technical leadership whatsoever. Just screaming PMOs and lots of intern devs.

PMO full of lots of BAs refuses to use JIRA. Doesn't think it is its job to talk to the clients. Does nothing really except demands 2 hour phone calls every day which ALL developers and testers must attend to get shouted at. No screenshare. Just pure chaos. No system. Not Agile. Not Waterfall. Just spam the shit out of you, literally 2,000 emails a day, then scream if one task was missed.

Developers, PMO, everyone spends ALL day in Zoom. Zoom call after call. Almost no code is ever written. Whatever code is written is so bad. No design patterns. Hardcoded to death. Then when a new feature comes in that should take the day, it takes these unskilled devs 6 months, with PMO screaming like a banshee, demanding literally 12 hours days and weekends.

Everything on spreadsheets. Every JIRA ticket is copy pasted to Excel and emailed around, though Excel can do this.

The DevOps team doesn't know how to use Jenkins or GitHub.

You are not allowed to use NoSQL database because it is high risk.

My companies org is in a serious state of disrepair when it comes to project management.

Everything is tracked via conference. Each level of management (CTO, EVP, SVP, BP, S DIRECTOR, DIRECTOR, S MANAGER, MANAGER) all have a different tracking page that all say slightly different things.

To organize things there's a technical project manager who isn't just new to the team, he's new to the field. He's not technical, or experienced in project management. He's never worked within a scrum before.

He's dictating how to organize the teams scrum, and he's getting it very wrong. Decided to organize efforts in all the confluence pages by creating another one for him, again it's different.

When the work in confluence page 3/16 isn't done by a due date anybody knew about, the engineers have to hop on a call and get a Micky mouse solution out the door by the of day so upper management doesn't think the projects off the rails.

In the mean time I've taken a small group of more junior devs and shielding them. We have a side scrum that we manage and is going great, and I'm blocking the BS.

CORPORATE SUCKS. Golden handcuffs are a thing. I might set sail for greener pastures once i don't have to pay back my signing bonus if I leave.

Companies are laying workers off these days like it's nothing.

My company dismissed (just within my department) 90 out of 129 workers — that messed me up.

However, though, my team experienced just a partial effect: 2 Senior devs are needed out of 3 — mid and junior devs are going. I literally had to re-interview for my role again, since they need to keep only 2 senior engineers.

To cut the long story short, I was the first selected candidate — grateful I still have my job. But, I'm sad to see the disruption.

I understand that at the end of the day, it's all business, but mehnnn ...

Is anyone going through the same thing here?
How y'all coping?

I learned C with a K&R copy a friend gave me years ago. Now at University we in CompSci get taught in Python the first year and Java next while the engineers start with C and (I'm guessing) move on to assembly later on.

This friend comes to me all worried because he has to submit the next day a working Reversi game for the console written in C. Turns out the game was divided among two labs and he failed to submit the first one.

The guy is smart but once a week or so, when we met to smoke a joint and relax with some other friends, he was always talking about how he would prefer something like law but that would be bad business back in Egypt.

Back to the game, I get completely into it. First hour checking all the instructions he was given, then reviewing the code he wrote and copied from Internet. We decide start from scratch since he doesn't really get what the code he copied do. It took us 10 hours only stopping to eat but we get all the specifications of both labs perfectly.

A week after that he comes to me: "my TA said your code is the ugliest shit he's ever seen but he gave me a perfect score because it passed all the tests". I'm getting better (the courses I'm taking help me a lot) but what really made me happy is that he solved the next lab by himself (Reversi wasn't the first time I helped him, only the first time he was absolutely lost). Now he actually gets excited about coding and even felt confident for his programming final.

No more talking about being a lawyer after those 10 hours, totally worth it.

go fuck yourself with your fucking communities. i went into computing because i like being left alone. who are all those fucking freaks building their communities? this is capitalism mother fuckers, everybody in the world agreed on it, on each person being an independent individual doing their job to the best possible standard, instead these low-skill low-iq oversocialised sheeple started conglomerate into communities and brainwash everybody that this is what it is about. get stuffed alright. all my life i've been introverted, just leave me alone to write code alright? take my library i don't mind i'll take yours no strings attached, just push the code and forget about it. but no, all these degenerate morons without CS degrees have occupied our safe space, pushed us out of it and just can't get enough of using the buzzword "community-driven" "volunteers" volunteer my ass assholes you can't even make software nobody in real industry needs you because you have no skill at all you learn a bit of js which is any 14-15 yo can do and now think you're some kind of prodigies, unsung heros of humanity who selflessly bring the progress. nothing can be further from the truth - because of you we don't have real software, we don't have investment we don't get no respect everybody walks all over software engineers treating us like shit, there's an entire generation of indoctrinated parasitic scum that believes that software tools is grown for them on trees by some development teams that their are entitled to automatically, because some corporation will eventually support those big projects - yeah does it really happen though - look at svelte, the guy is getting 50k a year when he should be earning at least 500k if he had balls to start a real businesses, but no we are all fucking prostitutes, just slaving away for the army of people we never see. are you out of your mind. this shit should be fucking illegal alright it's modern day slavery innit bruh, if a company wants to pay their engineers to work on open source this is fine, i love open source like java or google closure compiler, but it's real software made by real engineers, but who are all these community freaks who can't spend a 10 seconds on stage in their shitty bogus conferences without ringing the "community" buzzer? you're not my community i fucking hate your guts you're all such dumb womenless imbeciles who justify their lack of social skill by telling themselves that you're doing good by doing open source in your free time - mate nobody gives a shit alrite? don't you want money sex power? you've destroyed everything that was good about good olde open source when it was actually fun, today young people are coerced into slavery at industrial scale, it's literally impossible to make a buck from software as indie unless you build something really big and good, and you can't build anything big without investment and who invests in software nowadays? all the ai "entrepreneurs" are getting fucking golden rained with cash while i have to ask for a 5$ donation? what the actual fuck? who sanctions this? the entire industry is in one collective psychotic delusion, spurred by microsoft who use this army of useful idiots to eliminate all hounour dignity of the profession, drive the abundance and bring about poverty of mind, character, as well as wallet as the natural state of things. fucking amatures of course you love your shitty little communities because you can't achieve anything on your own. you literally have no personality, just one homogenous blob of dumb degenerates who think and act all the same. there used to be a tool called adobe flash builder, i could just buy it, then open and make a web app, all from start to finish in one program, using tutorials of adobe experts on youtube, sure it might have had its pitfals but it was a product - today there's literally no fucking product to make websites. do you people get it? i can't buy a tool that i need to do my job and have to insult myself by downloading some shitty scripts from some shitty unemployed devs and hope my computer doesn't blow up in my face in the process because some freak went off his nut and uploaded some dodgy ass exploit on npm in his package. i really don't like. it's not supposed to be like that. good for me i build by own front/back end. this "community" insanity is just a symptom of industrial degeneration, they try to sell it to us like it's the "bright" communist future but things never been worst, i can't give a shit about functional programming alright i just need to get my job done mate leave me alone you add functional because you don't know how to solve the problem properly, e.g., again adobe flex had mxml where elements had ids and i could just program to id, it was alright but today all this unqualified morons filled the whole space after flash blew up and adobe execs axed flash builder instead of adapting it to js runtime, it was a crime against humanity that set us back to 1000s

## building my own router

I hoped things would go more smoothly :)
Anyway, my new miniPC easily accepted CentOS 8 - no fuss here. And I've got to say - I love CentOS8 so far! Shell has amazing nifty tricks, UI (gnome3) is also snappy, video/audio/ethernet,.. everything works.

What I did NOT expect is hardware being off. Well okay, the price was low - it was obvious smth is not right. But still.. I decided to build my own router so that I could swap wifi card whenever I want. So that I could run my own network services in there. Turns out - the card swapping is not as easy as one might think.

I got the AX200 WiFi6 card for that very purpose. But once plugged in the OS can only see it's bluetooth module. Weird... What's even weirder is that even though the card is PCIe, the OS uses btusb module to talk to that device. What? USB?? emm.. What??

And there it is. After opening it up again I noticed that the mPCIe area is marked with a label: "USB WIFI / WWAN". USB? Does that mean this PCIe slot is wired into the USB bus? Not impossible I guess.

Googling for a "pcie wifi over usb" or smth like that brought me to one reddit (I think?) where someone wanted to build a DIY wifi mPCIe -> USB adapter and someone else adviced hime that (for some reason) at best he could only get bluetooth working (hey! just like me!). It's got to do smth with pcie channels and USB being too weak to handle all that load, or smth.. IDK, I'm not a HW guy.

Well that sucks then! I have a mPCIe slot that does not work as a PCIe. Shit! So I guess the best I could do is to plug back in the same wifi card that came with the device. It smells like 2003 - supports only g protocol. Fine, let's try that. Maybe I'll find a way to work around this mPCIe limitation later on (USB adapter or smth... except there are no USB WIFI6 dongles yet :( ). So I plug it back in and start turning it into a router. Disable NetworkManager, configure static NCs' settings, install dhcpd, hostapd, bind and others. Looks like all is done! Now it's time to start it all. systemctl start hostapd --> FAILED. wtf? journalctl says it could not initialize a driver. umm okay? Why? Forums say I should airodump-ng check and kill whatever's using that device. Fine. airodumo reveals avahi and wpa_suppl are still using it. kill, kill, GOTTA KILL 'EM ALL!! Starting hostapd again -- same shit... wtf?

iw list

My gawd... That shitty network card does not even support AP mode :( I mean.. My USB wifi dongle for 2€ supports 2x more modes, is faster, has better range and is easier to work with than this old tart!

Yeah. That was an interesting day. When enfironment engineers break my testing environments at work I'm glad I have where to spend my time now.

BTW any ideas how to bypass this mPCIe nonsense? Come on, there are USB GPUs out there.. Why can't they make a USB (or dual-USB if they really need to) mPCIe adapter?

I don't care about market cap. Stick your hype-driven business practices up your ass. Infinite growth doesn't exist. I won't read your fucking books and attend your fucking bootcamps and MBAs. You don't have a business model. Selling data is not a business model. Fuck your quick-flip venture capital schemes, and especially fuck your “ethics”.

I will be the first alt-tech CEO. I only care about revenue. The real money, not capitalization bubble vaporware. You don't need a huge fleet of engineers if you're smart about your technology, know how to do architecture, and you're not a feature creep. You don't need venture capital if you don't need a huge fleet of engineers. You don't need to sell data if you don't need venture capital. See? See the pattern here?

My experience allows me to build products on entirely my own. I am fully aware of the limitations of being alone, and they only inspire lean thinking and great architectural decisions. If you know throwing capacity at a problem is not an option, you start thinking differently. And if you don't need to hire anyone, it is very easy to turn a profit and make it sustainable.

If you don't follow the path of tech vaporware, you won't have the problems of tech vaporware, namely distrust of your user base, shitty updates that break everything, and of course “oops, they raised capital, time to leave before things go south”.

A friend of mine went the path I'm talking about, developed a product over the course of four years all alone, reached $10k MRR and sold for $0.8M. But I won't sell. I only care about revenue. If I get to $10k MRR, I will most likely stop doing new features and focus on fixing all the bugs there are and improving performance. This and security patches. Maybe an occasional facelift. That's it. Some products are valued because they don't change, like Sublime Text. The utility tool you can rely on. This is my scheme, this is what I want to do in life. A best-kept secret.

Imagine 100 million users that hate my product but use it because there are no alternatives, 100 people in data enrichment department alone, a billion dollars of evaluation (without being profitable), 10 million twitter followers, and ten VC firms telling me what to do and what data to sell.

Fuck that. I'd rather have one thousand loyal customers and $10k MRR. I'm different, some call it a mental illness, but the bottom line is, my goals are beyond their understanding. They call me crazy. I won't say it was never about the money, of course it was, but inflating your evaluation is not “money”. But the only thing they have is their terrible hustle culture lives and some VC street wisdom, meanwhile I HAVE products, it is on record on my PH. I have POTDs, I have a fucking Golden Kitty nomination on health and fitness for a product I made in one day. Fuck you.

The year was 2006. During the first half of my career, I use to work in the NOC. This was before I made my transition to software engineer. I worked on the third shift for a bank services company. The company was on a down turn. Just years earlier they just went public, and secured a deal with a huge well known bank. Eventually they entered a really bad contract with the bank and was put into a deal they couldn't deliver on. The partnership collapse and their stock plummeted. The CEO was dismissed, and a new CEO came in who wanted to "clean things up".

Anyway I entered the company about a year after this whole thing went down. The NOC was a good stepping stone for my career. They let me work as many hours as I liked. And I took advantage of it, clocking in 80 hours a week on average. They gave me the nick name "Iron Man".

Things started to turn around for the company when we were able to secure a support contract with a huge bank in the Alabama area. As the NOC we were told to handle the migration and facilitate the onboarding.

The onboarding was a mess with terrible instructions that didn't work. A bunch of software packages that crashed. And the network engineers were tips off, as they tunnel between our network and the banks was too narrow, creating an unstable connection between us and them. Oh, and there were all sorts of database corruption issues.

There was also another bank that was using an old version of our software. The sells team had been trying to get them off our old software for over a year. They refuse to move. This bank was the last one using this version, and our organization wanted to completely cut support.

One of the issue we would have is that they had an overnight batch job that had an ETA to be done by 7 AM. The job would often get stuck because this version of the software didn't know how to fail when it was caught in an undesired state. So the job hung, and since the job didn't have logging, no one could tell if it failed unless the logs stopped moving for an hour. It was a heavily manually process that was annoying to deal with. So we would kill the JVM to "speed" the job up. One day I killed the JVM but the job was still late. They told me that they appreciated the effort, but that my job was only to report the problem and not fix it.

This got me caught up in a major scandal. Basically they wanted the job to always have issues everyday. Since this was critical for them, all we needed to do was keep reporting it, and then eventually this would cause the client to have to upgrade to our new software. It was our sales team trying to play dirty. It immediately made me a menace in the company.

For the next 6 months I was constantly harassed and bullied by management. My work was nitpicked. They asked me to come into work nearly everyday, and there was a point I worked 7 days with no off days. They were trying to run me so dry that I would quit. But I never did.

On my last day at the company, I was on a critical call with a customer, and my supervisor was also on the line. My supervisor made a request that made no sense, and was impossible. I told her it wasn't possible. She then scalded me on the call in front of customers. She said "I'm your supervisor, you're just a NOC technician, you do what I say and don't talk back". It was embarrassing to be reprimanded on a call with customers. I never quite recovered from that. I could fill myself steaming with anger. It was one of the first times in my adult life that I felt I really wanted to be violent towards someone. It was such a negative feeling I quit that day at the end of my shift with no job lined up.

I walked away from the job feeling very uncertain about my future, but VERY relieved. I paid the price, basically unable to find a job until a year and a half later. And even was forced to move back in with my mother. After I left, the company still gave my a severance. Probably because of the supervisor's unprofessional conduct in front of customers, and the company probably needed to save face. The 2008 crash kept me out of work until 2009. It did give me time to work on myself, and I swore to never let a job stress me out to that degree. That job was also my last NOC job and the last job where did shift work. My next few jobs was Application Support and I eventually moved into development full time, which is what I always wanted to do.

Anyway sorry if it's a bit long, but that's my burnout story.

This is my first ever post on DevRant, and it will be more of a question: Is the tech sector more toxic than others?

I've been working for my entire adult life in tech, supporting tech companies of basically any scale. I've always worked in engineering teams, building the core software/product of the company. After years of passion and working hard, I believe I gained some skills in what I do.

However, every so often I reach a point where I feel burned out by all the chaos going on around me. I work as an "expert" in engineering and frequently I get the feeling that I'm not being listened to. Any feedback I give seems to be disregarded.

On top of that, I've met many people with a rather aggressive/abusive communication style. Engineers who truly believe they're far above and beyond everyone else, but with little to back that up. Talking shit about their predecessors, trashing junior engineers,...

I've seen behavior toward women that is grossly inappropriate. I've seen female coworkers cry more than once because they don't feel heard. I've seen coworkers being criticized for personal life choices they made.

In almost every company I've worked at, there was at least one engineer who was so stubborn that it became nearly impossible to work with. Just shutting people up, forcing the rest to follow their plan, and failing to provide any form of accountability when results don't pay off.

Here's the thing. I love developing products. I care about the people who want to use them. I really try to be nice to the people I work with. I started working in this sector because I really wanted to make a difference. However, all of that melts as snow on a sunny day, when I experience toxic behavior.

I am wondering if this is the same in every sector or if these problems are specific to working in tech. Is it maybe because tech is male-dominated and we've lost touch?

Every so often, when I lose my job or leave by burning out, I wonder... Is the grass greener on the other side? Would I be happier choosing another career?

Today is the birthday of Sir M. Visvesvaraya, one of the greatest engineers of all time. In India, we celebrate his birthday as Engineers' day. Happy Engineers' day to all engineers here!

Had my first day as a Software Engineer in one of the most trending software companies. Absolutely crazy how organized a company can be. There are so many talented software engineers I‘m a little bit afraid of the expectations they‘re having. Wish me luck, I‘m just a little software dev who graduated 3 months ago :(

What if there was like a 1-2 day workshop that helped recruiters be more technically fluent? Like the basics of software development (not programming, but concepts and what engineers really do)?

I just rebooted my server by accident because I wanted to play Space Engineers.

Long story short, dual booting. Needed to boot into windows. Typed reboot into my terminal. My terminal was not local. When am I finally getting around to set up my terminal color as red when it is connected to another host?

But two things are good here. This was my own server.. Well, bunch of stuff is running on it, including for my bachelor's thesis. But if that was a server of my company, that would have been worse.

Second thing, my systems are fault tolerant. I reboot once per week at the latest and for systems with fail overs once per day. I know they are coming back up. I don't worry. My Gitlab will be back in 5 minutes at the latest. I am going to reboot and play Space Engineers now.

Reboot your servers guys. Only way to make sure they'll survive reboots!

The conversations that come across my DevOps desk on a monthly basis.... These have come into my care via Slack, Email, Jira Tickets, PagerDuty alerts, text messages, GitHub PR Reviews, and phone calls. I spend most of my day just trying to log the work I'm being asked to do.

From Random People:
* Employee <A> and Contractor <B> are starting today. Please provision all 19 of their required accounts.
* Oh, they actually started yesterday, please hurry on this request.

From Engineers:
* The database is failing. Why?
* The read-only replica isn't accepting writes. Can you fix this?
* We have this new project we're starting and we need you to set up continuous integration, deployment, write our unit tests, define an integration test strategy, tell us how to mock every call to everything. We'll need several thousand dollars in AWS resources that we've barely defined. Can you define what AWS resources we need?
* We didn't like your definition of AWS resources, so we came up with our own. We're also going to need you to rearchitect the networking to support our single typescript API.
* The VPN is down and nobody can do any work because you locked us all out of connecting directly over SSH from home. Please unblock my home IP.
* Oh, looks like my VPN password expired. How do I reset my VPN password?
* My GitHub account doesn't have access to this repo. Please make my PR for me.
* Can you tell me how to run this app's test suite?
* CI system failed a build. Why?
* App doesn't send logs to the logging platform. Please tell me why.
* How do I add logging statements to my app?
* Why would I need a logging library, can't you just understand why my app doesn't need to waste my time with logs?

From Various 3rd party vendors:
* <X> application changed their license terms. How much do you really want to pay us now?

From Management:
* <X> left the company, and he was working on these tasks that seem closely related to your work. Here are the 3 GitHub Repos you now own.
* Why is our AWS bill so high? I need you to lower our bill by tomorrow. Preferably by 10k-20k monthly. Thanks.
* Please send this month's plan for DevOps work.
* Please don't do anything on your plan.
* Here's your actual new plan for the month.
* Please also do these 10 interruptions-which-became-epic-projects

From AWS:
* Dear AWS Admin, 17 instances need to be rebooted. Please do so by tomorrow.
* Dear AWS Admin, 3 user accounts saw suspicious activity. Please confirm these were actually you.
* Dear AWS Admin, you need to relaunch every one of your instances into a new VPC within the next year.
* Dear AWS Admin, Your app was suspiciously accessing XYZ, which is a violation of our terms of service. You have 24 hours to address this before we delete your AWS account.

Finally, From Management:
* Please provide management with updates, nobody knows what you do.

From me:
Please pay me more. Please give me a team to assist so I'm not a team of one. Also, my wife is asking me to look for a new job, and she's not wrong. Just saying.

The near future is in IOT and device programming...
In ten years most of us will have some kind of central control and more and more stuff connected to IOT, security will be even a bigger problem with all the Firmware bugs and 0-day exploits, and In 10 years IOT programmers will be like today's plumbers... You need one to make a custom build and you must pay an excessive hour salary.
My country is already getting Ready, I'm starting next month a 1-year course on automation and electronics programming paid by the government.

On the other hand, most users will use fewer computers and more tablets and phones, meaning jobs in the backend and device apps programming and less in general computer programs for the general public.

Programmers jobs will increase as general jobs decrease, as many jobs will be replaced by machines, but such machines still need to be programmed, meaning trading 10 low-level jobs for 1 or 2 programming jobs.

Unlike most job areas, self-tough and Bootcamp programmers will have a chance for a job, as experience and knowledge will be more important than a "canudo" (Portuguese expression for the paper you get at the end of a university course). And we will see an increase of Programmer jobs class, with lower paid jobs for less experienced and more well-paid jobs for engineers.

In 10 years the market will be flooded with programmers and computer engineers, as many countries are investing in computer classes in the first years of the kids, So most kids will know at least one programming language at the end of their school and more about computers than most people these days.

Does anyone think tech recruiters are failed used car salesmen?

Bad experiences this week

One reached out to me on clearance jobs to apply for a job that I applied for, interviewed and was turned down for because of course they do not know Javascript is not Java and they were looking for a Java developer. She didn’t remember and then never responded. Out of spite I replied all to the last email that company sent me but of course no one responded.

This person who says that she is a recruiter for GOOGLE does not know the difference from UX designer and UX developer.

“ UX design still involves coding... idk where you got information that UX designers don't code but they absolutely do. UX designers are simply front end software engineers that work on refining the user experience of a particular program app or website.”

I don’t know because I used to be a fucking UX developer and used to work with UX designers??? Who didn’t code because figuring out what humans what is tough enough on it’s own. UI designers may know html/css but that is it.

I know we are going into a recession and I need to start being nice to these dumb recruiters because I may need them one day.

I live in an apartment building and ordered a DVD from Amazon, 2-day delivery on Friday. So was supposed to arrive yesterday but got a "Delivery was Attempted". I said ok probably the postal service being lazy. Some days they just don't deliver even though they should...

They tried again today but I get notified of the same problem. Now I'm pissed so finally contact Amazon. Turns out they didn't use USPS or any of the big shippers.

I'm going WTF... isn't it common sense... all these rocket science engineers and they can't add a simple if?

if(address.HasApartmentNumber) shippers.Select( x => x.CanAccessApartmentBuildings)

At some arbitrary future point, when things progress further into the realm of unreasonable demands from software engineers as a "regular day at the office", a huge inquiry into the working conditions and hours of devs will take place, and a major rethink into how software projects are handled as a whole, because the current methodologies, mixed with unshifting deadlines, clients and other worldly bullshit is unsustainable given the current industry climate.

So I've learned how to code a little over 2 years ago. I have been at my current job as a full stack developer for just less than 2 years. For my job I work with multiple fortune 500 companies and it is unbelievable the incompetence that almost all the devs that I work with have. I have only been doing this for 2 years and some of the devs I work with will spend months on a ticket that I can do in a few hours. At times I think they just have it figured and do very little work and just chill most of the time and get paid 6 figures to do it.
I just don't understand how these guys have all this experience and they are still bad engineers. They just don't know how to engineer properly. It's so frustrating.
Maybe it's just the people I work with but I have seen on the inside of a lot large corporations and it's terrifying.
Here's to one day opening the doors of my own company and not allowing incompetence to come through the door

Wishing Happy Engineers day to all those idiotic-not-so-good-engineers working at Microsoft. Windows 10 is still the biggest horse-shit you'll ever see for an operating system.

Into a bunch of open source hogging meat heads because no one likes paying for things their own peers toil days and nights creating and creating more under documented over expensive licensed stuff (because agile) while throwing buzzwords to clients just make business while simultaneously choking the life out of underpaid overworked devs and engineers with the skill of running away from responsibility trying to save their own skin with the inept ability to look like a hero/King at the end of the day with a single mail sent with psychic communication or the lack thereof with people who are slogging their asses off to fix a problem created to the vulnerabilities and bugs introduced due to the impatience of the same moron who couldn't afford to give his employees/subordinates more time to figure out an elegant solution to a non existent problem created in the confusion of improperly documenting unnecessary requirements of an ignorant or unknowing client who is way too eager to process way too much load with way too less resources all the while whining about lack of features theyre not gonna use.

Day 8. My suffering with no internet connection... has finally come to an end. I had to call the internet providers from outside of my city (capital) so they can come here and fix the internet. They came within 30 mins and fixed this bullshit in 2 minutes, while the engineers and electricians in my city failed to do it for over 8 days. This is astonishingly mindbending to me

In the city where i live everyone seems to be extremely dumb slave and incompetent to do their jobs while people living in the capital city get shit done asap

Need a good doctor that can actually fucking heal you? Go to capital

Need a good doctor that actually knows how to heal your fucking dog? Go to capital

Want to earn more money? Go to capital

Need an electrician who actually knows how to fix the electrical problem? Call the capital city

Need software engineer who actually fucking knows their shit? Go to capital

Need your dick sucked right? Go to capital

Almost everything seems to be done right and fast by people from outside of my fucking city. Of course there are plenty of shit even they cant do. But people in my city cant do ANYTHING right

Im so frustrated and annoyed. Tired of all the shit. Too much shit happening in my life rn. Life gangfking me from All fking directions

To all my Machine Learning engineers, Ive been doing Frontend development for 6 years and I'm done. Wanting to get into machine learning because I've always loved data.

1. What is your day to day like?
2. Any advice for my learning journey?

Thank you🙏

unrealistic dream :

in my 40s, being cto of a market leading product in its v10 stage, whose v1 i created from scratch. me doing nothing except creating the best remote work hustler culture for the company .

i will be making both : the topmost and bottomost engineers/managers give ppts and talks of product that they created, ll system and hl system designs and the decisions that went into it

i also want some powerful management/ ceos as friends, that drive our boat to greater heights and generate tremendous revenue+ fundings + profits

----

realistic dream :

to keep being SE1 (or at worst SE2/tech lead) in a company, do 4-5 hr non impactful work per day and earn 3x the inflation as am doing now. plus somehow get a lottery or something once in a lifetime , that is worth 100x my current income so that i could build a home and 2 cars and a children fund

dev is not a great thing to be dreamt about, but it certainly paves way for a happier and healthier lifestyle if done right

I don't think I wanna be a dev anymore

Just a year ago, I was doing many side projects for fun, aching for proper coding tasks at work.

Now, I got a senior title but I don't want to do ANYTHING, I don't want to learn this new service or learn how to develop new stuff, I've lost all desire to learn something new. I just want a simple af simple low needs job, but also want good pay XD I know, it's stupid, but I really don't care what tech I use or how exciting the product is, I just want a simple repetitive job with little stress and deadlines and good pay

How do you motivate yourselves to get through the day and do your tasks? Honestly every PR review I'm shocked other engineers care so much about the code, they're obv right, I just wonder where that desire to maintain good coding practices comes from

So, the story starts with me getting a job. Full-time job for the first time in my 21 years old life. After short conversation about how amazing this company is, after countless lies and stood questions they decided to hire me. I had to get come on Monday a week later with everything prepared.

So of course I did that and got to my workplace on designated time. Turned out nobody was expecting me, nothing was prepared for a new programmer and everyone seemed angry at me for no apparent reason.

After long talk with my new boss I got some less than 100$ pc with CPU that couldn't handle virtualization and expected me to work on software that needed extensive use of virtual machine.

PC is of course filled with all kinds of spying software that uses most of the resources. IT teams only job is to check if programmers are working their assess off for at least 8 hours a day.

I've filled a ticket about granting me access to Debian machine on the mainframe so I could work. No response for two weeks. I've lost hope already.

I have to work on open space with more than 30 engineers. Screams, phone calls, alarms, all at once, all the time. My colleagues seem to not care and I can't understand how.

I was tasked with rewriting major application because old developer did some half assed piece of burning shit. It took him more than one year, I'm finishing it in less than two weeks.

Of course nobody except for me is preparing any kinds of documentation. I had to reverse-engineer whole API for alarm system.

Salary is less than a junior programmer should earn.

But I'm stuck here for at least a year because nobody's here wants a guy whose only experience is as a freelancer.

I was ten years old. At this point, despite being in my early 20's, I've officially been programming more than half of my life. From the first moment I knew that this was possible, that we, as software engineers, can do what we do... I've been quite literally obsessed with the idea.

I don't like to give other people credit for the events in my own life, but there is one thing that, more than anything else at the time that lead me down the path of computer science, directly lead me to where I'm at today. If you're at all interested in film and cinema (not to mention programming) then you've undoubtedly heard of The Social Network, directed by David Fincher. Amazing film, I'd recommend it to anyone based off of the film alone, but for me that movie holds a special place in my heart.

My mom took me to see it that movie in theaters when it came out, I would not stop bugging her to take me, there was just something about the founding of Facebook that... Sparked my young imagination. I swear to you that I didn't blink for the entire time I was in the theater watching it. It blew my mind, not only that you could do that kind of stuff with computers, but that you could actually make a lot of money working with computers as well... Ten year old me had different priorities in regards to programming 😂 Starting the moment I got home from the theater, I dedicated my life to learning everything I could about computers. Originally my goal was to, shock of all shocks, create a social networking site for me and my friends to use. I still like to brag about it to this day, but that project eventually became my groups final project in our computer class in Middle School. It was funny, middle school computer class, I had already been programming a few years by that point and was rather proficient in PHP. There were kids submitting literal spreadsheets in Excel as their final project, a few static HTML pages, that sorta jazz. My group and I submitted a full fledged twitter clone, with complete functionality. We got 100% on the project 😂😂

My reasons and interests have changed over the years. For example, I'm not particularly interested in creating a social media application these days, and I don't program because I think it'll make me rich one day (though the hopes always there) but the one thing that hasn't changed since that night I sat enraptured in the beautiful cinematography of David Fincher and facepaced dialogue of Aaron Sorkin, is the complete and total fascination with computers and technology. For that reason The Social Network will forever be my favorite movie.

I like watching the videos on the qt website where engineers with foreign accents describe their love of the framework it's kind of amusing

It's kind of a massive framework it takes up decent disk space !

Maybe Ill win the battle and finally eb able to keep photos of myself much diminished as these people apparently try to hide how hot I was in my actual 40s

Certainly had a slimmer waistline lol
Now I got that lower belly gut I'm working off slowly yay

Bottle of wine yesterday prolly didn't help but the 11 miles of walking today and the workout prolly balanced that out.

Need to get to running some more
Did that the other day doing sprint walks and poured goddamn sweat !

I'm about to give a presentation to IBM engineers on a subject I don't really know much about and for which I haven't practice
It's going to be a nice day

==rant
Cleaning up others mess is not a responsibility stated in the job descriptions of software engineers but they end up doing it every other day!

Happy Engineers' Day to all engineers here!

Sir M. Visvesvaraya, one of the greatest engineers of all time, was born this day in 1861. His contributions to the society through engineering is priceless. We celebrate his birthday as engineers' day here in India.

People around you (especially non-engineers) coming over just to know whether you saw their instant message ping / email to send them a value of a configuration. Or others who just comes in at the right time - when you just got into your utopian magical zone - "just to say hi and catch up". There goes the rest of my day.

Complement that to the instant messaging application of choice of the organization and it's a no-no for productivity. I find myself being invited to random channels only because they want to mention that I did something. I set myself to Away whenever I'm in the mood, but that still doesn't stop people from pinging and sending me notifications anyway.

Design in Motion: Real-Time Rendering's Impact on Architecture

Architecture, a discipline that once relied heavily on blueprints, models, and lengthy render times, has undergone a revolutionary transformation in recent years. The advent of real-time rendering technology has fundamentally altered the way architects visualize, present, and interact with their designs. This paradigm shift has not only enhanced the creative process but has also empowered architects to make more informed decisions and create immersive experiences for clients and stakeholders.

Real-time rendering, a technological marvel that harnesses the power of high-performance graphics hardware and advanced software algorithms, allows architects to generate photorealistic visualizations of their designs in a matter of milliseconds. Gone are the days of waiting hours or even days for a single rendering to complete. This acceleration in rendering time has not only expedited the design process but has also encouraged architects to explore multiple design iterations rapidly.

One of the most significant impacts of real-time rendering on architecture is the ability to visualize a design in various lighting conditions and environmental settings. Architects can now instantly switch between daytime and nighttime lighting scenarios, experiment with different materials, and observe how their designs respond to different seasons or weather conditions. This level of dynamic visualization offers insights into how a building's appearance and functionality evolve throughout the day, contributing to more holistic and thoughtful design solutions.

Moreover, real-time rendering has transformed client presentations. Architectural concepts can now be communicated with unprecedented clarity and realism. Clients can virtually walk through spaces, observing intricate details, exploring different angles, and even experiencing the play of light and shadow in real-time. This immersive experience fosters a deeper understanding of the design intent, enabling clients to provide more targeted feedback and make informed decisions.

The impact of real-time rendering on collaboration within architectural teams cannot be overstated. Traditionally, architects and designers would need to wait for a rendering to complete before discussing design changes or improvements. With real-time rendering, team members can make adjustments on the fly, observing the immediate effects of their decisions. This seamless collaboration not only enhances efficiency but also encourages interdisciplinary collaboration as architects, engineers, and other stakeholders can work together in real-time to refine designs.

The integration of virtual reality (VR) and augmented reality (AR) into the architectural workflow is another transformative aspect of real-time rendering. Architects can now create VR environments that allow clients to step inside their designs and explore every nook and cranny. This not only enhances client engagement but also enables architects to identify potential design flaws or spatial issues that might not be apparent in 2D drawings. AR, on the other hand, overlays digital information onto the physical world, facilitating on-site decision-making and construction supervision.

Real-time rendering's impact extends beyond the design phase. It has proven to be a valuable tool for public engagement and community involvement in architectural projects. By creating virtual walkthroughs of proposed structures, architects can offer the public an opportunity to experience the design before construction begins. This transparency fosters a sense of ownership and allows for constructive feedback, contributing to the development of designs that resonate with the community's needs and aspirations.

The environmental implications of real-time rendering are also noteworthy. The ability to visualize designs in various environmental contexts contributes to more sustainable architecture. Architects can assess how natural light interacts with interior spaces, optimizing energy efficiency and reducing the need for artificial lighting during the day.

In conclusion, real-time rendering has ushered in a new era of architectural design, propelling the industry into a realm of dynamic visualization, immersive experiences, and enhanced collaboration. The ability to witness designs in motion, explore different lighting conditions, and interact with virtual environments has redefined how architects approach their craft. From facilitating client presentations to fostering sustainable design solutions, real-time rendering's impact on architecture is profound and multifaceted. As the technology continues to evolve, architects have an unprecedented opportunity to push the boundaries of creativity, efficiency, and sustainability in the built environment.

I do not feel insecure in my competency as software/Firmware engineer but i started feeling really insecure about being an engineer , mostly because the way Society in general place us
usually it's like

surgeon > physician > Scientist (or any basic science person) > engineer

i didn't realise this before but recently i noticed and i stopped introducing myself as engineer to the people i meet either from my family or from dating apps. Here is the conversation that usually happens

Person: what do you do ?
Me: I build things
Person: so what do build ?
Me: My work involves building lot of things related to smart phone's wireless capabilities.
Person: oh so you manufacture phones ?
Me: No i work in connectivity part of it like bluetooth , wifi
Person: I don't understand, does it involve staring at computers all day (makes a face )
Me: yes 90% of it , I like building things making something new HW or SW and most of them do require a use of computer , even if I was a mechanical engineer computers would be necessary
Person: Hmm if i was not a surgeon i would be hair dresser , because i can't do anything that involves staring at computers all day.

same conversation happened multiple times.
no matter how good you are at writing code or how important task that code is performing , society consider's Software Engineering as a mundane task of " staring at screen "
if that song Remember the name is written for software engineers it will go like

This is ten percent luck
Twenty percent skill
Fifteen percent concentrated power of will
Five percent pleasure
Fifty percent pain
And a hundred percent reason to live in disdain

There was a good old barber in Mumbai. One day a florist goes to him for a haircut. After the cut, he goes to pay the barber and the barber replies:

I am sorry, I cannot accept money from you; I am doing a Community Service.

Florist is happy and leaves the shop.

The next morning when the Barber goes to open his shop, there is a "Thank You" Card and a dozen roses waiting at his door.

A Confectioner goes for a haircut and he also goes to pay the barber. He again refuses to take the money.

The Confectioner is happy and leaves the shop.

The next morning when the Barber goes to open his shop, there is another "Thank you" Card and a dozen Cakes waiting at his door.

A Software Engineer goes for a haircut and he also goes to pay the barber again refuses the money saying that it was a community service.

The next morning when the Barber goes to open his shop, guess what he finds there......

A Dozen Software engineers waiting for a free haircut... with Printouts of forwarded mail mentioning about free haircut.

Engineering days: Wasting the entire semester and studying a few days before exams
Post Engineering days: Wasting the entire day and working just a few hours before the shift ends
Happy Engineers Day everyone😄