Fuck the memes.

Fuck the framework battles.

Fuck the language battles.

Fuck the titles.

Anybody who has been in this field long enough knows that it doesn't matter if your linus fucking torvalds, there is no human who has lived or ever will live that simultaneously understands, knows, and remembers how to implement, in multiple languages, the following:

- jest mocks for complex React components (partial mocks, full mocks, no mocks at all!)
- token cancellation for asynchronous Tasks in C#
- fullstack CRUD, REST, and websocket communication (throw in gRPC for bonus points)
- database query optimization, seeding, and design
- nginx routing, https redirection
- build automation with full test coverage and environment consideration
- docker container versioning, restoration, and cleanup
- internationalization on both the front AND backends
- secret storage, security audits
- package management, maintenence, and deprecation reviews
- integrating with dozens of APIs
- fucking how to center a div

and that's a _comically_ incomplete list; barely scratches the surface of the full range of what a dev can encounter in a given day of writing software

have many of us probably done one or even all of these at different times? surely.

but does that mean we are supposed to draw that up at a moment's notice some cookie-cutter solution like a fucking robot and spit out an answer on a fax sheet?

recruiters, if you read this site (perhaps only the good ones do anyway so its wasted oxygen), just know that whoever you hire its literally the luck of the draw of how well they perform during the interview. sure, perhaps some perform better, but you can never know how good someone is until they literally start working at your org, so... have fun with that.

Oh and I almost forgot, again for you recruiters, on top of that list which you probably won't ever understand for the entirety of your lives, you can also add writing documentation, backup scripts, and orchestrating / administrating fucking JIRA or actually any somewhat technical dashboard like a CMS or website, because once again, the devs are the only truly competent ones - and i don't even mean in a technical sense, i mean in a HUMAN sense of GETTING SHIT DONE IN GENERAL.

There's literally 2 types of people in the world: those who sit around drawing flow charts and talking on the phone all day, and those WHO LITERALLY FUCKING BUILD THE WORLD

why don't i just run the whole fucking company at this point? you guys are "celebrating" that you made literally $5 dollars from a single customer and i'm just sitting here coding 12 hours a day like all is fine and well

i'm so ANGRY its always the same no matter where i go, non-technical people have just no clue, even when you implore them how long things take, they just nod and smile and say "we'll do it the MVP way". sure, fine, you can do that like 2 or 3 times, but not for 6 fucking months until you have a stack of "MVPs" that come toppling down like the garbage they are.

How do expect to keep the "momentum" of your customers and sales (I hope you can hear the hatred of each of these market words as I type them) if the entire system is glued together with ducktape because YOU wanted to expedite the feature by doing it the EASY way instead of the RIGHT way. god, just forget it, nobody is going to listen anyway, its like the 5th time a row in my life

we NEED tests!
we NEED to know our code coverage!
we NEED to design our system to handle large amounts of traffic!
we NEED detailed logging!
we NEED to start building an exception database!

BILBO BAGGINS! I'm not trying to hurt you! I'm trying to help you!

Don't really know what this rant was, I'm just raging and all over the place at the universe. I'm going to bed.

With all the major library/framework overhauls in the JS community, I feel we may need to start versioning in our resumes:

angular@2.4
react-router@4.0.0-alpha.5
jest@19.0.2
..

I'm a self deprecating PHP developer.

..there's a decent pun in this thought, somewhere..

Deprecation. What’s that?

Me: XYZ library just announced that they will stop support for their version 3. I will update our code to use the latest version. It'll probably take 10 hours because we use it pretty extensively.

Manager: Okay. While it's updating, could you work on the ABC feature?

Me: ... no, because I'll be working updating the library.

Manager: Oh so you gotta work on it? I thought it would get updated overnight like my iPhone.

I've told the same story multiple times but the subject of "painfully incompetent co-worker" just comes up so often.

I have one coworker who never really grew out of the mindset of a college student who just took "Intro to Programming". If a problem couldn't be solved with a textbook solution, then he would waste several weeks struggling with it until eventually someone else would pick up the ticket and finish it in a couple days. And if he found a janky workaround for a problem, he'd consider that problem "solved" and never think about it again.

He lasted less than a year before he quit and went off to get a job somewhere else, leaving the rest of our team to comb through his messy code and fix it. Unfortunately, our team is mostly split across multiple projects and our processes were kind of a mess until recently, so his work was a black box of code that had never been reviewed.

