I'm all for enhancing the user experience. To some extent, making the UI get out of the way to focus on getting things done is admirable!
But it's absolutely *NOT* acceptable to absolutely change how established convention works.
For example, clicking a link should not perform a state change. Use a flipping button!
Checkboxes should not act like radio buttons!
(apparently non-interactable) text should not perform actions!

Due to Coronavirus (COVID19) all TCP applications are being converted to UDP to avoid handshake.

Me trying to find the shutdown option on Mac after being raised on windows..

On a serious note, most developers really don’t code complex algorithms all the time. The bar for interviews is way too high— to the point that most people get discouraged from pursuing a career in IT.

Ass licking and creating tests for the sake of code coverage

Does anyone else fantasize about giving up programming and go live in a jungle or doing other things that require more physical effort?

I've been learning carpentry, farming, DIY power generation etc. The goal is to be self-sufficient and go live in a fucking jungle someday. Or legally buy some cheap land far from the city and automate the shit out of it. No wait, I'll just live there as a normal farmer and write code if I feel nostalgic or something.

I think anyone other than me could have expressed that better.

The guy after me.

You may know I love to hate tests. Well not the tests actually, what I hate is the TDD culture.

DBMS schema in my app dictates a key can either have a value, or be omitted - it can't be null, and all queries are written with that in mind (also they're checked compile-time against schema). But tester failed to mock schema validation, inserted a bunch of null keys with mock data, actually wrote assertions to check those keys are null (even though they never should be), and wanted me to add "or null" to my "exists" queries.

No, we don't need more tests, and you're not smart with your "edge cases" argument. DBMS and compiler ensure those null values can never exists in our DB, and they're already well tested by their developers. We need you to stop relying on TDD so much you forget about the practical purpose of the code, and to occasionally break from the whole theoretical independent tests to make sure your testing actually aligns with third-party services some code uses.

And no, we don't need more tests to test your mocks, and tests to test those test, and yo dawg, I heard ...

The difference between small and large companies is astounding when applying for jobs.

Small: "What can you do?"
Big: "What do you look like and speak like?"

Yeah.... I want to confess i like light themes better. Anyways the colour/theme of your editor does not make you a good programmer.

When a normal person says "IMHO", it means "In my humble opinion"

When a programmer says "IMHO", its means "You are wrong".

How many of you already feel you have wasted one week of 2020?

For fucks sake, just because you don't know anything besides JS, you don't have to constantly complain how it's "so fucked up"!

Yeah there's a lot of frameworks. So what? Python has 50+ wsgi frameworks just for server-side apps, Linux has literary hundreds of desktop environments, C++ has over 30 actively-developed UI frameworks, and let's not even get started on CMSs or game engines. And each language comes with its own dependency management or two, NPM discourages static linking & bundling dependencies until the very end, while some others only recommend dynamically linking widely-available dependencies & always bundling the remaining ones.

Software development is constantly evolving, and for most time there's no right or wrong approach. And when one approach is chosen over another, there's a reason for that. Imagine you just found a perfect library for your use case, but some idiot decided to only offer minified code with bundled jQuery? Or a different idiot made it impossible to have multiple versions of a dependency on your system without resorting to one of various third-party hacks?

Every language has a ton of various frameworks & libraries that ultimately do the same thing, every language has a bunch of design choices you probably don't understand at first, and every language was made with a purpose and the fact that you're using it proves it achieved that.

Last but not least, all devs had to learn about quirks in various languages, and they're fucking tired when someone who barely knows a language tries to act smart going "ahaha how the fuck 0.1 + 0.2 isn't 0.3".

In a time where a web dev is expected to know, well.. everything... Backend -JAVA, python, nodejs and C++ would be great.
Front- angular, react, other 10 libs
DBs -sql, mongo, redis, elastic, kafka, rebbitmq
Also be devops on the side with AWS and docker kubernetis and more stuff

How the f is that possible?

In my real job for the last couple of years and different companies, I usually use 1 language/framework & 1 main DB.. and although it's possible in some companies, but in mine, ppl dont get access to AWS etc..

So let's say there's me.. a server side dev for years.
So I decide to be better and learn Golang.. cool lang, never needed in my job, after few days of not using it I forgot all I learned and that was it.

Then I realized I gotta know some frontend cause everyone want a fullstack ninja nowadays.. so I tried Vuejs.. it was amazing .. never got to use it at work, cause i was a backend, and we didnt use frameworks on our products back then..
Also forgotten.

Then I decided to learned nodejs, because this is the coolest thing ever.. hated it, but whatever... Never got to use it at work, cause everything was written in other lang which the whole team knew... Forgot the little i knew.

Then I decided, its time to see what Angular is, cause everyone started using it... similar idea to vuejs which i barely remembered, but wow it's a lot of code to remember, or I'll have to google everything.. so I went over it, but can't say i even learned it.

Now Im trying to move on to python, which, I really am learning in depth.. however, since I dont have real experience with it, no one gives me a shot at being a python dev, so again i feel like I'm trying to memorize syntax and wasting my time..

Tired of seeing React in all job ads, i decided to have a look what's that all about.. and whadoyaknow... It's fucking the same idea as vue/angular with again different syntax..

