I'm not sure what to think of this. Buzzwords everywhere I guess.

I AM SO FUCKING TIRED OF BUSINESS MOTHERFUCKERS USING TECHNICAL FUCKING BUZZWORDS LIKE THEY KNOW SHIT ABOUT TECH! THEY TRY TO BE FUCKING SMARTASSES AND ARGUE WITH DEVELOPERS LIKE GOD KNOWS WHY THIS FUCKING DOUCHE IS NOT THROWN IN /dev/null YET!

Ugh. He try to sound smart and argued with a unity game developer why the dev is not using "react" and "redux" in his game, purely because "since its the hype in 2016"... I was like really nigga?? FOR FUCKS SAKE Do some research before you say! Then he argued with a senior full-stack web developer on why they're using ES6 and not ES7, purely because he heard that ES7 is newer. When we try to explain we're not using decorator syntaxes since we use pure functions in our codebase, or how we haven't installed any ES7 babel plugins to transpile our code, he kept saying ES7 is newer and cooler and we must use it somehow... More to rant but i am fucking tired right now...

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

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

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

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

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

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

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

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

So. A while ago I was on OkCupid, trying to find the Pierre to my Marie Curie (without the whole brain getting crushed under a horse carriage wheel obviously) and I decided the best way was to have my profile lead with my passion for technology. It turned out pretty unique, if I do say so myself.

At the end of it, I amassed some interesting and unique messages:

- A Java pickup line (that I never responded to. Yes I'm a very basic Devranter)

- A request to turn the man's software into hardware (to which I politely informed him that this was scientifically impossible unless a reader proves me wrong)

- Another impossible request to turn his floppy disk into a hard drive (how outdated too, why not HDD to SSD for faster speed amirite? That was awful don't mind me)

- A sincere request to help troubleshoot a laptop (Honestly I would've helped with help requests but this is a dating site...)

- A sincere request to help debug a student project followed with a link to a GitHub repo

- Another sincere request with studying for a computer exam

- And lastly, my favourite: a sincere job offer by a guy who went from flirtatious to desperate for a programmer in a minute. He was looking for *insert python, big data, buzzwords here* and asked me for a LinkedIn. I proceeded to inquire exactly what he wanted me to do. He then asks me to WRITE a Python tutorial and that he would pay a few cents per word written so he could publish it. Literally no programming involved.

Needless to say I went to look elsewhere.

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

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

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

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

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

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

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

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

A company gave a placement talk in college today.

First, they talked about their company's facts and figures, which no one was interested in.

Second, they talked about Amazon and Jeff's vision, AirBnB and their revolutionary idea, more than their own company and products.

Third, they showed some testimonial videos of their employees and customers.

"What the fuck is going on?" I thought. We were there to get information about a placement test.

Buzzwords started coming in. Machine Learning, Artificial Intelligence, Big Data and what not.

Last 15 minutes, a guy came. He talked about test date, test format and test topics, finally.

An hour and half wasted for 15 minutes of information.

Fuck placement talks.

I can understand (to a point) when non-devs use meaningless tech "buzzwords", but please, as developers, can we just agree not to spout nonsense?!

"Electron is so amazing, it's such a lightweight framework!"

"Django is incredible, it's so agile!"

Agile is a family of development methodologies, and Electron is about as heavyweight as a desktop application can possibly get...

No one fucking knows how to handle/raise errors.

I feel like this is the least talked topic in all fucking programming industry. This shit needs to be tought even more than the fucking SOLID, DRY, KISS, YAGNI and other kinds of buzzwords that fancy devs love tossing left and right.

Basically everyone just does "whatever you dumb error just dont bother me". They will just log/return null/ignore the errors and be in their oblivion with bugs propagating upstream the call stack.

"Throwing errors you say? Ew, why do you want to produce more errors?". Yeah, right, just stick another log/return null/or ignore the fact that the monke calling your function with bullshit arguments.

"But bro it's so difficult and time consuming and it would never happen!" Yes, you fucker! Yes! Programming IS fucking difficult if you want reliable systems! Did you not know that!? Well now you do! Go and fucking learn it!

FUCK!11!1!!

Oh wow, so many memorable co-workers, though typically not in a positive way. I guess the most memorable was this project manager who got his job solely through nepotism. He was a fucking moron, putting it lightly. He would rattle off buzzwords and jargon that he had randomly picked up in a completely nonsensical way, which made him sound even more ridiculous. He didn't seem to notice our blank stares.

Anyway, since he loved to show everyone just how awesome he was, he had to have the latest and greatest laptop. He had some top-of-the-line model which cost an insane amount of cash back in the day, but of course he got bored of it when something better came out six months later. So he decided to sell his old laptop.

Now, this was his personal laptop he was selling but we were about three months away from launching a top-secret project which had a seven figure budget and a lot riding on it. So what did this absolute goose do? He sold his laptop unformatted with a metric shit ton of confidential files and documents on it. As fate would have it... he sold it to someone who just so happened to work for a competing company.

Cut to about two and a half months later, around two weeks before the launch of this massive project, our competition comes out with something incredibly similar and beat us to market. Aghast, senior management then found out that they had obtained a treasure trove of confidential information from this numpty's laptop, handed to them on a silver platter.

The following Monday, with a sombre mood in the office, this guy cheerfully comes in through the door and is immediately yanked into the boardroom by management. What followed was around thirty minutes of brutal, relentless, non-stop shouting, table- banging and obscenities. When it finally stopped, the door quietly opened, this guy walks out as white as a sheet, turns towards the exit and left the building.

We never saw him again.

(tl;dr) Protip: never take internship/training/job offers from startups.

Fucking piece of shit startups hiring innocent interns from University, hoping that they are full stack developers to build their shit website.
"I will throw challenges at you".

You fucking scum, I need a proper mentor to teach me something which is not my fucking domain. You expect me to know nodejs and reactjs, and if I don't know that means there's something wrong with my learning process?!!

I'm looking for an internship which basically means that I get company exposure to proper training unlike being your fucking slave, you uncultured swine.

Seriously, recruiters, these days jack off to google buzzwords.

Anyone else here with anxieties, depression or what-not? I feel this could get heavy, but I feel this is the only place I could write this. So...

My 18-month-long programming course is slowly coming to an end. Time has come for us to be sent out to job interviews at various companies.
Every single time an interview comes up, I feel the exact same mix of my inconfidence, constant anxiety, "I'm gonna throw up", impatience and whatever else is there in my head. I figured it would get easier with each consecutive interview but it hasn't.
The questions they ask make me sick. The atmosphere is unfathomable. Robots are more humane.

- Why do you want to work with us?
I need money for my meds and something to down them with? I willingly put myself through this shit to become a corporate slave, what else is there to say? I can only hope I'll be writing any code here.

- Where do you see yourself in 2-3 years?
Far away from anything remotely related to an HR department of any sort?

- Had you been a fruit, which one would you be? Whatever would come out of my tears blended with semen? What the fuck is even that question?

Of course those aren't my actual responses, but conjuring the IRL ones to finish the process is a serious burden. And those are only some HR ones. After this barrage of questions they want my lifeless, flaccid body to write code. I mean ok, it's a software dev gig, but I already gave all I had on self-clairvoyance.

We'll be in touch!

Is there a strategy you guys have when you go to an interview? Any tips for taming the acrid beast running around in your brain? Is it too much to talk with a human in a humane language without "15 buzzwords to make the recruiter moist"?

How bad it feels when it work in a place where Agile and DevOps are mostly abused buzzwords.

Forced doing "scrum" with:
- half of the team providing endless daily reports instead of focusing on the 3 questions
- a scrum master that is barely reachable
- a product owner that would not even make a decision
- a sponsor that pushes us to go faster regardless of current technical debt (it's important to look good to other sponsors!)
- doing all possible scrum ceremonies with no value added
- not even estimating stories
- not even having accurate description in stories. Most of the time not even a description.
- half of the team not understanding agile and DevOps at all

Feels so good (not). Am I the one in that boat?? ⁉️

What's the point of doing scrum if implemented that badly?? 😠

Overheard: "I'll need to get in touch with my Infrastructure Architecture Innovation Team"

😂🤣😅😂🤣😅

Why not just call them team buzzwords. Omg.

How the fuck is CLI a skill for job seekers?! And what's a Toolbox?
Apparently, recruiters write any Buzzwords they hear of! CLI is not even a Buzzword. How did it get there?

Why is the interviewing process becoming worse over the years?

About 2 years ago I applied for a company and got into 2 interviews: one with the hr to see if I am bsing them and one with the tech people, to be sure I am not using buzzwords without context. Pretty straightforward, could be done in a single interview IMHO, but it's making me waste max 2 weeks.

Fast forward to one year ago: 1 interview with the hr, 1 interview with the tech people, 1 interview with CEO (why? Just.. why?)

Fast forward to today: 1 interview with hr, 1 interview with tech people, 1 interview with the CEO (again... why?), 1 coding assignment which "it's only going to take a couple of hours" and punctually has either poorly documented APIs to rely on or has trick questions/points. So "it takes a couple of hours", but if you want to pass it you need to spend a day on it... (and let's add that they may be using old docker versions so if it doesn't work cause they are using docker 1.0 and it fails too bad, you lost time for nothing, we are not trying to solve it, you just don't pass!).

Not kidding the last assignment I took and dropped required: external API, testing, don't use CSS libraries and make your own CSS, you must use TS and it was supposed to take "3 hours max".

My question is: why? Why is the interviewing process slowly becoming less of a: "I understand that your code may not be perfect for us but that you are a human being able to reason and adapt your code to our standards" and more of a: "You must do everything PERFECTLY and we don't give a sh*t about your time, start giving us your free time and then we see if we want you."

I just keep giving up after I analyze the assignments, cause a part of my brain thinks that if this is the way a professional relationship starts it's too easy to foresee weekend shifts and lots of overtime cause some manager thinks that "come on, it just takes a couple of hours!"

Today, I looked at my company’s job description of my own profile.

Shit is full of buzzwords.

Wonder if that’s the case everywhere. Gives me some confidence to just apply to jobs without worrying about ticking all the points in the descriptions.

(For those wondering whether I did not see the description while applying for my current job.. actually, I saw it but didn’t take it too seriously because I just wanted to get a dev job.)

I don't understand why there is such a hypocritic professionalism in tech industry.

In the careers page ,these companies show smiling people, party images , slides and shit. And while selecting resumes, they want to scan buzzwords to select a particular candidate and hate "actual" introductions.

Like, how would you like to meet someone in a bar , who introduces himself as " a super enthusiastic 10x engineer and a tech enthusiast with a knack of building scalable and industry recognized softwares in x tech for last y years". Dude, introduce yourself as a human not a bot.

There is a clear difference when we are talking about personal stuff and when we are talking about tech in real life, why not maintain that in your resume?

But no, just write a single sentence in first person p.o.v and next thing you know, you see tons of LinkedIn post about "how to write a 'professional' resume"

Lead: alright people what are your ideas and updates for this page refactor we've been talking about.

dipshit: Alright guys, I've done a quick awesome prototype that I really like...

dipshit: *starts to speak super fast* (I catch words about function composition, clean, no side effects, speed, efficiency. Basically a string of brogrammer buzzwords.)

me: what did you mean by that? How does it work?

dipshit: *basically repeats the same drivel*

me: uh..ok I don't quite understand

everyone else looks confused.

me: ok since you've done a prototype, we take a look at it later

*** After meeting, looks at code ***

It was COMPLETE GARBAGE. He used 1,500+ lines of js in 17 files to make what was essentially a simple 2 item list.

We were looking at a way to overhaul the entire page, he "refactored" maybe perhaps 5% of the page.

There was absolutely nothing clean / functional / composable about this monstrosity. It was as if he read chapter 1 of a book on functional programming and decided he understood enough to call himself an expert.

WHY THE FUCK ARE YOU STILL HIRED?

HOW DO YOU CALL YOURSELF A DEVELOPER?

YOU ARE SELF TAUGHT, DISS PEOPLE WITH FORMAL CS/CE DEGREES AND YOU PRODUCE TRASH CODE?!

ARE YOU SO RETARDED THAT YOU DO NOT RECOGNIZE HOW STUPID YOU ARE?

Please die in a fire, along with your jock attitude and unprofessionalism. Take this worthless junk unfit to be called code with you.

"Java and C++ Spring Boot and Angular Ansible Jenkins Azure Hosting"

nice, a stack for boomers lost in the 2000s

stop it. just stop it.

"Some other tech buzzwords we use"... yeah, "typescript" and "big query" are not "tech buzzwords" they're literally the names of languages and/or tools

tell me you're an HR rube without telling me you're an HR rube

😩😩😩 <- love this one, literally called "weary face"

Why are project/tool webpages so useless...?

I mean, whenever I hear of a new tool/project I google its name. Of course, its dedicated webpage pops up as result #1. And EVERY TIME I find them looking nice, but quite confusing, riddled with all the buzzwords, nice phrases, promises of a better tomorrow,... but I'm yet to find a tool's webpage that explains what's that tool for and how to use it at least half as concisely and clearly as that tool's README.md in its GH/GL repo.

I mean, I can read every single word in the webpage, look at every picture/diagram, every fancy gif and still in absolute majority of cases I have no clue what that tool does.
Then I go to its GH/GL repo, read the first 2 sections of its README.md (takes me what, 2-4 minutes?) and I know all I need to now about the tool.

What's the point of those fancy webpages apart from containing docs and an SEO-tuned link to a README.md...?

Useless waste of storage and computing power if you asked me.

I've been trying for the last 3 months to land my first development job. I have a good (over 3 years) amount of experience, but no industry experience and no degree. So it's been a uphill battle. Currently working at a call center making garbage and most of my time and energy is invested into this. Currently am not mobile so most of my money is being geared towards that. It's just frustrating to see all these over glorified job postings that ask so much for just entry levels. I haven't even gotten a damn interview, I feel like in houston it's either you have a degree or you are not even considered for just a fucking interview. If I can get at least one they will be able to see my drive, persistence and skills that have been developed overtime. And fuck recruiters, have been interfacing with them over linkedin and not one of them seemed eager (initially yes) to land me an interview. Most of these fucks don't even fucking understand the technology or buzzwords that are on the job posting. If I were a recruiter I would at least put a little research into what the different technologies are so the process will seem less abstract. The tech will have more meaning and maybe I would be able to get a better success rate with clients if I knew what was really required of them. Not just looking at xyz and seeing if client has experience with them, but really see if they know what they are; that way I will have more confidence sending them into an interview. But of course that's not how it works. "Oh yeah Java and javascript are very similar"... get the fuck out of here.

Block chains, i think distributed databases is going to go big.

So we're doing this contract work for this other company and the project is just an overcomplicated piece of garbage where they shoved every buzzword technology into it just because. I managed to get the code just about organized and functional on our side of the contract and it was looking up when suddenly the management decides "we had a rough start, lets start over, learning from our mistakes"
So I was thinking "cool, there were a lot of problems with this overcomplicated pre-optimized stack, surely we can only do better".. oh boy how naive I was. See Im not the guy in charge of the infrastructure (unfortunately) and really the project structure across this huge multi service project is a free-for-all kind of management.. so we had a call on friday where they explained how the new structure should be built... 3 new technologies, more micro services and even worse dependency tree later I was contemplating suicide on the spot.

I tried to make this shit usable and efficient and all my fucking work went down the drain in a single day of these fuckers throwing more buzzwords at the problem... I can't even get a new empty project started without browsing our huge 100+ repo project git for which dependency Im still missing to even run it...

I fucking hate this retarded piece of crap project and I hope every "manager" and "developer" with an exception of very few chokes on a cock...

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

can someone tell me the buzzwords and trends currently in the market? i want to leave the company, because if not, i am going to commit suicide.

So I had this conversation yesterday while fixing yet another Windows laptop for someone else.

Other Guy = OG
Me = Me (Duh)

OG: So what are your plans after your apprenticeship?
Me: Uh, I'll probably start somewhere that's e-commerce related, kinda like my current company but somewhere else.
OG: Uh have you thought about being your own boss?
Me: Well yeah, but I wouldn't know how to attract customers and shit

-- This is the moment shit gets real
OG: OH BTW I heard that Germany is lacking AI developers, you should do that! It earns you shitloads of cash!
Me: Uhm.. well, that might be true b-
OG: There's no but dude, it's free money, you're smart.. I mean you can fix any computer, right? AI will be just as easy
Me: It's not like-
OG: Duh, don't make yourself look so bad I know you can do it!
Me: B..But I'm not interested in it at all
*silence for 5 seconds*
OG: Well.. I guess you do you then

After that we continued to have random chit-chat about his job and experience (He's a mechanic)

God I hate when people throw buzzwords around and try to convince other people to do what *they* want.
No, I don't want to develop a structure of 1000 ifs/elses, I'd rather keep doing what I'm doing, thanks!

Has anyone been at tmrwconf ? Anyone knows more about this? Apparently a not-very-cheap conference where some speakers talk about the buzzwords AI BLOCKCHAIN METAVERSE and all the current "trends". This shit is available from may 11 to may 13th and the cheapest ticket is $70 all the way up to $700 per person.

What the fuck? Typical for web3 conmen. Has anyone been to this conference before, is it worth the money?

hey, so i have recently started learning about node js and express based backend development.

can you suggest some good github repositories that showcase real life backend systems which i can use as inspiration to learn about the tech?

like for eg, i want to create a general case solution for authentication and profile management : a piece of db+api end points + models to :

- authenticate user : login/signup , session expire, o auth 2 based login/signup, multi account login, role based access, forgot password , reset password, otp login , etc

- authorise user : jwt token authentication, ip whitelisting, ssl pinning , cors, certificate based authentication , etc (

- manage user : update user profile, delete user, map services , subscriptions and transactions to user , dynamic meta properties ( which can be added/removed for a single user and not exactly part of main user profile) , etc

followed by deployment and the assoc concepts involved : deployment, clusters, load balancers, sharding ,... etc

----

these are all the buzzwords that i have heard that goes into consideration when designing a secure authentication system for a particular large scale website like linkedin or youtube. am not even sure how many of these concepts would require actual codelines and how many would require something else.

so wanted inspiration from open source content to learn about it in depth, replicate and create new better stuff if possible .

apart from that, other backend architectures like video/images storage system, or just some server for movie, social media, blog website etc would also help.