I opened the box and found only despair and regret. He was using deprecated features from older versions of the language to work around language bugs that no longer existed. He overused constants to a ridiculous degree (hundreds of constants, all of which are used exactly once in the entire codebase, stored in a single mutable map variable named "values" because why not). He didn't really seem to understand DRY at all. His code threw warnings in the IDE and had weird errors that were difficult to reproduce because there was just a whole pile of race conditions.

I ended up having to take a figurative hacksaw to it, ripping out huge sections of unnecessary crap and modernizing it to use recent language features to get rid of the deprecation warnings and intermittent errors. And then I went through the same process again for every other project he'd touched.

Good riddance.

A certain, reasonably sized company had a large in house payment system to handle all their client purchases that was developed many, many years ago. All the devs that developed it had left, and as it "just worked" they hadn't seen fit to get anyone to update or maintain it since.

That was all fine until it suddenly (and completely) stopped working one sunny afternoon.

After paying a small fortune for one of the original devs to come back and look at it, turns out the payment API it was based on had been retired. Warnings of deprecation had been sent out 18 months prior, but they had just been ignored, as the secretary receiving them after the devs left had no idea what it meant.

Gonna make a pull request for Project!

"How to Project:

npm install
npm test
npm run start"

npm install: warning, warning, deprecation, warning

npm test: 30 tests, 15 failed

npm run start: error, C stack trace

Pull request status: on hold

Already hate everything about this job. Not even a week has passed.

PHP5, CakePHP 2, No git, no nothing.

Self-deprecation 2.0

NODE 18 MOVES INTO MAINTENENCE TOMORROW

...do you know where your legacy software is?

This was a free public service announcement brought to you by your favorite 🎪🤡🤹‍♂️

DRINKING GAME.

Start package installation in any NodeJS based project.

Drink every time you see a deprecation notice.

When you add a deprecation warning before you leave for vacation... A week later.

unexpected and honest npm deprecation warning. very honest

Was training a model for an hour on paid GPU after which it showed a deprecation error and crashed my Jupyter notebook.

Fool! Your code ain't written yet, but I reckon it's already bound for deprecation.

Have my projects compile without a single warning.

The road will be long, and deprecation warnings will pounce at me, but I shall prevail.

Okay, honst question:
What the fuck is up with all that self deprecation?
I am not talking about the usual irony that comes with certain stereotypes about being a developer.

I am talking about people telling themselves that they are unable to socialize, find a girlfriend or generally justifying bad things just because they belong to a certain group.

It's not the 80s. Software devs and nerds in general are not all social outcasts anymore. I don't understand how some people can just "accept their fate as a dev" and act as if anything is keeping them away from social success.

What's your take on this issue?

Java 17 and I see methods in the API that apparently were deprecated back then in Java 1.1! Shouldn't deprecation be the precursor to being eventually removed? Or is backwards compatibility so much important that is ok to have shit in this limbo state for decades?

API changes. Customer downloads newest version of dependency, and breaks my software. Why? Because the devs making the dependency don’t phase anything out with deprecation, just poof. So then I’m up all night making a patch so I don’t have to deal with set client.

Anyone else working on projects to remove flash from their projects? Anyone not going to get it done in time? What are your work arounds?

Just got placed on a project to help remove flash from a proj and there's no way this is going to get done. I looked up when they announced deprecation and that was in 2017.

I find it laughable the company waited to the last minute to do this. Obviously they didn't deem this important enough to do ahead of time so I see no reason to work OT for someone else's poor planning.

Just started Online Banking at my bank. Checked how much money I have and what I can do on the website.

Afterwards I opened the dev tools and see that there is a js warning. So I open the console and the fucking first thing I see is: Loglevel set to INFO. WHAT THE FUCK?!?

Other things I found out:
API Endpoints are logged here. Two deprecation warnings for a function used. A warning about a deprecated service used.

The log level is now set to WARN. Several more deprecation warnings for the framework from before.

The fuck is this?

Why the fuck does Android's SyncAdapter stop working without ANY notice since API level 26 when available storage is low?

They fucking deprecated the system-wide broadcast that the storage is getting too full to properly work. And there's no replacement!!! 😠 No callback. No exception. Nothing. You ask the SyncAdapter to sync and it will just not do it until some storage is freed.... 😭

Has anyone ever installed a NPM package without seeing deprecation warnings? 🤦‍♂️