THIS IS CRAZY!

in how many syntaxes do i need to know how to make a fucking crud api, and a page with same fucking post form, TO BE A GOOD PROGRAMMER?!?

Add azure, AWS, Jenkins, docker, ui path

2019 is full of shit.

continued…
I'm In Canada. A woke HR lady hires an African guy despite him plagiarizing code and lying through an interview. First day he surfs soccer websites so I confront it and HR lady basically calls me a racist and to watch my back.

A second African new-hire comes into the office today and he seems quite capable in an area of specialization for our team. So I ask if we can have him on our team because he has skills. The exec decides to look at the costing for him and goes, "HOLY SHIT WHY ARE WE PAYING ANYONE THAT MUCH?" She looks at the résumé of the new guy and finds out that he is only at intermediate level in his specialization. So I say, "It could be worse. The other guy flat out lied through his interview and he got hired anyway." I forward the emails where I recommended against hiring the other guy and why.

My exec, who is a company stakeholder, opens the pricing list for recent hires. It is obvious that if you are not not white you get paid way above market value for your skill level. Exec is pissed off on a level I never knew was possible.

We make a call from the board room only to find out that the head of HR (also an executive) is driving this. My exec tells me to give her the room. The yelling was so loud everyone could hear what was said from outside the boardroom. At one point the HR lady says, "Just because we could get them cheaper doesn't mean that we should… We pay that much because it is 'the right thing to do'." My executive goes completely silent for a few seconds then in a super aggressive way says.

"…I am going to have your FUCKING head for this. Then I will make sure that you NEVER get a job in HR again for the rest of my natural life. ONLY ONE of us will survive this. YOU are the one pissing away profit. So get ready because I'm going to drown you and your team like a bag full of unwanted puppies." Then she hung up the Polycom. She came out about a minute later and kicked the office manager out of his office and sat there all day making calls and sending emails.

https://devrant.com/rants/2337768/...

FUCK OPEN OFFICE ENVIRONMENTS
FUCKING GOD DAMN

Git ...

I just noticed I'm programing while wearing a black hoodie, using vim.
I hope nobody uses me for making shitty stock-photos.

Grunt, gulp, bower, webpack, rollup, yarn, npm, requirejs, commonjs, browserify, brunch, rollup, parcel, fusebox, babel,
wrappers for bundlers, frameworks on frameworks, then for css, theres scss, sass, less, stylus, compass, and for templates, handlebars, mustache, nunjucks, underscore, ejs, pug, jade, and about five billion other word-salad tools, all with their own CLIs, each in some way building on npm, but with their own non-congruent little syntax, like no one realized they were reinventing the same problems introduced by domain specific languages, most happy to announce "configuration takes a little time, but it's worth it!"

No, it's not. Just stop people. Just stop. You're not doing anyone any favors by creating another lib, all you're doing is tooting your own horn and self promoting. Use what exists and stop creating more shit for new people to learn, to add to the giant clusterfuck that is the 2019 hotmess known as "web development."

You're not special. You're not important. You're lib or tool will be famous for 15 minutes and no one cares what you've made.

If you want to contribute to web development, do us all a favor and contribute to global sanity by kindly deleting your contribution and any plans to contribute new solutions to problems that have already been solved.

A nice UML diagram of a typical Electron application

Is it just me or are all the stoopid people in middle management? Why do these clueless people always impose completely nonsense requirements? Like 'You have to process all entered client data but you are not allowed to store it, nowhere, because of GDPR, storing data is evil!' But when customer logs on all his not persisted data has to be pushed to the frontend immediately. WTF THIS IS CRAZY

"Sometimes there is no need to be either clever or original." - Ivan Chermayeff

"Coding a first person openworld mmorpg in 24 hrs"

Unpopular opinion: Laptop stickers are horrendous.

Me : Who wrote that monstrosity of code ? I’m going to kill someone!
Git blame !
Me : Oh never mind, it was me 4 yeas ago.

I really don't like this trend of building command line applications for controlling some <buzzword> cloud app or <buzzword> framework.

Why should I need or want to learn the exact wording of your gcloud command, or the path to your Ng cli, or some ass-backwards AWS search syntax when I can get the same functionality from your web app, where I can use my FUCKING EYES to work out where the "Create Instance" button is and how to click it!!!??

Stop pushing your shitty python monolith of a client where possibilities for the above task range from:
- google-cloud instances --add "subfjfechye thiq"
To
- gcloud /create /type=INSTANCE "rogdhyuffhue"

"BuT iT mAkEs iT MoRe aUtomaTaBLe"
I DON'T CARE. What is the point when I can use a proper programming language instead of bash, with actual code-completion and syntax rather than the horrendous excuse for a suggestion system that is the Tab key where it probably doesn't even work in the first place and I have to copy and paste some mysterious dbus command buried in an old documentation page on the Wayback Machine using a utility I don't have installed and a broken URL?

Go away.

Shout out to those who put their actual job title on LinkedIn and not some bullshit line like

"Recruiting inspiring recruiters to recruit inspiring recruiters"

Do you ever look back at something you built a while ago and think "oh hey, that's cool.... how the hell did I do that"?!