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

Food arrives, boss grabs his food.

Boss: ahhhh finally! *looks lovingly at food* you won't hear me for the next 15 minutes 😍 *starts eating*
Me: well that was about fucking time.
Boss: 😐😶
Other engineers: 😂 *trying to keep food in*

#wannaCry :
*US engineers trying to find antivirus.
*Europe engineers finding preventing tools
*Meanwhile Indian engineers already updated their resume with " Worked/Implemented anitvirus for wannyCry"

Meanwhile. .
Indian HR consultants asking for minimum 5 years experience in handling "wannacry"

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.

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!

"Why did you bring Wagyu beef to the meeting?"

"Because the calendar description said: Engineers should proactively add value for our steak holders"

(True story -- They told me to do what management instructs, without correcting anyone and without asking questions. And I love playing that game!)

Dear clients.

Putting your support subject or content either in uppercase letters or telling US that your matter/ticket has 'the utmost priority' doesn't mean anything to us. You'll just have to keep in line.

WE decide the priorities. Also, calling us when we haven't looked into your very fucking high priority ticket yet for about 5 FUCKING minutes is NOT going to help YOU.

- One of the Linux Support Engineers.

That moment at work when we've had no calls for an hour and suddenly the phone goes off

*TRINGGGGGGGG*

*suddenly you have a few Linux support engineers with a mini heart attack*

😅