a deprecation *warning*. we IGNORE warnings. if they actually want us to do something about it they need to call it a deprecation error. and also probably prevent compilation. virtual smoking coming from the emulator wouldn't hurt either. if they expect action on these things, they're going to need to do better than warning.

When I say "error in an async function" you say "no stack trace"!

"Error in an async function"!
"No stack trace"!
"No stack trace"!
"Error in an async function"!
"Unhandled promise rejection DEPRECATION WARNING Unhandled promise rejections will be shoved up your ass in node v7.coffee.9.10.666."

As I dismantle the infrastructure for a now dead project I once worked very hard to main, I find myself oddly emotional about it. I can't help but feel a since of loss. Goodbye friend.

Google decided to deprecate the ProgressDialog class in Android O (26). Now I have to deal with all those deprecation messages in Android Studio!

From the docs: "ProgressDialog is a modal dialog, which prevents the user from interacting with the app. Instead of using this class, you should use a progress indicator like ProgressBar, which can be embedded in your app's UI. Alternatively, you can use a notification to inform the user of the task's progress."

They also bugged the Toolbar! Nice.

Fuck JavaScript!

Seriously, it's always like this:
> "Hey, look <module name> seem cool, let's try it!"
> Find a tutorial
> Tutorial is 3 to 6 months old
> Should be good
> Everything is deprecated
> Come on...
> Back to C I guess.

It's moving waayyyy to fast.
It's frustrating...

Ansible be like:

[DEPRECATION WARNING]: The sudo command line option has been deprecated in favor of the "become" command line arguments. Yadda yadda yadda yadda yadda...

Me:
# grep -rnw . -e 'sudo'
#

Then why the fuck do you keep yelling at my face?

Hating WooCommerce at the moment. Have to update a private CC payment gateway plugin to do tokenization and subscriptions. The examples are pitching errors and deprecation notices, not all steps are being shown, and the example plugins aren’t providing any useful hints, either...

Last thing I need to deliver before Christmas; looking to be a long night...

It's pussy-assed mass hysteria at its best. Social media and the overall deprecation of quality life for the human race is what's caused this. Fear takes its toll in many ways, and this is an incredibly forceful way of engineering a "Big Brother" effect on the World to increase the sale of products and pharmaceuticals based on predictive statistics that nailed down our habits and decision making process as a whole.

Sad shit, since history proves that this will eventually lead to a World War and we're way too far lost in opinion to comprehend the true consequences that will follow.

Having said that, it ain't gonna happen for a while, but this is the igintion that will cause Stephen Hawking's theory where we went from having 1000 years left on Earth ecologically to what is now approximately 100 years left socialogically.

But, at least you get to "work remotely" while jacking off to Facebook all day.

Go team.

Could anyone tell me why practically every mixin in Bourbon is suddenly deprecated? :P

TMW you make something good with much efforts and dedication, and then the API gets deprecated with breaking changes.

Hello. (Android) dev here contemplating about the future of my profession.

I am looking for a specialization or a field in my profession where i can be free of dependencies from GAFAM (The big five)
Basically software development is me only using dependencies and stuff they and 3rdparty people have created and then it works or it doesnt. Or if you dont keep it up2date it wont work because deprecation and breaking changes. I was web developer before and changed to android because of all the libs and frameworks one needed to wield for proper development. And now android has mostly become the same. Vanilla android is easy, but u start using google apis or 3rdparty services u quickly realize how far u get away from your actual usecase. Usermanagement, oauth, 2fa, userdatamanagement, crossplattform, offline, syncing etc.

I am pretty sure the topic came up before (dev fatigue, dependency fatigue) and most of you know what i mean but i might be the recent casualty here.

In most businesses, self-proclaimed full-stack teams are usually more back-end leaning as historically the need to use JS more extensively has imposed itself on back-end-only teams (that used to handle some basic HTML/CSS/JS/bootstrap on the side). This is something I witnessed over the years in 4 projects.

Back-end developers looking for a good JS framework will inevitably land on the triad of Vue, React and Angular, elegant solutions for SPA's. These frameworks are way more permissive than traditional back-end MVC frameworks (Dotnet core, Symfony, Spring boot), meaning it is easy to get something that looks like it's working even when it is not "right" (=idiomatic, unit-testable, maintainable).