Boss asked one of our senior Linux engineers to look into an issue. When restarting a service, the person renting the server would get the errors e-mailed which occurred during the restart (it wasn't reachable so the service trying to reach it would throw errors).

Although this was very expected behavior, the client found it unacceptable! Boss asked the engineer to look into this while acknowledging that it was probably an impossible task except for if you'd just disable logging but then all debug info would be gone which we frequently use to debug stuff ourselves.

After two minutes:

E (engineer): fixed it.
V (boss): wait, WHAT? HOW?! I'VE BEEN TRYING TO FIND A FIX OR WORKAROUND FOR AGES!
E (with the mist nonchalant/serious face): I disabled the log mailing in the configuration.
B: 😶
B: .
B: .
B: .
B: 😂

Everyone was laughing. The client thanked us for 'solving' it xD

Waaaay too many but let's go with this one for now.

At my previous job there was a web application which was generating about 1gb of log data a second. Server was full and the 'fullstack engineers' we called had zero clue about backend stuff and couldn't fix it.

Me and another engineer worked our asses off to figure this out but eventually the logging stopped and it went back to normal.

Great, right?

For that moment. I was the on-call server engineer and at like 3am I got called awake because this shit was happening again.
Sleep drunk with my phone I ssh'd into the server, not sure about what to do at first but then suddenly: let's chattr the goddamn log file...

$ chattr +i /var/log/logfile

Bam, worked, done, back to sleep.

(this comment + param marks the file in a way that it can only be read until the mark is removed, so you can't write to it or move it or remove it or whatever)

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.

Employer: so why do you want to join this organization?

Engineer: well like i said in the first 4 interviews, I love desks. Sitting behind them. Standing behind them.

Employer: are you a standing or sitting man?

Engineer: i like to sit in the morning and then switch up to stand at lunch.

Employer: a man with a plan. Very good. Do you remember anything from school?

Engineer: not a goddamn thing.

Employer: perfect. You don't need math. Just emails. You like emails?

Engineer: love emails.

Employer: there's gonna be a lot of emails.

Engineer: can't get enough emails.

Employer: perfect. Do you like a clear separation between life and work?

Engineer: oh not at all. I like it to muddy together in a never ending hell.

Employer: alright and you're familiar with work culture?

Engineer: oh those hours i work for free?

Employer: yes.

Engineer: I love that bullshit.

Employer: alright terrific. And are you familiar with the hate hierarchy?

Engineer: yeah the tech's hate the engineers, the engineers hate the tech's and the managers hate everyb-

Employer: everybody. Perfect. Alright I- honestly I think we'd like to make an offer.

Engineer: well, first I gotta leverage that with my current employer for a raise. And if they don't budge, I'll jump shut.

Employer: no loyalty at all?

Engineer: not at all.

Employer: you're hired.

I used to work in a role that was basically tech support for engineers. Folks would call, we'd look at their code and see where things were going wrong.
One customer calls in, they're having timing problems with a satellite control system.
I dig down through their code, and buried in one of the modules is a comment to the effect of:
"Once we upgrade to Windows 98, we'll need to change this call to the precision counter"

They never did.

This system was running XP.
Somehow, they'd avoided destroying satellites despite having the code run on Win98, and ME without fixing that call. It wasn't until they upgraded to a multi core system and XP that their gyros stopped responding correctly.

Holy shit.

How most recruiter emails go these days:

- Hiring multiple senior lead engineers <— That’s me
- 180k+ <— I like it.
- Must have experience with AWS, GCE, AND Azure <— Okay, you’re looking for a unicorn
- Kubernetes expert
- Experience with Rust, Node, and .NET <— What type of fucking company are you?
- Must be on call and 25% travel <— Why?
- Preferred: experience with printer repair, Raid Arrays, CAT5, and Microsoft Access <— Y’all fucked up somewhere a long time ago. I’m out.

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."

rant

The Java course at our Uni requires us to do an end semester project - A Java App with Swing for GUI and some Multithreading code in it.

They asked us to upload the code to drive. I was bored and was checking out my friends' projects.

The code below is what I saw in one of the projects. They have simply called a thread with an empty run method because the project required to use multithreading concepts, wtf.

But then, It is no surprise to me cause these are the people who memorize code and vomit code for marks.

I am worried that people are going to be awarded degrees and called software engineers.

God save the software industry!

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

I was tasked with maintaining a handful of chemistry simulations for the web. First things first, replace these outdated links and turn them into Bootstrap buttons that work on mobile. Wait, why do all of these look so horrible on mobile? nothing's scaling properly. *looks at fucking 1,000-line CSS file* The old developers used position:absolute for absolutely EVERYTHING. And I counted one div on the entire page. This is why you don't trust chem engineers to do your "web design" #FuckDreamweaver

#wannaCry Ransomware:

US engineers trying to find antivirus

Europe engineers finding preventing tools

meanwhile...

Indian engineers already updated their resume with " Worked/Implemented fix for wannaCry ransomware"

Meanwhile...

Indian HR consultants asking for minimum 5 years experience in handling "wannacry"

And meanwhile....

in Hyderabad Ameerpet - people might be seeing banners of training institutes mentioning that they have trainers available with 10 years of industry experience on this.😜😜😝😝

Looking for Software Engineers with POOP experience!

Virtual interview starts and the HR lady:

Oh I was expecting a man!!

(I wasn’t expecting you get surprised!?)

Haven’t you ever worked with female developers in your company or know that it is actually not big news? Some companies have a lot of female engineers including the ones I worked for.

In Central Europe in this age of time?

She was a lovely lady though. I just said

I hope you’re pleasantly surprised 😊

Just scored my personal red flag bingo in new project:
- engineers who work there for 20+ years
- their own in house build tool
- "we have Jira so it means we are agile"
- "we have Jenkins so it means we do Ci/cd"
- git adoption is "in progress"

Business guy: hmmm, what do you think about getting the programmers to come to the office more often?
Me: uhhhh explain?
BG: feels like when working from home they might only give it their 90%, but in the office they'd do 100%.
Me: let's not talk about how you reached that conclusion for now. If you force them to come more often they will quit.
BG: what about the new people we want to hire?
Me: most jobs have full remote available, why would anyone pick us?
BG: hmmm. Btw next week we'll talk with some stakeholders about trying to get some outsource help. You know, for repetitive stuff that doesn't require in-house engineers.
Me: like what?
BG: you know, repetitive stuff

This is suffering. Is my only choice to tell the guy that he has no clue what he is talking about, should STFU, and let the technically capable people to handle themselves? As in, we already do but for some reason he still thinks he knows better than the people doing the god damn job? But if I do so, the salinity in his blood will bring other problems upon us.

I have got a new director at work. My previous director had to retire already, the man was already feeling it and he had been on the institution for more than 35 years....I am 30, so this tells you how much the man has been there.

This new dude.....has the presence of a Caterprie (Pokemon) or an Oompa Loompa. In contrast, the previous director felt like a 4 star General (never been in the presence of a 5 star since those occurrences are world war rare) but I had respected that man so much and loved working with him. I really did loved my boss, he was stern and professional, but kind and friendly to his staff, fiercely protective, no one took advantage of I.T while he was there, he would literally fight for us and took our word before anything else. The man was, well, a true man. A true leader.

He took a chance in putting me as the head of my department, but he had faith in me, and coached me and trained me as much as he could. Had the requirement for his position not been a masters he himself told me that he would have loved to make me his successor, even when I would constantly tell him that I was scared shitless of the work he did and the amount of things he did for the institution, to me this is a very laaaaaaaaarge cowboy hat to fill (this is Texas, he wore a hat, the saying is normally "shoes to fill", but fuck it)

This new guys looks away when the other managers are speaking to him. He constantly interrupts us. He constantly tells us about how the other institution in which he was (rival might I add) does X or Y, its fucking annoying to the point that me and the other managers have a drinking game, for every time he references his old institution we drink one beer over the weekend. It is Saturday night and I am 36 in in total (this is my favorite part of it tho) and it is just annoying.

His train of thought makes no sense to me:

"This application, where did you buy it? we tried purchasing one on Y when I was still there but found none"

Me: "Well, since it was a new government mandate and had nowhere to go we had to develop it in house"

Him: "We had tried to purchase what you guys had but found no place that sold it, so why didn't you try purchasing it?"

Me:.....well, because it was brand new, purchase it from where? We also don't like dealing with vendors that manage these sorts of things because every new requirement takes them weeks to produce on very high budgets, historically, my department has only had maintenance fees for the software that we have and even those applications crap themselves all the time and they take weeks to answer back to us.

Him: So you decided to develop it in house instead? we would never do that! back at y we purchased everything our engineers never really developed anything!

Me: Well then, what is the purpose of having engineers if they are not going to actually develop an application?

Him: IF there is something out there that is better then why should you reinvent the wheel?

Me: For this one I did not reinvent the wheel, I am not talking about creating a programming language from scratch, but how does custom solutions that specifically feed the needs of the institution to be produced otherwise? The department has developers for a reason, because they have very specific needs in here that can only come from a team of developers that are in house satisfying those needs.

Him: Well our engineers never had to do that. Sure projects sometimes had to put on holds because the vendor was busy, but such is the nature of development

Me: No it is not, the nature of development is to create things, it is one thing for my team to go through bugs and software considerations, it is another for me to not provide a service because some random company is taking two weeks on a $300 dllr an hour contract to put a simple checkbox on a form. If a project fails the board is not going to care that some vendor is not doing their job, they are just going to blame me, if that is the case then I would much rather the blame be actually mine than some sucky third party "developer" also, your engineers where not even engineers, they were people with a degree that purchased things, that's it, please do not compare them to my guys or refer them as engineers in front of me, they are not.

Him: Well, maybe.

MAYBE?!! motherfucker I did not kill myself learning the ins and outs of architecture and software engineering on my own time after my fucking bachelors in C.S for your codeless background ass to tell me MAYBE. My word IS the fucking WORD here, not yours. Fuck me I really dislike this dude's management practices.

The shitty part? He is not a bad person, he is not a bad dude that is out to get us, just a simple minded moron with no place as a leader.

I know leaders, I know what a leader is, this is not one.

I think the main issue with Computer Science is that it's considered an Academic study, while 99% of work is very much dynamic, quickly evolving and hands-on.

I think all forms of (higher) education should be part time, starting at 4:1 college/work, gradually moving towards the opposite.

Currently, combining work and study is only done for "lower level" education, at least in my country: For example a car mechanic needs to work on actual cars, and barbers need to cut actual hair.

To me, it makes sense if engineers work on actual software, during their education.

It also feeds back into the education itself, when companies are paying for courses and the course doesn't teach practicalities, there's a lot more feedback to the colleges on how to adjust their material.

Our software uses a lot of video/audio hardware. But this hardware goes away when we deliver to the customer.
So everyone was asked to think of a way to be less depended on hardware.
I thought of a very clever idea and I told it to two senior software engineers who both saw much potential in it.

I've only worked here for close to 2 months. And I feel like this is a major contribution if they'll use my idea

Next week at the brainstorm session I'll have to present my idea (informal meeting)

I'll make an update when I know more

>be me
>drop out of uni studying civil engineering
>"self-taught" "web programmer"
>start freelancing in 2010
>Make money, feels good man
>clients keep me busy, feel important
>Code just for the fun of it
>be 2019. Married, code to make ends meet
>lose all interest
>mere sight of the ide makes me want to bash the screen
>have zero motivation
>never get any projects done
>become broke af
>look at old friends on fb. They are "Something".
>look at real software engineers and programmers with education
>realize I am an imposter
>start dropping all projects and studying theory
>become more broke
>start taking "motivation pills" to just start working again
>lose all motivation and pissed at all the real programmers and engineers for their success
>be me on May 20, 2019 at 2:56 AM
Yep, this is the end.

Slowly working it up now, actually.

An annually updated, unbiased, multiple source application that engineers can use to check salary offers vs their skills, to make sure they don't get shortchanged. Intended to work for the entire planet (that we have data for).

The company I work for (very big IT consultancy) has made the absolutely genius decision to put a block on the corporate proxy for GitHub. GITHUB. Because no fucking software developer ever needs to visit there. Their reason? "We don't want people publishing our intellectual property". Mate, I can fucking guarantee you that if unscrupulous bastards want to publish code against our T&C's, they will do so. Why make every body else's job harder and block it?!

But the best bit, you can submit a request (that is accepted without question) to get yourself an exemption. WHY THE FUCKING FUCK HAVE THE BLOCK IN THE FIRST PLACE THEN

To add to their fucktardery, they blocked the CDN that hosted stackoverflows css and JavaScript last year (CloudFlare) weeks after the alleged hack was fixed, and seemingly without any research at all. This obviously rendered stackoverflow unusable. Because again, why would a company full of engineers need to go there.

Morons.

Whether you hated 2017, 2018 will be better, promise.
Wish everyone a happy new year.

Best wishes,
cozyplanes

P.S.1. Thank you everyone for making me the part of devRant!
P.S.2. Thanks David and Tim!
P.S.3. If you need to work todayn and you don't think that it is the right thing to do, think of engineers working in a TV/radio broadcasting company. They should prepare the show! (Poor devs there)

Every year, my company organizes an internal seminar week for its engineers and developers. I helped plan it this year and, since I also ran a few sessions, was absolutely exhausted by the end of the week.

On Friday of that conference week (after I'd spent four hours in our engineering building), I come back to my desk to discover that a coworker managed to, single handedly, get our boss to agree to shortening our release cycle to one that, without dramatic infrastructure changes, would require about 8x the developer overhead than today's. ...The test cycle I am supposed to pick up in a month.

When asked about it, he said he was so full of energy, why wait for automaton? What better way to inspire us to improve than to switch right now? The worst that can happen is just a few bugs.

I love my job, but I can't stand this guy. 😒

software engineers be like “i don’t read books” then proceed to read api documentation for 4 hours straight

I'm reading jobs ads for engineers at my current company and laughing. It sounds so serious with the wording they use but in reality, it's a clownhub.

This shows I should not be intimidated by job ads and trust my abilities and have more fucking confidence!

My university has a course "Higher Programming Languages for Engineers".

The language you actually learn there?

Fortran 90.

Technically they are right and Fortran continues to have quite an importance in the field of numeric simulations, but still. The name is pretty misleading.

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 ✌

Soooo I think I have finally come to the point that I may have to create a YouTube channel, to teach software engineering from the ground up... and teach it the way the universities and everyone else should be teaching it, so that they have a solid foundation.... throwing hello world, and loops and variables at folks out of the box without any of the environment context or low level embedded register, even logic gate understanding

That lack of understanding is why, soooo many college students and younger folks, are actually pretty shitty engineers. Everything is high level languages and theoretical concepts to them. Nothing practical, that’s why there’s sooo many python and java developers that can’t for the life of them understand memory management, low level hardware interfacing etc, because the colleges don’t teach it the way it use to be taught.

I seriously fear 30 years from now or sooner when there are few embedded engineers only left till retirement, as without those folks the whole pyramid of electronics falls to pieces.

Java, C#, python, all that shit don’t run on the bare metal... there’s this magical layer of C, and assembler that does all the work just so folks can abstract their thoughts.

Either 1 of two situations will happen.. price of electronics will rise because the embedded guys are few and far between therefore salaries skyrocket... OR everything starts running shit like java on the metal, where there are a over abundance of developers, their salaries will be low because there are soo many but the processing power, space, and energy needed to run java natively causes electronics cost to increase

but regardless 30 years from now if those script kiddies are building everything I fear it cuz there’s gonna be memory leaks, and overflow issues everywhere.. shit be blowing up more than 4th of July.. lol

Soooo in effort to prevent that and keep the embedded engineers up, or atleast properly educate the script kiddies, I’m gonna make that YouTube channel.. 1 maybe 2 videos a week, 1-2 hours sessions each.. starting at the fucken ground and building up.

My worst interview ever was my first interview fresh out of college. After the initial phone screen, they asked me to drive 2 hours to their office to give me a "code challenge."

The challenge was to spend 4 hours writing a simple rest API for a blog type thing, but the catch was to not use any existing libraries for data access and instead write an entirely database agnostic DAL. Then after I finished they sat me in a conference room with 3 of their engineers and the CEO to just tear apart my code.
For a JUNIOR position to someone fresh out of college.

I guess I defended it well, because they asked to continue the process l, but after that I found a different position.

1. Aim is to complete work as soon as possible and not worrying about good coding practices.

2. Senior Engineers take credits for everything that Junior Engineers work on. And that Junior Engineers are just shadows

3. Credits? Team lead and senior engineers take. Complains/issues/delay in product delivery? Junior Engineers are blamed

4. Testing? Test cases? What are they? Why do we need them? That's what my team lead asked.

5. Take work without even knowing what it is or what is to be done and then just keep carry forwarding it.

6. Junior engineer dares to point out any mistake, he/she is very rude and is taunted forever

And many more.....

*phone dings*
Manager: Please share the timelines for feature X

Me: *swiping away the Teams notification* Please get a life and stop texting your engineers at 9 PM

New spin on the Manager / Dev format!

Recuiter: WE NEED AN ABSOLUTE NODE EXPERT, NODE NODE NODE, WE LOVE NODE! WHAT IS YOUR NODE EXPERIENCE?!?!

Dev: Well I've had exposure to it since it was nearly new, all the way back in 2012, and since my professional career started about 7 years ago I've used it fairly often on a per-project basis.

Recruiter: WELL HAVE YOU BEEN USING IT DAILY FOR THE PAST 5 YEARS!?!

Dev: Well no, as I said I've used it for specific projects... anyway, there are these things called weekends...

Recruiter: WELL WE ONLY WANT NODE ZOMBIES SO SORRY.

Dev: Thanks for reaching out and wasting my time.

Recruiter: ...

Dev: ...

God recruiters are like robots, don't they understand senior-level engineers are language agnostic?

The founder of a company I worked with is convinced that if you're a founder who argues with engineers, you're a bad founder.

He believes that any engineer knows engineering stuff better than any manager. It feels like common sense. Though it's a very rare point of view among managers. He agrees and says that managers only argue with developers because of lack of confidence, megalomania or some other ego issues.

So, all our arguments with him go like this:

— %Foundername%, we should change X, here's why
— Okay, discard existing mockups and go ahead

Or like this:
— %Foundername%, we should change X, here's why
— Kiki, I tried it, here's the evidence that our current stuff works better
— Okay

It's always this two ways and never something like "I'm YoUr SupErIoR sO I'm rIgHt", the stuff I heard in companies I worked for before.

On reccomendation of @chabad360 I made this its own rant.

I switched from marketing to CS (complete with a three year degree, no Bootcamp). I still went to interviews as you'd expect a marketing man to go; in a suit. Commence the weirdest interview.

$I: interviewer
$M: Me

I: "You're not the typical engineer. Can you talk to real engineers?"

M: "could you elaborate"

I:"you're dressed in a suit. That leads me to think you're a MS user. Do you think you could talk to real, ie. Linux using engineers?"

M: " well, I haven't used windows in about a year soo..

I: "Mac isn't Linux."

M: "I'm aware. I've switched to Ubuntu so I could use KVM-QEMU android emulator with GPU pass through to train Deep Convolution Networks on mobile devices. Also had to compile Google's internal build tool because it had bugs I had to fix so I could compile the APK."

I: "ah, Ubuntu eh? **Insert Smirk** How about a follow-up?"

M: "no, I'm switching to Gentoo this week and would like to talk to real engineers about that."

I thanked him for the coffee and left.

Note that the example tags for rants includes Xcode... There is a reason.

In 1984 Apple introduced Macintosh and we got a computer that could barely handle multiple windows on the screen. But by 1986 multiple windows all over the place.

In 1985 Microsoft introduced Window 1.0 Yes boys and girls, no "s" because it hand only one Window. 7 years later in 1992 Microsoft got their head out of their ass and produced "MDI" or Multiple Document Interface and woohoo, had multiple windows on the screen... big boy pants 8 years after Mac.

Today we have Xcode from Apple. The old Window 1.0 engineers are apparently alive and well as Xcode is a One Window Trick Pony and if you fight with it, it starts randomly jamming your separate Windows into tabs into one window, completely fucking up your spatial organization of your working source code.

It is like the bastards going into a blind man's house and re-arranging his furniture for fun.

Xcode - it's only free if your time is worth absolutely nothing.

Did I ever tell you kids about the time I worked for a company that got a contract to develop an iOS application around some object detection software that had been developed by another team?

Company I was working for was a tiny software consultancy, and this was my first ever dev job (I’m at my second now 😅). Nobody at the company has experience building mobile applications but CEO decides that the app should be written in React Native because _he_ knows React Native.

During a meeting with the client, CEO jokes about how easy the ask is and says he could finish it in a weekend. Please note that Head of Engineering had already budgeted a quarter for the work. CEO says we can do it in a week! And moves up the deadline. And only assigns two engineers to project. I am not one of those engineers.

The two engineers that are put on it struggle. A lot. They can’t seem to get the object detection to work at all, and the code that’s already written is in Objective-C. I realize one of the issues is that the engineers on the project can’t read Objective-C because they have no experience with Objective-C or even C. I have experience with C, so I volunteer to take a look at it to try to see what’s going on.

Turns out the problem is that the models are trained on one type of image format and the iPhone camera takes images in a different format.

The end of the week comes, they do not succeed in figuring out the image conversion in React Native. There’s an in-person demo with the customers scheduled for the next Monday. CEO spends the weekend trying to build the app. Only succeeds in locking literally every other engineer out of the project.

They manage to negotiate a second chance where we deliver what we were supposed to deliver at the original schedule.

I spent the weekend looking up how to convert images and figure it would be a lot easier to interface with the Objective-C if we used Swift. Taught myself enough Swift over the weekend to feel dangerous. Spoke to Head of Engineering on Monday and proposed solution — start over in Swift. Volunteer to lead effort. Eventually convince them it’s a good idea (and really, what’s the worst that can happen? If this solves our main problem at the moment, that’s still more progress than the original team made)

Spend the next week working 16 hour days building out application. Meet requirements for next deadline. Save contract.

And that’s ONE of the stories of my first dev job that got me hired as a senior engineer despite only having 10 months of work experience in the industry.

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!

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."

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.

So i got a message on a job platform today from a recruiter. So far nothing unusual. But what he wrote was really disgusting. It was basically something like this:

"Since many engineers now lose their jobs in the covid-19 crises, rest assured that we are still hiring! I work for a large company blablablabla..."

So he tries to play with your fear of losing your job in the coming depression. It's also quite possible, that he will also try to negotiate a shit salary for you. Since at least you have safe job now, right?

Fucking disgusting pig.

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.

I manage a team of engineers.

Toxic Culture Post #2:

Manager: Everybody on your team needs their own swimlane in Jira. Each person's work should be their own lane. When I have a ticket for <Project A> I want to make sure that <Bob> always gets it, all tickets for <Project B> must go to <James>. You'll need to figure out which team member will handle <New Project C> and create their personal swim lane.

Me: That's not really how SCRUM works. Actually, that's not how teamwork works. You're creating silos and we all need to learn how to do these tasks. We're a cross-functional team, and each team member brings their own unique talents to the whole process.

Manager: So you'll create the swimlanes?

Me: No

Manager (to Bob): You'll be devoted to <Project A> from now own. It's the only work I expect you to do. All work for that project will be yours.

Likewise, my manager also reached out to each team member and assigned them specific tasks, furthering the silos.

I often want to scream at co-workers because of their lack of attention to details.

I believe attention to detail is important for software engineers.

I tell my junior developers that "it works" isn't enough, you need to make sure it works as perfectly as possible and paying attention to detail helps with that.

Six people(4 engineers, 2 managers) in the room, it took fucking 45 mins for daily scrum/standup meeting. Seriously, why do you want talk about every line you wrote?
I excused myself after 35 mins.

3 hours of "I don't have access to that router" and waiting for someone who does have access to join the line. And then they don't have access, etc..

I love networking, hate working with network engineers.

So we have Oncall system. Every month I get one working weekend.

Now senior engineers and lead are assholes. They think they can bully us. They are putting their Oncall work on our heads.

I refused to do it. But my partner in Oncall agreed to take up their weekend Oncall and in return they would do our weekday. I don't see how that is fair enough.

I refused to do it still. My partner apparently ended up doing it alone this weekend.

I don't FUCKING need to lick anyone's ass here! I don't FUCKING need to do these things to be in their good books! Waiting for the time when I saw GOODBYE TO THESE FUCKING ASSHOLEZZZZ

The online funeral live stream just broke. The 4G* connection at the place is awful, which is probably the reason for it...
*If it even has 4G now, it definitely didn't a few years ago

Germany keeps jerking itself off how amazing our economy and science is. We're a country of engineers and all that.
Yet our digital infrastructure is a fucking joke.

Rural area? Well better hope you'll get any reception, let alone 4G.
Oh and cable connections? I've seen areas that will give you a 6 Mbit/s DSL connection.

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."

Which type of dev are you?

1. I exercise/ workout regularly :)
2. I want to. But I ain't got no time for that :|
3. I don't believe in that shit :(

PS: I see some sw engineers in my gym.

I left my country (France) because of the working conditions that are absolutely terrific in software engineering.

Basically, 80% of the time you will be hired by agencies which rent you in a dishonest way to other companies. Half of the later use the agencies services because they are scared by the work code, which is tough but fair, and the other half can’t hire because the agencies put a lot of money to get the engineers and make money by renting employees.
Most of the companies you will work in in France will have outdated stack, and an awful bureaucratic hierarchy.
Your boss will suspect you do nothing.
There is also an untold competition taking place in every companies : who will stay the longer in the office, sometimes taking place until 8pm.

I moved to the UK, the country is absolutely awful, but the working conditions for engineers are a way better, more realistic.

Client: *uses Oracle on AWS RDS*

Ora: *licence about to expire*

Client: we need a cheaper and equally performant solution.

AWS: we have an outstanding Aurora db! Its performance is flawless!

Client: shut_up_and_take_my_money.png

Engineers: *migrating to Aurora mysql*
Engineers: fine-tuning the db for 2 months, adapting app code.
Aurora: *shits its pants during test ramp-up, delivers ~70% of Ora perf*

==========

Client: we need to do better!

AWS: try Aurora Postgresql!

Engineers: *migrating to Aurora postgresql*
Engineers: fine-tuning the db for 1 month.
Aurora: *shits its pants during test ramp-up, delivers ~40% of Ora perf*

AWS: let me see...
AWS DBAs: *fine-tuning the db for another 2 months*
Aurora: *survives ramp-up, delivers ~70% Ora perf*

AWS DBAs: your application is wrong.
We: Ora didn't complain about that...

AWS DBAs: umm.. Err.. Then your load test is wrong
We: ora wasn't complaining about that either...

AWS DBAs: errr.. Ummm.. Oh, I've got it! Your queries aren't optimized!
We: we cannot change queried - they are hardcoded by our framework's vendor

AWS DBAs: well there you go! Your queries aren't optimized! It's your fault, not aurora's

yyeeahhhh... Riight...

From my xp, aws support and aws engineers ALWAYS try to put the blame on a client. Always. Even when they're obviously wrong.

I am a senior a DevOps engineer who took the production stack down for ~10 minutes today because of a bad code commit. I could use some encouragement! It’s a fierce world of competitive engineers and I wonder why my company doesn’t replace me. The mistake was missed by two other peer reviews... but that doesn’t stop me from feeling this way.

Have you crashed prod? Did your team support you or tear you down?

(From a previous rant I made)
As a note to all of my brothers from India. I am not happy with the current state in which your country is in regards to this bothersome pandemic. I do not feel happy, I am not jumping around singing to the doom you are all facing. I am sad. I know your people are good and your engineers outstanding.

Were it for me you would all be here in the U.S with me chilling with some good bourbon in celebration to how strong you can make our tech be.

My previous post was in regards to scammers, and I am very well aware that you are not at fault.

Be strong brothers, you will all survive this, just as India has survived generations of struggles.

It's not that my work is hard. Basically, all the work I do these days is something I've done before with a slight twist on it.

I just feel underappreciated.

"bUt u mAkE sO mUcH mOnEy dO uR jObBbb!!"

How much money I make should not suppress how I feel at a company. Two years without a raise, every company meeting is a circle jerk for the sales team, and whenever our work is mentioned it's "Great job to the PMs for getting this to our clients."

Fuck you guys. Lol. This is a team effort from all sides, but to put engineers last on the "kudos" ladder is just so shitty.

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.

"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.

I will give you a reverse rejection. Went to two interviews on site with company. They asked me a question, and I struggled. Solved the question one hour after the interview :) asked me to come for a second hands on interview, make some changes to sample code. Did that reasonably well. I rejected them because in both times the engineers we're sitting behind their laptops and were working. 0 interest or engagement on their side about the candidate.

That startup failed some years after.

To all the data engineers in here: WTF is going on in your field?

I've worked closely with a dozen data engineers in the last 5 years (and talked to friends and internet strangers about this and get similiar responses), mine if them seem to know how to use a computer!

They don't understand git, ORMs, best practices, how to use a terminal, DAGs (important for using modern ETL scheduling tools like airflow and prefext), etc

Guys with 10 years of experience on their resume and they can't wrap a model into a flask app with 1 endpoint. They'll reference local files on their machine in w jupyter notebook and are shocked it won't work on other computers!

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.

Attention Software Engineers!

Quit shooting yourselves in the fucking foot! And this ESPECIALLY goes to new grads. I get that you have just finished school. I get that you need a job! But don't fucking settle for a $30-$40k salary because you're "entry level"! The only reason why there are employers who offer that type of salary is because they know that there are enough idiots who will settle for it!

On average, an entry level software engineer's salary is between $50-$60k at the very least! For Senior developers, it is at least $80K/year (although an argument can be made for why they shouldn't settle for less than $100k/year).

Each time a moron low balls his/her salary, that brings down the market value for that talent. And keep this in mind! They don't have a choice but to hire you. They could choose to outsource their work to poorer countries but they don't want to do that due to obvious quality-related reasons so they HAVE TO hire you if they need the work done. And since the ball is in YOUR COURT, demand your fair salary. You went to school for 4 fucking years. You dealt with that stress for 4 fucking years. Why settle for a salary that you could've made without going to school?

Y'all, are internships in your area paid, unpaid or u need to pay to get one?

Our uni made internships mandatory! being from one of the country which produces largest number of engineers per year. Every godamn student from our uni is running around to get an internship! And there arises these dick heads with so called made up startups which has never done a godamn single project, just legally registered before the dawn and puts up advertisements for internship trainings!! All our uni needs is a fucking certificate from a technical company which is legally registered. And these assholes provide internship to those who pay them hella amount, and attend there couple of days just to get the certificate!! No developers! Just some random guy talking about html and css! Now thats Internship!

Fucking shit! Making money by looting students in their hard times! Students get the certificate that satisfies the uni, but for fucks sake at least bring an expert to guide them! No!! Need to stand up against this shit!

I never thought clean architecture concepts and low complicity, maintainable, readable, robust style of software was going to be such a difficult concept to get across seasoned engineers on my team... You’d think they would understand how their current style isn’t portable, nor reusable, and a pain in the ass to maintain. Compared to what I was proposing.