They then use components as if they were simple HTML elements injecting the initial state via attributes (props), skip event handling and immediately add state store libraries (Vuex, Redux). They aren't aware that updating a single prop in an object with 1000 keys passed as prop will be nefarious for rendering performance. They also read something about SSR and immediately add Next.js or Nuxt.js, a custom Node express.js proxy and npm install a ton of "ecosystem" modules like webpack loaders that will become abandonware in a year.

After 6 months you get: 3 basic forms with a few fields, regressions, 2MB of JS, missing basic a11y, unmaintainable translation files & business logic scattered across components, an "outdated" stack that logs 20 deprecation notices on npm install, a component library that is hard to unit-test, validate and update, completely vendor-& version locked in and hundreds of thousands of wasted dollars.

I empathize with the back-end devs: JS frameworks should not brand themselves as "simple" or "one-size-fits-all" solutions. They should not treat their audience as if it were fully aware and able to use concepts of composition, immutability, and custom "hooks" paired with the quirks of JS, and especially WHEN they are a good fit.

Deprecated Dependencies or Depreciated Dependencies?

In my country the word deprecation they call it depreciation.

So I am so confused with the terminology.

I think I've asked this before. Just cropped up again cuz I'm pushed to do some stuff in nextjs

I Wonder how much longer before js framework devs realise they've been reverse engineering the browser this whole time, that the current browser spec was outdated since the dawn of Web fidelity and real time applications

I wonder whether there are some guys who have seen this and are already cooking in the background. The browser still treats the Internet like front end and back end, whereas with the way apps are going (eg deprecation of the front/back end roles), it seems apparent the browser needs to scale up by fading whatever js is now

I'm seeing "use server", which was one of php's infamous atrocities back in the day (lack of separation of concerns, everything in index.php). It's shocking how those who ridicule that language let this fly, but that's probably a separate thread. Point is, a bunch of these stuff done by front end frameworks seem like boilerplate but the syntax is far different from what I remember javaScript to be. I only vaguely recollect and understand what I'm reading

Why not merge all the cryptic syntaxes struggling to achieve bare minimal expectations, into advanced markup language controlled by dom attributes? Overhaul and Rethink client - server communication to fit modern standard. Someone needs to step out of the box and take a good look at the rat race. I find our lives would be made much simpler if api integration into client side behaviour wasn't a separate thing altogether

You have all these funny hoops and precarious bridges to cross. The reality is what we're fighting to overcome is the manner the architecture is setup. We need a Google/meta/amazon/apple to step in with a new browser since it's not a weekend gig and might need their reach to catch on with mainstream users. Sadly, they're the same guys rolling out new js frameworks

Deprecated API methods without any documented replacement methods or even justification for the deprecation. What do I do with this!?

Following are the only real problems I had with my XFCE Manjaro (I guess essentially XFCE problems). My question is, is it just me?

Touchpad problems:
The synaptics deprecation kinda f'ed me up.
I tried sticking to synaptics, but I had an issue where if I connected a usb mouse the touchpad would sometimes stop working (it's deprecated after all).

So I switched to libinput. The default movement feels good (synap felt kinda slippery)... but then... NO COASTING/KINETIC SCROLLING in a lot of apps? WTF?!
Would kinetic scrolling work in general if I switched to a wayland based DE?

The alt tab has a delay:
you would expect one of the most lightweight DEs to have near instant switching. But no, I have like almost full second delay, and for the life of me I can't find the way to customize it.

Thr battery management is kinda stupid. Even though I set the thing to hibernate or sleep in low battery it never does.

NINE Methods _IN A ROW_ look like this. I can't bring myself to search for more. They are called 100+ times and after each call we check if they returned success.

VERIFY_XYZ SECTION.
V_010.

MOVE RETCODE$FAIL TO RET_CODE.

CONTINUE.

MOVE RETCODE$SUCCESS TO RET_CODE.

V_100.

V_EXIT.
EXIT.

Fucking Yeoman, guys.
For a school project I thought I'd try it out to scaffold out my folder structure etc. Ran a php generator (not having commits since 2013) through npm and sipped my coffee while one node deprecation warning after the other filled my terminal.
Now I just feel like I'm sitting with my dick in my hand while staring at what looks like the fucking source code of the Matrix itself.
Does anyone use Yeoman for PHP projects anymore?
Well, at least Grunt works flawlessly 😎

def longVariableNamesEverywhere(*args):
"""
Not a substitute for docstrings and code comments.
"""
#TODO: insert witty and legible code.
#TODO: learn to read code.

return "Rant and self-deprecation complete."

Deprecating the tests before deprecating the feature