I even walked them thru one of projects I rewrote.. and the biggest complaint was too many files to maintain.. coming from the guy who literally puts everything in main.c and almost the entire application in the main function....

Arguing with me telling me “main is the application... it’s where all the application code goes... if you don’t put your entire application in main.. then you are doing it wrong.. wtf else would main be for then..”....

Dude ... main is just the default entry point from the linker/startup assembly file... fucken name it bananas it will still work.. it’s just a god damn entry point.

Trying to reiterate to him to stop arrow head programming / enormous nested ifs is unacceptable...

Also trying to explain to him, his code is a good “get it working” first draft system.... but for production it should be refactored for maintainability.

Uggghhhh these “veteran” engineers think because nobody has challenged their ways their style is they proper style.... and don’t understand how their code doesn’t meet certain audit-able standards .

You’d also think the resent software audit would have shed some light..... noooo to them the auditor “doesn’t know what he’s talking about” ... BULLSHIT!

Just got accepted as a volunteer (teacher assistant) in a non-profit organization, funded by Microsoft.
They teach high school students CS twice a week.
I know it might not be much, because I will not be payed, but I will be trained and teach alongside Google and Microsoft engineers.
The organization is called TEALS.

I hope it is a good experience and build a good network.
I do not have any friends, nor any engineer friend since I moved in USA, so I think this is a good opportunity.

P.S. Please for the love of god do not bash here Microsoft. Everyone, even the people who rant about hating Microsoft, will accept a job there if they got the chance. So please stop the hypocrisy if you intend to do some "sarcastic" comment about this organization funded by Microsoft.

Friend: i have an idea
Me: what is it?
Friend: uber is not yet here, lets do the app exactly like uber only for the city, can you do that like in one month?
Me: uber is a billion dollar company with several and the best engineers in the world
Friend: so what, just copy the exact same idea, of course the money comes when the app is done
Me: sure... ill call you in a month. (delete conversation)

So someone decides that the employees need to do these stupid Web-based training's that not even high school kids should be looking into.
What is about ?
Security and Cryptography, and now event the real stuff.

What it covers?
Alice and Bob, Bob and Alice.
Alice wants Bob some pics/messages that she suspects someone else will see. DDDDDDAAAAAAAFFFFFFFAAAAAAAAAKKKKKK

A total of 7 useless time wasting interactive and annoying training's, 20+ min each.

But someone forgot that please do not send this shit to engineers of your company, specially Software/Network engineers. Oh another subset, specially not to those who work deeper into the domain.

I'm getting paid to do this time wasting activity, and still.

I also may come back and remove this BUT FOR NOW I NEED TO RANT.

Why do recruiters say you need 5 years of experience for a certain framework when the framework was released 2 fucking years ago. Don't they consult with engineers what they want or do they just think of a random fucking number and write it down. And why do they think the OOPs concepts are totally different for all programming languages?? Also the job descriptions are usually very vague and ambiguous.

JD for SDET: you will work with engineers and help build scalable solutions bla bla

JD for SDE: you will work to build scalable solutions bla bla

Is this deliberately done so that a poor candidate wastes his or her time applying for a wrong position or even giving an interview??

Half Life, Portal and Halo as well as a hate over windows vista.

I don't shit on things I can't comprehend. So when I bought my laptop with vista and hated how shitty it was I decided to find out the culprits. Turned out they were software engineers, but I was not about to shit on engineers without knowing what they go through. Down the rabbit hole.

Portal and Half life are what inspired to focus on Comp Sci afterwards and Glados and Cortana fascinated me. The fact that good money follows in the field played a big part as well.

Also, and more importantly, mom wanted me to be a programmer since she wanted to be one, she always thought this was the future. She won't read this, but I always thank her for pointing me on this path, she is my biggest fan.

Many people / engineers around me talk about trendy stuff like Cybersecurity or AI and show off what great encryption and neuronal networks they 'have built' ( I would rather say 'using').

I kinda get the feeling of 'Everbody talks about it - no one really knows what's goin' on inside (especially those guys who hate math and even algorithms).'

Am I just stupid or does somebody else here feel the same way? I mean people have been doing serious research about this stuff for years. And currently many kids are coming up with it as if it is easy stuff like the bubble sort.

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 )

Situation : Most of my company's clients speak French, and I prefer a Qwerty keyboard for coding.

And to write proper french, I have to switch to an FR keyboard to type é, à, è...etc.

But, for some reason, I usually forget to switch back to English. Oops ! , for some reason, our fellow french chose to put change Z and W places on the keyboard.

And I end up 'ctrl+W'ing (close) , while in fact I wanted to 'ctrl+Z'ing (undo) .

I did some changes to test my code, and after I accidently closed the whole shit, it turned out that I can't undo it anymore.

Thank you french engineers for this unpleasant headache.

I wonder what they were thinking about when they switched Z and W places ?

Seriously, how the fuck is it possible for someone to be a senior engineer after only 1.5 years in the industry?

I have been working for 5 years and I don't dare to say it because I have seen real seniors with 15+ years of work experience and how they work. A completely different level. Hell, I refuse opportunities that announce they want senior engineers for that reason.

Arguing with a co worker.... he is writing a serial data plotter, and wants me to send the data as text. I’m like ugh no I’m not wasting bandwidth for text data, you are getting it as binary, as my embedded system has a lot of other stuff todo than send debug info, so the quicker I get the data to you the better... plus his program is running on a pc there is no issue regarding resources handling binary data.

He tells me I’m am wrong, and is trying to defend his stance, then all the electrical engineers and other software engineers all stand up and said why in the hell would it be faster to send text than binary? He has no response.

A company in Switzerland keep re-posting job openings for "ninja software engineers" on the university board. Maybe I should slide in with my black pyjamas and a katana and see If I make the cut?

Some of these Software Engineers on YouTube are so frustrating me:

YouTuber:

- Hey guys, I'm doing YouTube because I interviewed at Google/Microsoft and got rejected. I really wanted to work at Google/Microsoft because it's my dream company to work.

- Hey guys, I wanted to let you know that I got the job at Google/Microsoft. I will still be making YouTube videos.

- Hey guys, so I have resigned from Google/Microsoft after working for 1 year because blah blah

Upwork is absolute GARBAGE.

PLEASE tell me alternative to find a job as a dev and work remotely. I have to work for foreign international software company.

I cant be working for my local city companies because the salary even for engineers is TRASH

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.

Data Scientists/Researchers

Stop building libraries.
You can't build libraries.
You're not software engineers.

Write your script as plainly as possible.

Why?

Cus for every fucking paper that has code associated with it, unless it's from Meta or Google, I'm having to edit to make shit work.

Stop over-engineering shit.

Write your model and fuck off.

!rant && Thanksgivings++

I am truly thankful to be a programmer for it is the only job on Earth where doing mistakes is the profession itself.

Think about it. We make more mistakes than other professions on DAILY basis. If a doctor miss a step during a diagnosis or an operation, a fucking human being might die. Engineers, lawyers, teachers you name it. They are not allowed to make mistakes.

Us? We are earning money from other people for all the hours we spent fixing the mistakes which we made in the first place.

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

I really dislike the company I work at.

I want to say hate, but there are parts that I adore (mostly the people I get to work with).

However, I dislike:
- The management
- The way engineers are treated
- Lack of responsibility for on QA for finding bugs, and it falling solely onto the engineers
- Sales circle jerk every All Hands meeting
- The amount of "ring-around-the-rosy" they played with me for a 10k raise (took 12+ months and not what I was looking for when I first asked)
- They lie

Just a shitty company overall. Interesting product depending on what team you're on, but overall I'd rather dye my hair green and become a talking broccoli stock.

🪙 The golden age of tech is coming to an end. We currently live in a world of tech built by engineers and great minds; both Windows and Linux are great in their own ways. PCs are the peak of engineering, both desktops and laptops because of how versatile, powerful and universal they are. They serve engineers, designers and end users. You can do anything you can imagine; because the great people who built it, did it in such way that they themselves could use and enjoy it.

📱 The tech of the future will become ever more limited. The next generation of humans will use Chrome OS gladly and not even feel limited because they never experienced the freedom provided by a true personal computer device. Android OS is already getting ever closer to restricting 3rd party APK installers. Big tech will do everything they can to limit freedoms and make everyone use cloud, where they can charge $ for every damn click.

☎️The consumer-facing tech will become increasingly dumbed-down over time. The programmers and engineers will be still able to use "true" tech, but only for work. In everyday life, they will have to be content with the dumb limited tech.

And there is nothing we can do to stop it.

LinkedIn shows that I’m a web developer, using mainly laravel, twig, less, JavaScript, etc.

Recruiters: are you interested in a java function? Possibly .net? We’re also looking for network engineers...

As much as I love to complain about my job, I have to say I have such a huge amount of respect for my peers who go out of their way to help me and other engineers out. I feel like they deserve so much more praise because when they help others out, everyone succeeds.

I work for a consulting company, my boss comes into the room full of engineers trying to work on Adwords campaign and asks us what words to use. "Should I use blockchain, I heart that's popular. What about AR?" None of us have ever touched any of those technologies and he's going to try and market us as such to some poor potential client he's going to B.S to. Get me out of here.

So I had a problem. MongoDB replica set connection was not accessible to server in another container. I’ve used ChatGPT. Gave it my code. It showed me the things I didn’t know and helped me work out a problem I’ve struggled with for 2 days.

It’s awesome!

ChatGPT is basically StackOverflow 2.0. It’s a tool and a great one. I can’t wait for an actual production level implementation target to software engineers.

P.S. I think co-pilot sucks.

I want to say I would not have been the programmer I am now, if it hadn't been for all of my mentors in my past and current job who took a chance on me.

I am socially awkward, am nervous and stutter around new people, cannot sustain conversation, and as a consequence come out rather poorly in most kinds of interviews.

But there has been 3 mentors/leads in my life so far who saw through the nervous wreck I was in the few hours of the interview and took, what felt like to me, a gamble by hiring me. My current mentor even taught me everything I know on my job and has vastly shaped the programmer I am.

A humble thank you to all the amazing mentors out there, who inspire and enable the now green engineers, who will later be the mentors of the future generation!

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.

Competent software engineers are in high demand in Belgium. If you are looking for a workplace that treats devs as demi-Gods, relocate now.

Perks available to you are:
- working from home 2-5 days/ week.
- English at the workplace because the northern & southern parts don't speak each other's languages
- terrible rush hour traffic jams allowing you to flexibly choose your schedule as long as there is enough overlap
- pension & hospital insurance
- a company car (electric or fuel)
- ability to get away with any lack of soft skills as long as you're technically strong
- a competitive salary (2-4k/mo), even with almost half of it being eaten by taxes
- limited competition, because there's a sore lack of competent developers

Passed a code test for once and invited to interview with engineers.

I’m nervous yet proud. Any tips? It’s the first time I’ve reached this point

What companies think they're hiring for - software engineers. Actually they're looking for unicorn duct tapers.

Just had an argument with someone who thinks (micro)python is the way to go for embedded projects. Cause a lot of engineers are terrible at using C/C++. And their argumets for optimisation and granular controll over what the processor does is not necessary.
Its utterly wrong to push technologies into areas for which they werent originally designed for. We've seen it alot with websites lately and I dont like that embedded is heading the same way!

Sweet talker but Incompetent colleague/team lead has given estimate of 350 story points (1point =1day) i.e more than an year and half, for one module to refactor. Worthless manager seriously considered to proceed with these estimates and ready to accept proposal.
When presented these numbers/estimates with wider audience, one senior engineer reminded everyone that module was developed few years back, in <2 months by 3 engineers.
Shame shame!

So.. how does being in a company makes you a better engineer?

For eg, this year my team shipped these 2 interesting features (among other things) that were never part of our product.
these were crazy ideas, that got liked by our users, and might have impacted the finances of company positively.

However the engineers (not me, i worked on them even less) that worked on it, did they got their knowledge growth? they just analysed the old codebase, its shitty architecture and drawbacks, and added the feature around it in a similar manner. so basically it was building debris over the debris

but is this growth? if that engg was me, would my experience in dealing with debris and building debris over it (that somehow works) be helpful for any other organisation?

And number (2) : is my organisation even a good one if its allowing to build debris over debris and not leaving a space for discussion or cleaning the mess or thinking about better architectures, data structures for scalability and robustness?

An engineer's growth should be made by giving them a chance to explore new and best solutions and not the best hacks i guess

Why do big companies hire such loser engineers ??? I mean what the hell man. When you are hiring a fresher to code they should at least know how to apply/write a for loop. I once had a colleague who assigned each array element individually instead of writing a for loop and asked me why I refused to approve his stupid code. What do I reply to this ? It was so dumb, I could not articulate an answer.

For skilled mid-career engineers, dynamic programming problems, np-complete bar raisers.

For new engineers, simple questions that can't be taught in school (questions that require business prioritization)

For older engineers, questions they haven't done since college (big-O, writing algorithms from memory)

A column of some Soviet newspaper. Top to bottom:

The Atheist’s Page
“The oldest profession”
(Ukrainian tale)

Three people argued over whose profession was the oldest. One of them said:
— Surgeons: without them, god wouldn’t have pulled Adam’s rib out to make Eve.
— Engineers, — the other one interrupted him. — Without them, god wouldn’t have made light.
The third one thought for a while and said:
— No, mine’s older: in the beginning there was darkness, and who spreads darkness? I do!

The third one was a priest.

Fuck you thesaurus.com!

Those fools, dorks, weirdos and dweebs pioneered, crafted and shared the very architecture that not only holds up your companies your limp dick of backbone but is also the very reason for your pitiful fucking existence.

The brightest minds and best engineers of the 20th century handed your thick headed underachieving ass their creation on a royalty free platter and single handedly gave you - a fucking moron the power to compete with and dominate oxfords gigantic print empire.

We gave you a means to distribute and centralise up to date information globally in seconds only to find you now, back in your cave, living in the dark ages.

Hope you enjoy playing with your rock, you guys really do have an unbelievable amount in common.👌

Never been promoted.

I was at my last job for 3 years 6 months (first out of uni), my last mid year review I was discussing my performance with my manager, he said I was doing everything I needed to be promoted, just needed to wait a bit longer. I had been performing at that level, with that extra responsibility, for 18 months.

I've since left for a job at Amazon, start in a week, and will literally double my salary. The thing that annoys me is I was one of the most junior engineers in the building, but giving support and teaching almost every engineer in the office. Granted, the company was only 30 people (mostly engineers), but still felt undervalued...

Im deploying a Machine Learning Model to production. We dont have an automated deployment pipeline for the models, so we do it manually exposing the models through a rest api.

I asked for the model artifact to the DS, they didn't have permissions to download files from Databricks.

I asked their manager for the artifact. He told me that he has the permissions, then bullshitted me with something about the formal process, some shit about proper permissions handling, and that they do no have a standard process for sharing files right now so i should wait.

I was like "bro, share the artifact with me to unblock my work, then stablish your process, i dont care". He said no, and just after that he started a thread involving half of the middle management and data engineers asking for feedback on how to stablish a process for sharing databricks files. Just Wtf.

I got pissed, i reach out to his superior (good friend of mine), that was on vacation btw, and i told him the situation. He opened slack and humiliated him so bad, that i almost felt bad for the manager jajajajaja.

I grabbed my model artifact and got out of there instantly.

The programming things I've seen in code of my uni mates..

Once seen, cannot be unseen.

- 40 if's in 10 lines of code (including one-liners) for a mineswepper game
- looping through a table of a known size using while loop and an 'i' variable
- copying same line of code 70 times but with different arguments, rather than making a for loop (literally counting down from 70 to 0)
- while loop that divides float by 2 until it's n < 1 to see if the number is even (as if it would even work)

..future engineers

PS. What are the things you've been disgusted by while in uni? I'm talking about code of your collegues specifically, I'm also attaching code of my friend that he sent me to "debug", I've replaced it with simple formula and a 2D distance math, about 4 lines of code.

*embedded rant*
Boss finds new chinese supplier for the lcds we use and tells me to make one work so we can see the new quality. All is good.. the lcd works. But at some point I start seeing some defects. Pretty annoying defects.
Boss tells me to explain the defects to the chinese engineers so that they can either fix it or tell us if we did something wrong. So I do it. I explain everything in detail as one engineer to another.
An hour after I submit the email I get called. The boss is furious that the email is bs. His reasons .. " We are working with cheap-ass chinese. None of their engineers know english. How do you expect anyone to understand all that stuff you said?!"
ffs.. i had to dumb it down to 5th grade english..

So my company is using the cheapest software products out there; to save money of course. Naturally you pay what you get for, aka shitty products. I wonder how much money we waste by demotivated engineers using this Scheisse!

It's weird how these "senior engineers" bash on other people's code while they themselves are still stuck coding in 2007 and refuse anything new or different. "Software Engineer" has become a laughing stock that I don't want to associate myself with the title anymore. Instead of engineers, I'd call those seniors "software tools" (also human "tools" for that matter).

We make a small server product with a web based admin system, as we were going to have limited customers who will use this (usually just the engineers) and this was not on the www. We dropped all support for all browsers other then chrome/firefox. No more IE/safari bugs for us XD

#Ransomware :US engineers trying to find antivirus, Europe engineers finding preventing tools, meanwhile Indian engineers already updated their resume with " Worked/Implemented anitvirus for ransomware"
Meanwhile. . Indian HR consultants asking for minimum 5 years experience in handling "ransomware"

I will never work in an open floor plan environment again.

The average salary is 6 figures and they can't even spring for sound deadening material on the concrete walls, nevermind cubicles.

Nothing says "I don't value your contribution to our product" quite like treating your engineers like cattle.

Here I am for three months trying to implement TypeScript in this project that was a dump when I picked it up.
And then some morons get assigned to the project and just start adding @ts-nocheck everywhere?
Like, WHAT THE ACTUAL FUCK?

And then you wonder why the project is bug-ridden??
FUCK THESE PEOPLE THAT CALL THEMSELVES JAVASCRIPT ENGINEERS!! NO WONDER JS GETS SUCH BAD PRESS WITH ALL THESE CLUELESS IDIOTS TO WHOM STATIC TYPING IS JUST AN OBSTACLE TO THEM CHURNING OUT LINE AFTER LINE OF "CODE"

Almost at my company for two years, and not a single raise or compensation adjustment. No bonuses. No nothing.

I was scheduled to get something in April, but COVID hit and fucked it up for everyone.

But hey, if you're on sales you get a BONUS on top of your commission for selling a product and get a mandatory meeting every Friday that the entire company has to attend, just to jerk each other off with deals we've made.

Yes, we make a product. Yes, you are hired to sell it. We cannot live without each other. Just blows that the engineers are under appreciated, underpaid, and just not cared about.

full of contradiction.

If u try freelancing nobody would pay you shit coz theres always someone who'd do it for 100$.

If you do get a good budget freelance project, any Dev you'd consider outsourcing to to split the work with will ask for more than the project is worth.

There's a lot of competition but it's basically made up of

- people from fancy universities who dont know shit coz they think their degree is worth something on its own and expect high salaries off the bat.

- people who figured out the first group are idiots and tried to self learn, so they joined bootcamps that spoon fed them some Laravel and React and now think they are high tier engineers but may not even know their way around a bash terminal

- people who actually know their shit, went through hell to get the skills they have now, could probably spin up a startup on their own

group 3 all left the country tho

Man I am tired of my company's dogshit software release process.

We have to commit to fucking estimates for 6 months (2 quarters), SQA shadowing dev by 2 weeks, and freaking estimates and work done at the end are not even close. And then we call it a minor release. These shitty estimates are based on requirements that basically say "we want feature x, plz make it work". It's some fucked up agilefall garbage that does not work for shit.

We rush like motherfuckers during the final weeks because estimates are bullshit but we are still expected to be done with every story points which somehow are days instead of other better metrics.

I swear this fucking bullshit has been designed by the board so they could plan their money entries based on the software release.

The only reason this company actually still holds itself up is because the engineers are good at their job.

Go fuck yourself high management.

Okay I'm doing the whole leetcode bs, interviewing with a faang like company.

I'm genuinely curious to see if their engineers are actually any good. It seems backwards to me to hire someone based on something they most likely know by heart.

It's like trying to stress test an API by calling a cached endpoint. It will look fast AF, and it will be, but it won't compute shit.

Anyway, if I get the job and the engineers aren't crappy, then I'll forever stfu about how lame this is. But if I get the job and the devs are crappy, oh boy you'll hear me for a long time.

What happens when you get bored of working as a software engineer?

3 years after starting my career as a dev, I'm already in the middle of a crisis, struggling to find motivations to stay in tech aside of the good salaries.

Don't get me wrong, I like solving problems trough code, designing complex solutions, I love software architecture. My problem goes around the jobs themselves, doing engineering for a living is just so boring, makes me feel so empty inside.

It is not the same doing something for someone else company than doing it for yours, I usually feel like I could be happier raising my own startup, immediately after that, I remember that I must stick around working for someone else if I want to put food on my table.

I have been thinking about quit and get a normal job, but money is a huge deal, i'm used to a lifestyle that is hard to backup without a salary like the ones of software engineers.

In short, I feel empty and hopeless. What are your toughs, are you going trough something similar?

Software Engineer
Nerdious Geekius

The elusive Software Engineer is a nocturnal creature, rarely found at their desks before 10 or 11 in the morning, but often staying late into the night. They dislike being interrupted while at work, and it theorized that their penchant for twilight hours is an evolutionary adaptation to reduce breaks in their trance like state of coding.

Not surprisingly, Software Engineers are solitary creatures, except for occasional gatherings called "code reviews". In these gatherings, engineers gently pace around a clearing, sizing up each others work. Although occasional battles will erupt, they mostly end without injury and the engineer will retreat to their desk and continue to hibernate.

Fun Fact: Software Engineers have been know to kill each other in brutal fights over identation styles

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

Every now and then I attend to previews with clients, and almost every time the clients make me think : "they can't be so stupid? Can they? And I start thinking that there should be some kind of minimum brain use time to allow people to wake up the next morning."

The worst part for me : the clients should be engineers... They might even have some kind of engineer degree...

Depresing afternoon.

On the bright side, one of my mentoree handled a denied of service error so fucking swiftly! He's amazing!!

I got news for you buddy. The cloud engineers at Amazon are way smarter and better than your idiot staff.

So, I worked away from our software teams and directly with engineers for a few months to examine the capabilities of a new piece of hardware we expected to integrate with. It wasn't necessary that I be shut out from all the other software projects, but my boss decided that I shouldn't go to them. When pressed, he said he didn't want the meeting to be too full.

I studied this hardware thoroughly, and even know the engineers who designed it personally. This is, in every sense of the word, my project.

... So when the product owner asks to meet to discuss another feature around it, my boss decides he should invite the rest of my software team to meet with the engineers. There's some non negligible engineering background behind the tool and associated workflow.

When asked why he invited them, despite me being concerned about lack of focus in the meeting, he said he "didn't want anyone to feel left out".

This is the same man that cost me an entire week of work (and is now costing me my time with the systems experts) because he doesn't want to hurt the feelings of my junior colleagues. He's shown repeatedly that he's just fine excluding me, but heaven forbid my junior colleague feel junior.

I don't think he'll ever realize how much he's playing favorites here. Ugh.

Why would companies ever hire a manager from a non-tech background, at least for managing engineers? After reading @IAmNotARobot's latest rant I just have to ask because it makes absolutely no sense to me. Surely non-tech people should be reserved for managing non-tech roles like sales, HR, and maaaaybe team leads, right? How can you manage someone if you don't understand anything of what they do?

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?

When Google Engineers Made a Speech Synthesis Program, they hadn't figured out a name until:

"What should we name our advanced speech synthesis program"
"Hey bob what are going to order for lunch today"
"Tacos."
"What was that weird movie with the laser bikes that make light walls"
"Tron."
"Bob you're a genius"

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.

Most of the CS engineers don't make it to developers for their server fails in the "internship" beta testing phase :P

I feel like contractor companies are crazy overfunded at the moment..

They keep hiring more people to put on the invoices but everyone seems to be working at 50 capacity at most...

I understand that clients rather overpay contractors than hiring people themselves that they don't need anymore in a few months and can't easily get rid of but dude.. I'd gladly do the job of 3 contractors for twice my salary in this current climate.

Not to mention that the amount of hiring brings lots of underqualified engineers with it.

When engineers get so CS-driven they can’t see simple things 🙃

Another manager messaged me and my boss last night to ask whether he’ll have to expose a certain function to be available in objective c classes (we’re iOS devs and most of our code is in swift, but some older stuff is still in .m files). He said he dug into the lower level code and didn’t see any connections or exposures so he assumes he’ll have to add these. My boss concurred and told him to go ahead and make them available.

Then I showed up with my didn’t go to university brain & searched the codebase for calls to that function from .m classes. There were like a hundred lol, working just fine. It’s already exposed. Neither of them thought to do that.

I watch a lot of coding content these days just to get a feel for what's the message given to freshers or non tech people about the IT industry.

One of the things I immensely disagree with, is the idea that software engineers learn throughout their career. I disagree with the word 'throughout'.

They completely ignore stagnation on the job and also this fact that learning new technology at some point in ur career just wouldn't make sense, effort wise and financially.

Here's something I'll never do - Learn Ruby and then proceed to Ruby on Rails. Because the system wouldn't consider my past experience with NodeJS and Laravel, as a result I would be considered a fresher. So it wouldn't make sense for me to put this much effort and start all over again.

Also, your learning curve does plateau at some point in ur career for a certain amount of time. You may learn new things but sometimes you're only concerned with maintaining pre-built stuff so you don't learn new things.

I know some engineers are motivated enough to learn new things outside of a job. But I just wanted to say this.

If software developers / engineers and various other technical people stop serving banks and governments and become free minded we’re be having our own clothes and food served to us whenever we want and where we want by now.

Fucking capitalism and stupid dickheads.

I think being able to be served by robots in your own house to provide you everything you need is first step for long spaceship trips that can take over galaxies.

Living on this planet is boring as fuck.

The intern beside me just called me to solve an error in PHP.

He wrote:
for($slides as $s){
}

The PHP error message wasn't quite clear:
Fatal error: expected ';' on line 84

How could possibly an intern who's becoming an engineer in IT make such mistake and lose like 1h on an error like that? I even attends one of the best universities in the country

PS:
I know engineers aren't supposed to code, but he's been coding for the past month in PHP and was here just to do that

Phonies: "By doing X for Y number of years and reading things such as blah blah blah"

Kings/Queens, silverback devs, rockstar engineers: "I never got good."

Fucking Android 12 everybody hate it, it's ugly, and what has changed from 11 besides everything you already know. 90% of time pressing volume down + power to take a screen shot will result with volume bar popup first then screenshot, so your screenshot is dirty with volume bar.
They must have adjusted time threshold between how fast/precise press of both buttons is, and now you kind of must be faster and alwas this "I need to press 2 buttons but power must be pressed first"

So fuck you google engineers for ruining Android in every sense. I want revert path, I'm going back to 11!!
It's a first major upgrade that is worse than previous, and those ugly tiles and notifications, cool they are big for what exactly? I still can't operate the phone with hand gloves on the motorcycle with tiny keyboard buttons.

It's like everything is tiny and then grandpa style huge top drawer icons for who knows what with so fucking annoying scrolling text, for fuck sake 11 had is just perfect!

First they make it difficult to do your job. "Only use this server for your testing with twenty other engineers". And when you adjust to that, they change it to impossible. "The server is off limits while demos are on going" .. But you're expected to continue working at full speed ahead.

It's now. The last few months. I'm starting to think I might have to leave developer's career [fucking broken messenger heads.. Made me post this rant prematurely]. I'm starting to feel that I have so much more to offer than just write code, solve minor problems by moving miniature blocks here and there.

As for now I've moved to Performance Engineers. Will see how that turns out. But I have a feeling I won't feel like staying there for long either.

I'm frustrated with an abundance of different *Ops we're having right now. You can spell a random word followed by "Ops", and it's probably a thing. I get that Ops people in general are important but when there is stuff like GitOps, MLOps, FinOps, it gets confusing pretty damn fast. There's no value in all these titles besides "duh" usually, since Ops are just Ops in most situations. They kinda can slap a tracing tool or two on top of your code base but in general they just do Kubernetes (with whatever's hip like Jaeger, etc.) nowadays and that's it. Hell, even "DevOps Engineers", for a majority of cases you'll encounter, are basically just Ops with a misleading prefix since it's just a way people call them nowadays for whatever reason.

I've been on the job hunt for a developer job for about two months now.

Last Monday I finally got my first response. Later that they a recruiter from a local telecom reached out saying they needed software engineers and wanted to meet.

Tonight is my first interview. Wish me luck. Feeling pretty great right now

joined blind today...

i don't see smart engineers...

all i see is a bunch of scared sheep blathering around and complaining and wondering why a job in a capitalist society isn't 100% secure all the time...

get off leet code for once and read a damn history book

🤡🤡🤡🤡🤡🤡

Is it highly likely that, those at high position of management are more greedy of money and posses less ethics and values, than those who actually build the company ie engineers ?

I had seen, it's always the top management who get away from mistakes/ issues but generally it's those who develop the company at core i.e. engineers again, are sidelined or considered responsible for the mistake, when management don't know a shit about anything, or sometimes engineers just follow what management says and management fucks their asses wide even if the management did something wrong.

Who do you think actually build companies/product. Engineers or management or marketers/sales people, who eats fat cheques ??

I remember from silicon valley, when hooli reverse engineered Richards idea and developed their own prototype named Nucleus. Pushed their engineers to beat pipe Piper and when their product turns out to be awfully terrible and extremely fucked like a burned dick with broken balls, they just fired their entire nucleus division

No matter how much social skill improvement I do, it never makes meetings with non-tech leadership type people go as I expect. It is ridiculous how I have gotten so good at communicating, to the point where I can easily manipulate people, but they won't fucking have a straight conversation. Do non-engineers have an inferiority complex every time an engineer slips and says a technical term?

I just sat down in a meeting where I was grilled for answers, and when I went to explain the bigger principal that made them confused, they didn't want that much detail. Wtf? Just tell me you don't care and you want the job done, no need to pretend you want it done together just because you want it done now and your way.

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 have played different roles on different companies and all my mother says to people is that I 'work with computers', same for friends that work on manufacturing or as sales engineers. It really pissed me off.

Saw the Tesla self-driving capabilities? When Elon said he was looking for rockstar software engineers, he wasn't kidding.

First or second week of my first job (internship) and my manager mentions that upper management has decided that a couple of engineers are being reassigned to the new technical writing team, myself included, effective tomorrow with no prior warning, before dragging us into a tech-writing standup.

A couple of hours later my manager apologizes to me for forgetting to tell me about this and asked how I felt about this. I basically answered "not well, this isn't what I signed up for", and credit to him, he pulled enough strings to get me out of that team and back to my actual job. In hindsight I suspect that it was more due to the fact that this internship was a three-way contract with the university and that if I complained they might get their intern supply cut off.

Is there no more jobs for software engineers in market? Because the only thing I'm seeing is layoff, right now!

Microsoft Teams 👎

Luckily most of our company uses Zoom, which is great UX-wise. But MS Teams... What a joke!

I've even been on a call with MS engineers for some Office integration support. Of course, they scheduled a Teams meeting. It was embarrassing how bad the quality and connections were. But likely they simply don't know any better...

So in my org, as far as I can see, senior engineers and normal engineers do about the same amount of work, and the senior engineer is useful at PBRs for bringing up tech points that other engineers might not know about due to lack of experience. Is this a common thing across the whole software business? In terms of responsibilities, I’m seeing pretty much the same amount, don’t wanna sound arrogant here but we never task work etc based on seniority which I like but just want to know if it’s common

Just tried out Jupyter Notebook for the first time. I can see why software engineers wouldn't like notebooks, especially if you intend to actually publish the notebook as code for other people to use (please publish a module that can be imported, not a notebook that has to be hacked to pieces to make it reusable), but it's pretty handy for early prototyping or documentation.

I'm playing around with save-editing for a few GBA games as a personal project, and I used a Notebook to document the save file format with examples.

Stack Overflow people have profound buffallo bullcrap on their skulls, they are some software engineers who have fucked COBOL and BASIC, probably somewhere like NASA, just pondering out where someone post a question. They're probably some etilist cult banging a prostitute while delivering that awful downvote imitating the slap they give the chick during sex. They desire questions such as

"RANDOM_fuck_module_Abdul.method() not working in python" or "how to dock the dock by undocking" (tagged: AWS). Not things like "why does the audio tag not work in a PC but works in w3school tester?" or a genuine programming question. Fuck.

We don't tail recurse or loop abc for k in godfuck loops, huh? We make simple things as: a form, a http request to dell.

I hope there penises get rotten in the hell. Period.
this is just a part of SO.

ok so basically i have 2 emails x and y.
one is an appleId other is a personal email.
but turns out some other person p is using an appleId with my personal email from a year.

here is a fun fact, i created that email id this month.

apple engineers have taken a week and asked for a week more to figure out how an unverified email is used to create appleId

There are too many people that consider software engineering a "job". Anyone else here love the process, people and programming? How do people end up at these bad companies and WHY DO THEY STAY??!?!?! There is so much demand for programmers, designers, software engineers, et al. Such that I do not understand how people stay at these companies that hire people who want to make money instead of code.

Just finished fourth interview with a company (fuck me) for a solutions engineer position (I am a self taught dev that is transitioning to technical roles from a pretty "soft" background with the hope of being in a software engineer role within three years). Anyone have any experience with the solutions engineer role and some advice about it? Note: this IS an invitation to rant about solutions engineers so I know what NOT to do.

Browser are so bloated. Why does it use so much memory?

*Closes 62 tab*

Seriously why?! Damn you modern software engineers for making everything so bloated.

"It is pointless to use just a fraction of the data in a homologation environment"
Those words reveal the truth in our creed.
We work in the deepest of back-ends to serve the front.
No data is true. Everything can be edited.
We are Data Engineers.

And for those words to take hold, a junior must execute a leap of faith, and push a hotfix into production.

So I've been working with this company for like 3 years now, my only issue with it is I'm kinda underpaid (1.3K/month in Italy).

Today I had an interview at another company, like 1km away from this one, and it feels promising, the only difference would be in the products: here I make web-based stuff and VR apps, in the new one, I'd just be there incapsulating AI into other stuff for medical and industrial usage, using python and a lot of other stuff I never used or that I haven't used in the past 3 years or so...

Current company is made of me, boss and dude who works on social medias
New company is 17 people and many of them are engineers, mathematicians... more focused on what I actually do/like to do

Current company would go through quite a hard time without me (hardest projects were entirely developed by me + design/css from boss/other)

What would you do? My dream job is to make videogames with my own ideas (but can't rely on that to earn money)

#include <advice>
using namespace plz;

So I have a soft cozy internship for a large retail corporation, the workplace is fantastic and the people are nice. We run into problems where this company outsources to India for almost all of its programming leaving their "software engineers" to answer emails and support 15 year old applications. This is obviously not the work I want to be doing. I want to create. This company also pays slightly less than average for an entry level programmer. I have one year of college left as well. At the end of this internship it is almost guaranteed that I get a full time offer but I only get 2 months to accept or decline. I feel like I'll say no.

So I guess what I'm asking is, should I turn down the safe first job and go for work that will make me excited in the morning or take the easy soft underpaid email answering job?
Thanks guys

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.

can anyone prove 0/0 = 2

well, in the comments.

Fuck interviewers that ask for your public github repo that you did in your own free time.

Do they also ask structural engineers for bridge designs they made in their own free time....

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!

During my undergraduate studies I had a Numerical analysis course. The lecturer is an old professor who was the dean of the faculty at the time, during all lessons he'd talk about his grand children and how the course is important to us the engineers. Not for a moment did he speak of the material it self... Came the test - 10 fucking questions of prove and solve in 3 hours. Had to learn the course from Indian fellows on YouTube...

I am trying to get my company to support Linux (Fedora) for engineers. Currently we support Windows and Mac. Does any of you have some good reasons for my case to make my argument for the business perspective?

What are some job possibilities for software engineers that are a bit more challenging?

Software Engineering just became routine and with all the hin abstractions during the past years it’s not really a complex job anymore.

Thoughtful about data science but I think I’d get bored with that as well after a few years.

Looking for ideas with:
- technical skills
- have a lot if responsibility
- at least same pay

Would be interested in e.g. investment banking but that seems far out of my league (education wise)..