When each day there is a new framework in the JavaScript world...

After listening to two of our senior devs play ping pong with a new member of our team for TWO DAYS!
DevA: "Try this.."
Junior: "Didn't work"
DevB: "Try that .."
Junior: "Still not working"

I ask..
Me:"What is the problem?"
Few ums...uhs..awkward seconds of silence

Junior: "App is really slow. Takes several seconds to launch and searching either crashes or takes a really long time."
DevA: "We've isolated the issue with Entity Framework. That application was written back when we used VS2010. Since that application isn't used very often, no one has had to update it since."
DevB: "Weird part is the app takes up over 3 gigs of ram. Its obviously a caching issue. We might have to open up a ticket with Microsoft."
Me: "Or remove EF and use ADO."
DevB: "That would be way too much work. The app is supposed to be fully deprecated and replaced this year."
Me: "Three of you for the past two days seems like a lot of work. If EF is the problem, you remove EF."
DevA: "The solution is way too complicated for that. There are 5 projects and 3 of those have circular dependencies. Its a mess."
DevB: "No fracking kidding...if it were written correctly the first time. There aren't even any fracking tests."
Me:"Pretty sure there are only two tables involved, maybe 3 stored procedures. A simple CRUD app like this should be fairly straight forward."
DevB: "Can't re-write the application, company won't allow it. A redesign of this magnitute could take months. If we can't fix the LINQ query, we'll going to have the DBAs change the structures to make the application faster. I don't see any other way."

Holy frack...he didn't just say that.

Over my lunch hour, I strip down the WPF application to the basics (too much to write about, but the included projects only had one or two files), and created an integration test for refactoring the data access to use ADO. After all the tests and EF removed, the app starts up instantly and searches are also instant. Didn't click through all the UI, but the basics worked.

Sat with Junior, pointed out my changes (the 'why' behind the 'what') ...and he how he could write unit tests around the ViewModel behavior in the UI (and making any changes to the data access as needed).

Today's standup:
Junior: "Employee app is fixed. Had some help removing Entity Framework and how it starts up fast and and searches are instant. Going to write unit tests today to verify the UI behaivor. I'll be able to deploy the application tomorrow."
DevA: "What?! No way! You did all that yesterday?"
Me: "I removed the Entity Framework over my lunch hour. Like I said, its basic CRUD and mostly in stored procedures. All the data points are covered by integration tests, but didn't have time for the unit tests. It's likely I broke some UI behavior, but the unit tests should catch those."
DevB: "I was going to do that today. I knew taking out Entity Framework wouldn't be a big deal."

Holy fracking frack. You fracking lying SOB. Deeeep breath...ahhh...thanks devRant. Flame thrower event diverted.

I started in 2015 at my current job. The first contract was for a year, very normal in the Netherlands. Also, I had only 6 months of professional experience with programming.
I already knew that I would replace an older colleague who's going to retire and I would get some of his responsibilities.

One year later (6 months ago) I had an evaluation with my boss. He told me he was proud I learned everything so quick and offered me a permanent position and wanted me to take over one of the major products we sell. Even more, he wanted me to decide how to change the framework since it's over 20years old. (Multiple languages combined)

I am currently working on a new design and UX as well, which I presented last year. The love it.

I've never felt so appreciated and valued before.

Guy: dot net dev (C#) on windows. (desktop + server)
Team(not his team, he just happened to sit next to us): php/frontend devs and Linux (server) people.

Team: starting a new project! We'll have to see what framework to use and what server :D
Guy: i know it's none of my business...... but I'd recommend dot net and windows server!
Me: respectfully, that hardly makes sense, you know our skillset/field... i understand that it works for you but it doesn't really for us :).
Next to that we'd rather not use windows for security reasons.

It's fine if that happens once.

When it happened for the 1748472823'th time, I had a real hard time controlling myself.

The windows/microsoft fanboy I've ranted about multiple times.

- wouldn't use anything except for windows. Even if required for a project (I would if really needed, have done that a few times already)
- refused to use any framework/language not written by Microsoft
- tried to get other projects to use windows/.net when it wasn't required and it was only linux/php guys (and that fit the projects perfectly)
- ONLY wanted to use Skype and whatsapp. Always bragged about how he had 10gb of Skype history.
- didn't want to use anything related to linus torvalds or open source because 'those are open source and have no business model so they're bad'

And then: he suggested the use of windows server right after one was hacked (windows vuln that wasn't patched yet) which caused the devops guys to want to install a new Linux server for it.
Even the windows sysadmin pointed to the door when he said that and gave him a huge 'GTFO' face cD

Yeah, fuck him.

Seven months ago:
===============
Project Manager: - "Guys, we need to make this brand new ProjectX, here are the specs. What do you think?"

Bored Old Lead: - "I was going to resign this week but you've convinced me, this is a challenge, I never worked with this stack, I'm staying! I'll gladly play with this framework I never used before, it seems to work with this libA I can use here and this libB that I can use here! Such fun!"

Project Manager: - "Awesome! I'm counting on you!"

Six months ago:
====================
Cprn: - "So this part you asked me to implement is tons of work due to the way you're using libA. I really don't think we need it here. We could use a more common approach."

Bored Old Lead: - "No, I already rewrote parts of libB to work with libA, we're keeping it. Just do what's needed."

Cprn: - "Really? Oh, I see. It solves this one issue I'm having at least. Did you push the changes upstream?"

Bored Old Lead: - "No, nobody uses it like that, people don't need it."

Cprn: - "Wait... What? Then why did you even *think* about using those two libs together? It makes no sense."

Bored Old Lead: - "Come on, it's a challenge! Read it! Understand it! It'll make you a better coder!"

Four months ago:
==============
Cprn: - "That version of the framework you used is loosing support next month. We really should update."

Bored Old Lead: - "Yeah, we can't. I changed some core framework mechanics and the patches won't work with the new version. I'd have to rewrite these."

Cprn: - "Please do?"

Bored Old Lead: - "Nah, it's a waste of time! We're not updating!"

Three months ago:
===============
Bored Old Lead: - "The code you committed doesn't pass the tests."

Cprn: - "I just run it on my working copy and everything passes."

Bored Old Lead: - "Doesn't work on mine."

Cprn: - "Let me take a look... Ah! Here you go! You've misused these two options in the framework config for your dev environment."

Bored Old Lead: - "No, I had to hack them like that to work with libB."

Cprn: - "But the new framework version already brings everything we need from libB. We could just update and drop it."

Bored Old Lead: - "No! Can't update, remember?"

Last Friday:
=========
Bored Old Lead: - "You need to rewrite these tests. They work really slow. Two hours to pass all."

Cprn: - "What..? How come? I just run them on revision from this morning and all passed in a minute."

Bored Old Lead: - "Pull the changes and try again. I changed few input dataset objects and then copied results from error messages to assertions to make the tests pass and now it takes two hours. I've narrowed it to those weird tests here."

Cprn: - "Yeah, all of those use ORM. Maybe it's something with the model?"

Bored Old Lead: - "No, all is fine with the model. I was just there rewriting the way framework maps data types to accommodate for my new type that's really just an enum but I made it into a special custom object that needs special custom handling in the ORM. I haven't noticed any issues."

Cprn: - "What!? This makes *zero* sense! You're rewriting vendor code and expect everything to just work!? You're using libs that aren't designed to work together in production code because you wanted a challenge!?? And when everything blows up you're blaming my test code that you're feeding with incorrect dataset!??? See you on Monday, I'm going home! *door slam*"

Today:
=====
Project Manager: - "Cprn, Bored Old Lead left on Friday. He said he can't work with you. You're responsible for Project X now."

1) Looking up official Page of the new language/framework
2) Watch tutorial on Youtube
3) Realise it's teached very complicated
4) Buy a course on any course site
5) Realise it's even more complicated
6) Buy book
7) Learn it perfectly
#booksForLive :D

Imagine yourself exploring Medium, looking for some new awesome tools to try out.

You accidentally find the new, promising programming language. It called Blow. It promises itself to be “idiomatic”, “minimalistic”, “simple” and “handsome”. And it also compiles to Electron. You decide to give it a try.

It has its own package manager, simple and idiomatic – every package is “blow add” away. But it’s only three packages available: the “blowsay”, just like “cowsay”, the “this”, printing The Blow Manifesto and “blue”, which is simplistic, simple and minimalistic idiomatic handsome functional frontend framework built with simplicity in mind.

You want to build a todo app, so you type “blow add blue” and press enter.

Following Medium articles written by some guy wearing Ray-Bans, you managed to finally put a todo app together, after seven hours of straight up coding and fighting that simple and idiomatic syntax, trying to make it do what you need. Alright, it’s time to build it.

It has built-in task runner named “job”.

So you type “blow job todo”.

You spending three hours more doing “blow job this”, “blow job that”, trying to blow job everything you see. You’re tired and mad at those damn blow job hipsters created that. You literally suck at programming in that.

Everything falls apart. Things doesn’t work. And after another “ENOENT 0() 0x628 NOT_SUPPORTED”, you give up, admitting that you’ve really sucked at this.

As time goes on, I've always wondered what I'm going to say to my future grandchildren about what Dev work was like today:

"Grandpa Josh what was programming like when you were a kid?"

"OH IT WAS AWFUL. ALMOST NOBODY USED VERSION CONTROL CORRECTLY AND NEW JAVASCRIPT FRAMEWORKS WOULD APPEAR EVERY SINGLE DAY!"

"They at least attempted to use new paradigms in their framework code, right grandpa?"

"NO CHILD. THEY WERE EXACTLY THE SAME IN EVERY WAY..."

This guy is supposed to be a "spring framework guru"

Yo Mr. Guru, this is not how you write a pom file especially when you are teaching someone who probably is new to programming. Just think if the new guy/girl goes on to write such xml files in the future. What are you even trying to do man.

Ok, rant incoming.
Dates. Frigging dates. Apparently we as a species are so bloody incompetent we cannot even decide on a one format for how to write today. No, instead we have one for every language and framework, because every moron thinks they know better how to write the date. All of them equivalent and all of them different enough to make me start lactating out of frustration trying to parse this garbage... And when you finally manage to parse it on one platform it turns out that your ORM just decided to use the less common version of the date, and have fun converting one to the other. I hope that ever time someone comes up with a new date format will be hit in a face with a red hot frying pan untill they give up programming in favour of growing cactuses.

Recruiter: “can you write your own framework?”

Me, after considering for a good minute: “well, I am kinda starting to automate lots of things so I guess if I wanted I may be able to... for sure I’d learn a lot along the way...”

Recruiter: “very good!”

Me:”wait, why would you want that skill?”

Recruiter: “our customers want custom code”

Me:”so you write a new framework every time?”

Recruiter: “ah you have also experience in [x]!”

Some people scare me 😟

Told the new hire that for the first week they can just familiarise themselves with the JS framework, do the tutorials, and read through the code / docs.

Boss comes by Tuesday morning "you should be finished with all the tutorials by the end of the day"

Looks like we're throwing him in the deep end!

Context: new dev has Java and 3d games background. Our app is full stack JS

From my last job interview (which I got hired btw)

Lead developer: "so we see quite a lot of frameworks that you listed for php, Laravel,cakephp, codeigniter, we really like the idea of them but have not had the opportunity to use them since as you might know by know our pages run over basic and small scripts, you also listed some cool front end frameworks, react looks amazing and I do have somr experience. Tell me, if given the choice, which framework would you use for php?"

Me: Really depends on the project, but the ones that you have described previously seem that they would not really benefit from them, we should not use them if they are overkill or will not expand to anything else on the future"

Him: "But given the choice?"

Me: my own framework, completed it a couple of days ago, it has its own routing system and everything made by yours truly, used it before on some projects in which the developers work with it with no need to ask me about stuff, the documentation is sound and the code rather simple. Php is and can really be all you need depending on what we are talking about."

Him: **stands up, moves closer to me and fist bumps**
"All right now moving on, i was wondering abouy redux, what are the benefits of..."

Walked out of there like a boss, it got interesting when we started talking about Lisp, apparently they are interested in putting some Clojure to test in small things since they want to learn new things and apply them. Yup, this gon b good!!

I think all the JS framework stickers should be the same size and shape... that way each year when you switch you can just cover up the old sticker with the new one :)

AngularJS is dead. React is dead. Vue.js is dead. I guess you got to switch to the new awesome framework called Vanilla JS!

A few months ago I was working on a (totally underpaid project) where my friend and I had to basically rewrite the entire program our client was using.

So we started planning and wrote all sorts of documentation to show the client our ideas for the new flow of the program, the new structure of the GUI and a few more details of what would the inner workings of the new app. He seemed to like all those ideas and gave us the green light to go through with the project and start coding.

We spent a couple of months coding, redoing the front end from scratch (with a different framework even, so I couldn't reuse any code from the old version) and completely redesigning the back end so it would be better, faster, more scalable etc etc etc. During this process, we obviously showed the progress of the app to our client, explaining everything we had been doing, and he seemed to like every new version we showed him.

When we were in one of the last stages in development (basically sending versions of the app to the client for evaluation), the guy suddenly changed his mind. After agreeing on everything we had been showing him over the last months, he sent an email saying:

"...the new system makes the app too complicated. I want this program to be as simple to use as possible; so we should revert the "Policy" system to essentially what it was in the last major version. The only change I want to make is [...] and everything else is essentially the same as the last Policy system."

So basically he wanted us to FUCKING UNDO EVERYTHING WE HAD DONE AND REVERT THE FUCKING PROGRAM TO THE FUCKING VERSION HE HAD BEFORE HIRING US!!!! WHAT THE FUCK????

YOU WANTED US TO CHANGE YOUR APP AND THEN YOU SUDDENLY CHANGE YOUR MIND AFTER 3 FUCKING MONTHS WHEN THE PROCESS IS DONE???

GO FIND A SWORDFISH TO FUCK YOU IN THE ASS, IM NOT WORKING FOR YOU ANYMORE

God, it feels good to let that out.

Dear YouTube tutorial makers, if you list your video as a tutorial doing something only to make people download a library of framework and then teach us how to use the library you can go fuck a cactus :-3

Every single video that interests me like building interpreters, new 2D game methods and the like all have no actual ground up programming at all... Ugh!

Worst part of being a dev?

THERE'S A NEW FREAKIN FRAMEWORK EVERYDAY.

Where are we supposed to get time to learn everything the job applications require? And even worst, have 2 years of experience with the thing?

And how about when developing a responsive dynamic website? If you are crazy, like me, and you are the kind of dev that always wants to deliver something great, customized to the needs of your client, and that doesn't smell bootstrappy, you probably can't stand too when people ask you about time guesstimates. Especially when you are the ONLY DEV in your company.

Also, our gear is EXPENSIVE.

Sorry, I guess I'm stressed... Had to bring some work home, due to the bosses deciding to deliver a project one week early to the client, without consulting me first.

Still, luckily for me, all this bullshit can't take my love of coding away.

I think I ranted about this before but fuck it.

The love/hate relation I have with security in programming is funny. I am working as a cyber security engineer currently but I do loads of programming as well. Security is the most important factor for me while programming and I'd rather ship an application with less features than with more possibly vulnerable features.

But, sometimes I find it rather annoying when I want to write a new application (a web application where 90 percent of the application is the REST API), writing security checks takes up most of the time.

I'm working on a new (quick/fun) application right now and I've been at this for.... 3 hours I think and the first very simple functionality has finally been built, which took like 10 minutes. The rest of the 3 hours has been securing the application! And yes, I'm using a framework (my own) which has already loads of security features built-in but I need more and more specific security with this API.

Well, let's continue with securing this fucker!

Assigned to a new project team..

Using git, in a creative way. So.. "master" is "dev" branch, usually. Everyone can push their branch to dev server .. so it's "dynamic for us". Production branch is whatever, as long as the branch has the release version. Sometimes, the release comes from "master".. that mean "dev" in normal geek..

That's just Git. The source code is a saturated spagetti of Entity framework and Caliburn. It is littered with antipatterns, especially basebean. Holy Christmas and Easter that baseclass do a lot of stuff that has no place as a base class ..

Fucking frameworks, I'm gonna start to evangelize frameworks as the no1 antipattern.

MS SQL as the main DB, but is dumped to json FILES through a scheduled task to increase read performance on web.

There is a soap endpoint to expose the json files, fml..

I am assuming I was placed here to improve stuff, I have never in my life seen anything like this before.

There is a special place in hell for this repository

How Google loost its data Monopoly-

Present:
Step 1- US bans Huawei

Step 2- Google Bans Huawei

Step 3- China Gov helps Huawei get back on its feet

Future:
Step 4- Huawei makes their own OS to rival Google, the OS can run Android apps as well as IoS apps and has its own language/framework for developing new apps

Step 5- China bans Google from their market

Step 6- Chinese mobile manufacturers adopt the new OS

Step 7- China's population starts using the new OS i.e. country with the world's largest population starts using the new OS

Step 8- Chinese manufacturers like Xiaomi, Vivo, Oppo and OnePlus who already own approx 40% of India's smartphone market start distributing the new OS based phones in India. Factors like cheaper devices take this market share to 50%+

Step 9- Cry, cause the new OS is now being used by approximately 30% of the world's population.

Yeah, bring your hate in the comments but come back and talk to me in August 2022...

Spent 2-3 weeks on implementing a new feature, a guy with 10 years of experience jumps in and solves it within 5 days.

*Oh! I forgot to mention, it was his first time working with the framework.

I must say his OOP skills are really good, not sure if this is something you learn by reading books or simply by practice.

I strongly believe that if you have a good understanding of how to build apps with OOP pattern, you'll do a great job in the SW industry.

*Looks up advice on how to implement something
*Finds reasonable, well written advice on Stack Overflow that recommends not using <insert latest framework here>
*Ignores advice
*Two hours of exasperated coding and git resets later
*Goes back and upvotes advice

I wonder why there is a new JavaScript framework every 10 minutes. Could the issue be with the JS language itself?

Naaaaaaaah .... Impossible .....

Dear Product Owners,

If you tell me how I need to architect my software again I'm going to ask you to provide a network topology of the architecture you want me to build.

I'll also need you to request the new servers, work with the ops teams to setup credentials, provision the NAT, register the domains and document the routes that the proxy will need to use.

then I'll need you to hook the repo up to our non-existent pipeline so that I can make sure I won't do all that testing I already can't do.

I hope you're paying attention, because that framework you told me I needed to use is going to be a pain to setup correctly.

after you're done with that, please attach any documentation you shit out to the ticket you never created.

Enragedly yours,
Looking for a new job

PS: get fucked

So I just finished my first 40 hour work week.
And just an hour ago I had a meeting.

In that meeting I said pretty much this:
"Your old system is rubbish, I want to make a new one"
"Also we can't use the old framework"
"Also it needs to be in a different language that nobody knows here"

And they went for it!

At this point I think I can sell anything to anyone.

Skipping unit tests and documentation ...

I'm starting to recover after not writing a single test for the first 6 years of my professional carrer (wasn't taught in school, didn't know where to start, man I should have really found a mentor earlier), and barely any documentation (I was the sole developer for several years, and just didn't get into the habbit).

Unit testing is still not a habit, but now I have the first tests to serve as an example and an idea what/how to test at least, and I try to get every new "framework" function/class at least commented properly.

Wish me luck

I used to work in a small agency that did websites and Phonegap apps, and the senior developer was awful.

He had over a decade of experience, but it was the same year of experience over and over again. His PHP was full of bad practices:

- He'd never used an MVC framework at all, and was resistant to the idea, claiming he was too busy. Instead he did everything as PHP pages
- He didn't know how to use includes, and would instead duplicate the database connection settings. In EVERY SINGLE FILE.
- He routinely stored passwords in plain text until I pretty much forced him to use the new PHP password hashing API
- He sent login details as query strings in a GET request
- He couldn't use version control, and he couldn't deploy applications using anything other than FTP

The management brought some devs from another outsourcing company into our project to overcome the fact that we, the existing developers, are retarded. We are retarded because they change the scope continously (aka daily) and we can’t keep track with their requests. They want something and after we implement it, they want it changed. Completely.

Instead of getting the project and deep dive into it using the materials (setup, architecture etc.) I prepared along the way, their PM said that we have to make some low level knowledge transfer. This knowledge transfer session happened on Friday.

The presenters were me and one of my colleagues. After 2 hours of training, we found out that the supposed senior devs don’t know how to use GIT, they don’t have a clue about Spring nor Angular (nor any SPA framework), their only questions were ‘why didn’t you use X?’ (where X = bootstrap, jQuery etc.) etc.

What is even funnier: during the presentation we were asked to keep a screen sharing opened during working hours for a couple of days just so the new devs could see how we are working.

Guess what happened with the scope on Friday evening: it changed again because ‘you got new devs so there will be multiple resources to handle tasks’.

2 more weeks and i’m out of there...

So processors have Moores Law, I'm starting to think Web Development has one too.

"There shalt always be a new, better, framework, that would have saved weeks of time, but only after you've hit the point of no return in a project"

Anyone else know the feeling of "damn...I may as well just rewrite everything...."

Freelance client fired me on Friday, with literally a couple of minor issues to take care of left before launch. When I inquired, he said they're going in a different direction. I immediately smelled bullshit. When I asked who to turn over the files and DB to, it was their idea to allow me to broker the deal to switch things over and hand the keys over. I asked the new dev what framework or installed CMS and he thought I was crazy for asking. He told me they're taking by build of the site and finishing it. That's fucking low.

They:Why didn't you come up with this solution 2 years ago?

Me: The framework on which the new solution is proposed DID NOT exist 2 years ago.

This industry is fun!

Introduced a ‘new’ logging framework for our web site. Web team is testing the integration and I get an email saying the logging wasn’t working. Instead of sending me how she is searching the logs, she sends me a screen shot of the code (which is ass-backwards of how I documented the logging library, but that’s another rant). OK, she wrote 5 lines of code that should be one line, but OK, the error still should have logged fine. I search the logs, and sure enough, there they are. Errors logged just as they should.
So I email back (with screenshot of the search query and results) asking how she searched for the errors.
Hour later she responds ..”I don’t know.”
That’s it.
WTF do you mean “I don’t know”?…WTF…you are a –bleep-ing developer too! This is not the first –bleep-ing splunk query you’ve written!
OK..I’m calm..feeling better. Wouldn’t be so bad if she emailed just me with the question (I’m not a splunk query expert either, we can figure it out together), but she was sure to cc 3 of the PMs involved in the integration, my boss, and other team members to make it sound like the problem was my code.

I spent the last 3 months trying to hire new developers for my team. I found someone experienced who is great and a graduate, who is, well, a graduate.

For some reason he thinks he knows everything about our framework he has never used and seems to think he knows how everything works in our codebase which he has never seen.

That’s fine. I’ve had my share of cocky developers.

But what confuses me is that when I ask him what critical bugs are left, he reels off two significant ones. I ask what it will take to fix it. Of course he says he knows how to fix it. So I say great. Then fix it and let’s move on to a more fun part of our project.

Suddenly he didn’t know where he problem was and so I told him he had to investigate and come back with something concrete.

It’s just frustrating managing this developer who is deceitful.

!Rant

Designer decide to have a meeting with stakeholders about UX/UI workflow for control panel of our new embedded system (no framework, no library, gui is bit per bit rendered on frame buffer).
A week later, still nothing on my table, not a mail, not a call. Meanwhile I wrote a framework, the control system, renderer, and messaging queues between tasks.
Wrote some widgets, a layout system and a view swtching mechanism, and a separate stack control to use a "back" button.

Now I am stuck for I do not know what should happen when clicking on various (non obvious) items on the touchscreen.
Fine, I'll ask the designer.

"Oh, I will write the workflow next week" (ETA time, 2 weeks. Seriously? You take a week to draw on Adobe Illustrator 20 screenshot with text and I have another week to write it from scratch in C?)
Ok, while you write it, just tell me what should happen when I click an active item.
"Well, we didn't talk about that. We just decided the colour of the icons on the screen..."
For fuck sake...

Today I started work on a new project that contains a lot of legacy. I asked the developers about unit testing javascript and was told that not only is there none in place, but it's not worth adding any in.

At first, I grimaced and thought fair enough. This is their codebase, it's their choice. I've now been thinking about this for a few hours and have instead decided that screw those guys, I'm adding in a testing framework, a module pattern that's compatible with the existing code, and unit testing the crap out of it. If they don't want it they can refactoring it out, but I can't bring myself to intentionally deliver code I know is crap.

I WILL FORCE CODE QUALITY ON THEM.

Realizing that the former so-called PHP developers based the entirety of their so-called dashboard framework (self-written of course) on GET requests.

Every. Controller. Only. Accepts. Get. Requests.

It creates stuff? So what! It does update? No matter! It deletes? Who cares!

Just call that URL, and it will release all hell, plagued with multiple side-effects, and then issue a redirect.

Of course that one delete button was inside some twitter bootstrap tabs, and due to the redirect the page always reloaded and the content manager landed on a very different tab. Meaning if they wanted to delete multiple records, they had to hit "activate tab" and "delete" and "activate tab" and "delete" -- rinse and repeat.

It's our *job* to make things easier for our users! Not to waste their time. (Unless you are browser game developer. Then do your thing.)

And we are talking basic CRUD! Basic CRUD! I am not even demanding for it to be restful or to have some parts of a HTML page being updated on the fly with such rad and new technologies like ajax!

There is just question I would like to ask whoever build this: Seriously!?

My Task: Create a new application in a custom C#-Framework, to replace screens from the old application.
Me:Fine.
The old application has a Java Frontend.
Me:Fine.
The old application has an Oracle-DB.
Me:Fine.
The old application has its logic fully on the DB.
Me:What ??
You cannot connect to the DB via ODBC.
Me:But why ???
You cannot use external libraries, just our framework.
Me: For what are you thinking i can use to call the functions on the DB
You have to use a custom connection-bus which uses JDBC
Me:Fine.
This connection-bus cannot call SQL Statements and return the result.
Me:WTF, how should i get the data out of the Database ?
We don't know find a way.
Me:Ahh fuck off.

At work, an idiot who has never worked on machine learning before and understands nothing about it: "You know what, machine learning isn't actually hard. It is just basic statistics and then you download the model online and that's it! There's nothing else you are doing!"

STFU, you moron! Do you think just any model can work for your use case? Do you fucking think it is easy to come up with new architecture for a very specific use case and test it accurately? Do you think it's easy to effectively train a model and do hyper-parameter optimization?Do you fucking think it is easy to retrieve the right data for your use case? Do you think it's easy to keep up with research papers on arXiv being released daily? Do you think this is fucking javascript and there's a framework for everything? Stfu!
Honestly, i hate ignorant morons who generalize stuff they don't clearly understand.

Why is it that pretty much zero package & framework maintainers understand semantic versioning?

1. If you do a complete rewrite of your package, but the resulting API is identical, you don't need to bump to the next major version. As a user, I'm thankful for your increased performance or cleaner internal code, but it doesn't really affect my update process.

2. If your package required some-framework 6.0.0, and now ALSO supports some-framework 7.0.0 but is still compatible with 6.0.0, you don't need to bump to the next major version. As a user, I can now upgrade the framework, and know that the package will keep working, but otherwise it doesn't really affect me.

3. Following your versioning along with the framework/language version is super annoying, especially if your library really doesn't need to differentiate between framework versions because it's not actually utilizing new framework functionality.

4. On the other hand, if you stop supporting a certain language, framework or shared library version, or change the public methods, exceptions, fields, etc, you MUST bump to a new major version.

Yet everyone gets this wrong.

For example, many of Laravel's underlying subpackages (for collections, filesystem, database, config, http, mail, etc) do not change their code in a breaking way, or do not even change at all between major framework versions.

Yet they follow along with the major framework version.

Now if someone makes a library "laravel-elasticsearch" which uses the support libraries and collections from laravel, they need to update their package to move along with the versions as well, and often they choose to number their library along with the framework in turn.

This means that to update the framework, you also need to update over 9000 dependencies.

FOR NO FUCKING REASON. THE ONLY CHANGE IN THOSE FUCKING DEPENDENCIES IS TO UPDATE COMPOSER.JSON TO BE COMPATIBLE WITH THE FUCKING FRAMEWORK.

Meanwhile, Laravel itself breaks repeatedly on minor/patch version updates, because breaking changes slip through their review process.

Ugh.

Yes please migrate to a new framework in the middle of a project mmh yes punish me more.

Inmates are trying to take over the asylum again.

Got a message from the web team manager deeply concerned because since switching to the new logging framework, the site is significantly slower.

She provided no proof or any data to what 'significantly slower' means.

#1 The 'new logging' has been in place and logging for 5 years. We only recently depreciated the ILogger interface ('new' ILogger interface only has 1 method instead of 5)
#2 The 'old logging' was modified 5 years ago, so even if you were using the 'old' interface, the underlying implementation is still the same.

She tried to push the 'it wasn't this slow before' argument, so I decided to do some fact based analysis.
Knowing they deployed their logging changes couple of weeks ago, I opened up AppDynamics, looked at the average call time to Splunk (along with a few other http calls they are doing)
- caching services - 5ms
- splunk - 30ms
- Order Service - 350ms
- Product Data Service -525ms

Then I look at the data they are logging, for the month of June, over 5 million messages. At 30ms each, that's almost 42 hours spent logging errors...yes errors. Null reference exceptions, Argument exceptions, easily fixable stuff.

So far for the month of July (using the 'new' logging), almost 2.5 million errors. Pretty close so far with June's numbers.

My only suggestion was to fix the bugs in their code so they don't log so many errors.

Her response.."Can we have one of our developers review your logging code? We believe we can find ways to optimize the http requests"

Oh good Lord. I'm not a drinking man..but ...I might start.

I love static sites and fancy new frameworks. Had an interview some time ago at a medium sized company. They specifically wanted someone to build static sites and introduce the company to Vue and Gridsome.
I got really excited for my first project. It was a wordpress site and I had to build a custom WP theme for it. Not exactly what I expected. Also I had no prior PHP knowledge, nor any experience with Wordpress. So I got really upset, because it wasn’t the technologies I was used to.
The first week was hard, I wanted to quit. But once something clicked. And I realized I know this. This is not PHP, not Wordpress, not Vue, but just simply a programming language. At the core everything programming language is the same. PHP became comfortable, Wordpress conventions didn’t bother me. I realized I can use great technologies with WP too. I get to know twig, added some sass, compiled everything nicely with webpack. And after a month I have a beautiful, fast and efficent site. I love it.
I realised that I don’t love the languages and frameworks. I love coding itself. I love creating efficent and reliable, clean code. No matter the architecture.
And my advice for you is to stop hating particular languages and serious debates on what is better, and hating your job when you can’t code in your new shiny framework. Love coding itself, because it’s a wonderful activity. We are creators, we are artists. Not <insert specific programming language here> developers.

Earlier this day (or yesterday, timezones 'n stuff) I posted a "rant" about my new Project:

"The Spigot Web Framework" - a Tool that should help Owners of Minecraftservers without dedicated Webserver and knowledge about developing a website.

In the Screenshot below I show you guys, how few lines of code can make a beautiful website.

The Modulemanager is fully done and people can build their own Modules, which can be live updated.

I am currently working on "cross communication" between the Client and the Modules.

I hope you guys stay tuned!

EDIT: As mentioned in my last rant (look @comments) I will be able to pull off a standalone version of this software.

I should just quit. I am not paid enough to deal with this pissing contest.
Reviewer:
Need to add instructions (on readme) for installing pnmp, or if possible, have the top-level npm i install it (lol).
Also, it looks like we are no longer using lerna? If that's right, let's remove the dependency; its dependencies give some security audit messages at install.
Me:
it's good enough for now. Added a new ticket to resolve package manager confusions. (Migrate to pnpm workspaces)
Reviewer:
I will probably be responsible for automating deployment of this (I deployed the webapp on cloudflare pages and there is no work that needs to be done. "automating deployment" literally means replacing npm with pnpm). I disagree that it's good enough for now.

Imagine all readmes on github document how to install yarn/pnpm.

Lesson learned:
If you think an OOP static site developer can't handle modern JS framework, you are probably right.

Before I left for vacation two weeks ago, I busted my butt to build out another portion of my frontend testing framework and get it in place (and spec’d) to unblock a coworker on a semi-high-priority ticket. I sent him detailed notes on which areas of the product it covers, how to use it, and copied one of his (blocked) tests over and updated it to use the new methods, pattern, namespacing, etc.

I came back today and discovered … he hasn’t even touched it. Everything is exactly as I left it.

Wheeeeeee.

Today I learned that the my new teams choice to use a mostly undocumented/unused framework over a well known/documented one was decided by a coin toss.

My plan to become rich:

1. Create a library / framework that's really just an easy wrapper for other libraries.

2. Write a bunch of books / courses online teaching this "new" library

3. Market it to overpowered but impressionable PM's who'd fall for anything with the word "inovative" in it

!rant
As a self taught, I used to break what i want to learn into pieces and watch tutorials where people use these pieces. Then I could easily do what I learned, but I could do it exactly how I learned it from the tutorials.
Until one glorious day I found a tutorial about js that doesnt teach you the "how" of things but the "why" of things.
I cant describe how easy and in depth I understand js tutorials now. It is easier even when I have to learn a new framework.
It feels like I fast-forwarded my knowledge growth overnight.
I now see my 3 weeks old code and it disgusts me.

Software Devs are less supportive than the community tries to convey. They're also part of the most self-deluded and obnoxious crowd that exists on earth.

Someone saying they don't enjoy coding 24/7 outside of work? You actually enjoy totally different hobbies that have next to nothing to do with coding?
- Shitty developer, you should probably work elsewhere. Maybe flipping burgers.

"Coding in <Framework X> is SO friggin' easy. You're basically subhuman garbage if you can't learn it within a month!"

Watch some YouTube Videos with the "Freelancer Success Stories" of dudes that haven't - apparently coded, ever - and started to code late in life and tell you how perseverance and learning brings the success and yet you never see any repos of those guys. You see those guys mostly go on for up to half an hour to regurgitate some hot garbage you can read up within two minutes yourself from ANY coding blog.

You're not using a macbook to develop?
- "Oooof, man! How can you?"

You don't really like "Popular Framework X"?
- Especially when it comes to Frontend Frameworks prepare to either die on the hill of your beliefs or die a futile and slow death when people - more or less - snarkily try to dissect your opinion in order to try - again, more or less - to hide their own bias. Because don't forget, your opinion is OBJECTIVELY wrong and you simply happen to a garbage developer for (dis-)liking something.

You DO like "Popular Framework X"?
- Well, rinse and repeat basically.

You struggle to get a new job?
- All your fault. You clearly didn't spend enough time coding; you should have at least 12 Open-Source Projects with at least 100k downloads the week.

There is actually a whole lot more, but I feel I'm basically done with software dev. Software development is neither creative nor terribly fun. I'm just angry at myself that I switched careers for the money.

(New account because my main account is not anonymous)
Let's rant!

I'm 3 exams away from my CS degree, I've chosen to do some internship instead of another exam, thinking was a great idea.

Now I'm in this company, where I've never met anyone because of pandemic. A little overview:
- No git, we exchange files on whatsapp (spicy versioning)
- Ideas are foggy, so they ask for change even if I met their requirements, because from a day to another they change
- My thesis supervisor is not in the IT field, he understands nothing

The first (and only) task they gave me, was a web page to make request to their server, fetch data etc.
Two months passed trying to met their requests, there were a lot of dynamic content changin on the page, so I asked if I could use some rendering framework to make the code less shitty, no answers.
I continued doing shitty code in plain JS.

Another intern guy graduated, I've to mantain his code. This guy once asked me "Why have you created 8 js modules to accomplish the web page job?", I just answered saying that was my way of work, since we're on the same level in the company I didn't felt to explain things like usability, maintainability etc. it's like I've a bit of imposter syndrome, so I've never 100% sure that my knowledge is correct.
Now we came at the point where I've got his code to mantain, and guess what:
900 lines of JS module that does everything from rendering to fetching data..

I do my tasks on his code, then a bug arises so the "managers" ask him what's happened (why don't you ask to me that I'm mantaing is code!?!?), he fixes the bug nonetheless he finished his intership. So we had two copies of the same work, one with my job done and still with his bug, and another one without my work and without the bug.
I ask how to merge, and they send me the lines changed (the numeration was changed on my file ofc, remember: no git...)

Now we arrive today, after a month that they haven't assigned any task to me and they say:
"Ok, now let's re-do everything with this spicy fancy stunning frontend framework".
A very "indie" Framework that now I've to study to "translate" my work. A thing that could be avoided when I've asked for a framework, 2/3 MONTHS AGO.

Updated a website for an older client today. Realized I originally wrote their website in 2002.

That web site is a fucking non-responsive piece of shit... but it is still running normally after 18 years.

Just HTML/CSS and some light JS/PHP for form processing. It's not fancy but it still performs and works perfect on Desktop and OK on mobile. Mobile devices which DID NOT EXIST when I wrote it.

Let this be a lesson to the entire new class of developers who seems to think you need some framework to develop. You don't. And I GUARANTEE if that site used any framework that framework would have been retired or updated to un-useability 10 years ago.

Meanwhile my LAMP ass "web native" shit spaghetti with ZERO DEPENDENCIES is still just chugging the fuck along.

TL;DR, I do node.js now.

__________________

There's much I was working on the past weeks. First of all some of you may know I don't work in IT and therefore always am learning how to make things easier in my workspace with tech. And my boss once told me how annoyed he is converting stuff to PDF for easier sending via mail.

Then I started to build PDF converter with
PHP and the Laravel framework. My first steps into it succeeded and I could even deploy my Pdf-wizard website, but everything feels like a hustle and making this application bigger don't really seems like a enjoyable task for me.

I tried the same stuff with Node.js then. It was damn good. It was simple, because there are plenty of packages wich do this tasks on NPM. Afterwards I spent some time on doing research and ended up learning Express Framework.

This brought new inspiration to me and I wanted to share this with you guys.

So I started in a new job a week ago for a two weeks probation period, im getting payed double than my last job but it's so professionally frustrating.

They use a full php stack with a framework called tinymvc that I never heard of and the last commit is from 2009.

Beside this they implement some sort of "flexible" MVC where a great amount of the logic are inside the views. They have one model for each entity (in theory) but in reality one model have methods for a lot of tables.

Beside this the i18n is done by querying the database for all the translation strings and copying it in every user session, so every session file it's about 400kb where around 380 are duplicated translations.

The views folder is empty because they decided to modify the framework to look for the views in another folder called resource's and the development must be done connected directly to the production database

Above all this shit all the many-to-many relations in the database (MySQL) are handled creating a comma separated field on one of the tables, completely breaking the reference integrity.

So, after a week of work I can't stop thinking who the fuck developed this? In which world this shit is okay? How can I work around this big lake of shit?

how to learn web development in 2018:

- watch youtube video of that new shiny promising framework

- spend hours trying to set up development environment

- spend another hours waiting for the dependencies to install

- spend the next few hours wondering and googling why it wont work even at fresh install

- spend another few hours redoing everything just to make sure you haven't missed a step

- realize that the youtube video you watched is uploaded last week, and now the framework developers mysteriously decided to change literally everything

- spend hours looking for another youtube video until you realize that now you are watching completely unrelated youtube video

- spend next hours wondering how your life become this pathetic while overthinking all of your past mistakes, and now you are just this lonely pathetic person with no clear future and that you will spend the rest of your life working at a fastfood chain below the minimum wage with no social life living on your parent's basement.

For God fucking sake! The absolute worst platforms are TV's.. LG - WebOS has barely any documentation and a framework that runs very poorly. Not to talk about the 200 bulletpoint self checklist you have to go through before you can submit a new release!

Samsung - Tiden TV... Told me to contact a content manager, and I've almost been waiting 3 months now for any answer, haven't heard a word. My boss thinks I should write another email and cc him so Samsung will get scared... Jesus fucking Christ this sector is a bunch of arrogant lazy fucks

Can we please stop using a file structure (YAML, JSON, XML etc) and just changing the file extension and calling it a new file type?

Stop trying to make your software/framework sound more complicated by saying this shit, if you use something, own it and don't try to mask it...

And mini rant over...

Is it just me or what. I had begun learning web development (but prefer C, shell scripting, Linux... ).

One thing that amazes me - besides having to learn 1356367626785576 technologies to get something done and the fact we get a fresh new amazing framework every 0.00000000000234 seconds - is CSS.

Amazing, I made a navigation bar where I wanted the items to be displayed in the horizontal position, so I
.navbar li, a {display:inline-block}

Works fine.

Next day I'm doing the same from scratch, doesn't fucking work. I look the previous design, HTML structure looks identical, I only use a different font face and colors.

After a while I randomly decided to put a <div> around the a element in order to do something else, update the page and... Voilá, text is in line.

Like... Wtf.

I'm like fuck it. No way I want to work with this shit, let's go back to shell.

Everyone and their mother has a JavaScript framework and the NEWEST cool npm module you're an idiot for not using.

It's like musicians and gear acquisition syndrome, coders love to have new stuff even if it's over-engineered, already exists, or redundant.

Hate dealing with tech hipsters 🙄 is nothing tried and true anymore?

A word of advice to framework authors:
If I am currently using v2.5.5 of a library, and I update to 2.8.6, I would expect to maybe have to update a few deprecated method calls here and there.
I do not expect the entire API to be completely different, with half the classes totally renamed and restructured. Breaking changes should go into a new major version plz

Perhaps more of a wishlist than what I think will actually happen, but:

- Everyone realises that blockchain is nothing more than a tiny niche, and therefore everyone but a tiny niche shuts up about it.
- Starting a new JS framework every 2 seconds becomes a crime. Existing JS frameworks have a big war, until only one is left standing.
- Developing for "FaaS" (serverless, if I must use that name) type computing becomes a big thing.
- Relational database engines get to the point where special handling of "big data" isn't required anymore. Joins across billions of rows doesn't present an issue.
- Everyone wakes up one day and realises that Wordpress is a steaming pile of insecure cow dung. It's never used again, and burns in a fire.

[wk249]
My specialty, I don't think I actually have specialised in anything, maybe that's why I never run out of work, shove a problem on my desk and it gets done, don't have experience? Welp, you do now!

Maybe that's the point, you see a lot of people fall of the wagon or get stuck without work, and here I am just plowing through the next problem at hand.

My career was founded on trying something new, seeing something and going, it's needs X, or Y and building my own with it - no degree got me into software, and no degree is going to replace the years of experience gained by just trying new things.

It also allows you to be well versed in a lot of areas and not feel the paradigm shift when changing stack, language, framework, or whatever, it's just another tool in the shed that has its purpose.

TL;DR: Stop using React for EVERYTHING. It's not the end-all solution to every application need.

My team is staffed about 50/50 with tenured devs, and junior devs who have never written a full application and don't understand the specific benefits of different libraries/framworks. As a result, most of these junior devs have jumped on the React train, and they're under the impression that React is the end-all answer to any possible application need. Doesn't matter what type of app is, what kind of data is going to be flowing through the app, data scale, etc. In their eyes, React is always the answer. Now, while I'm not a big fan of React myself, I will say that it does its job when its tasked with a data-heavy application that needs to be refreshed/re-rendered dynamically and frequently (like Facebook.) However, my main gripe is that some people insist on using it for EVERYTHING. They refuse to acknowledge that there can be better library/framework choices (Angular, Vue, or even straight jQuery,) and they refuse to learn any other frameworks. You can hit them with countless technical reasons as to why React isn't a good choice for a particular application, and they'll just spout off the same tidbits from the "ReactJS Makes My Nips Hard 101" handbook: "React is the future," "Component-based web architecture is the future," (I'm not arguing with that last one) "But...JSX bro.," "Facebook and Netflix use it, so that's how you know it's amazing." They'll use React for a simple app, and make it overly-complex, and take months to write something that should have taken them a week. For example, we have one dev who has never used any other frameworks/libraries apart from React, and he used React (via create-react-app) to write what is effectively a single form and a content widget inside of a bootstrap template. It took him 4 MONTHS to write this, and it still isn't fully functioning. The search functionality doesn't really work (in fact, it's just array filtering,) and wont return any results if you search for the first word in an entry. His repo is a mess, filled with a bunch of useless files that were bootstrap'd in via create-react-app. We've built apps like this in a week in the past using different libraries/frameworks, and he could have done the same if he didn't overly-complicate the project by insisting on using React. If your app is essentially a dynamic form, you don’t need a freaking virtual DOM.

This happens every time a big new framework hits the scene. New young developers get sucked into it, because it's the cool hip new framework (or in React's case, library.) and they use it for everything, even when it's not the best choice. It happened with Angular, Rails, and now it's happening with React.

React has its benefits, but please please please consider which library/framework is the best choice from a technical standpoint before immediately jumping on the React train because "Facebook uses it bro."

New developers. Tip: There is no silver bullet.

If you like Python, please understand GIL's behavior before making a system that handles thousands of requests.

If you like Java, know that "Write once, run anywhere" is a fallacy. Even application servers don't like the same WAR.

If you like PHP, understand the life cycle of a request before connecting to the database from all corners.

If you like C#, don't make it a small command-line application that will be used on FreeBSD.

If you like C, meet valgrind.

If you like C++, templates are cool, but don't overdo it. And take the opportunity to meet valgrind.

Never use the same tool to do everything. Elect the language and framework for the given need with rationality.

Every time I see a "Java Man", a "C++ Chad" or anything like that, it comes to mind that if he were a carpenter, he would be tightening screws with hammers.

Every lock-in is bad.

Had to integrate legacy code into the new framework.

Me: Where does the virtual sensor come from?
Colleague: It's in the docs.
Me: That step is not in the docs.
Colleague: It is, look into the file $FILE.
Me: Yeah, it's empty :D
Colleague: Nope, it's not.
Me: See, empty (pointing to laptop screen)
Colleague: Why is it empty? (keyboard typing...) Damnit, too many git remotes in my repo :D

I'm intentionally resigning from my remote software development job to teach my company a lesson. The guy who wrote the codes previously really knew how to cook spaghetti 😀😂.

To add a single line takes minutes, because when you do something else breaks, and you'll keep fixing what breaks when you tried fixing what breaks when you try fixing what..... endless loop of bug-fix cycle.

Now they blame it on me.

They won't understand if they don't get someone new, my reputation will fix itself through that..

My first opinion after sighting the codes was, "re-write the whole project using better patterns and architecture", the reply as you can guess, we'll do that later.

I couldn't even upgrade the server to use even PHP 7.1 because the framework breaks, the guy has editted a lot from the vendors files. Don't ever try composer updates.

Two word to describes the situation. "It sucks".

The previous developer needs to be shot, literally.

Trying to integrate old code into a brand new framework... Oh, the pain.

OH MY FUCKING GOD!!!

IT FUCKING WORKS!!!

I tried so long on getting my new Netty based webserver up and running, I think I grew my beard twice... But NOW ITS WORKING!

Need to delete a few unnecessary functions that I needed with the old web server, implement SSL. And I can finally release a version of my framework ❤️❤️❤️

And I might put up one standalone version because - it's the same freaking server every time so I am fucking loving to export it ❤️❤️

Spending all weekend on research and testing for a new feature, finding the perfect framework for it, going trough the API just to come Monday to work and get told by Project Lead: we can't use it, it is not in our stack.

How can it be in our stack!? We've never done anything like that before!

Every new framework be like: 'We are new and better and faster and better. Change quickly cause we are the future.'

Me: But whyyy are you better? 🤔😫

Like restaurants in New York, you can learn a new Javascript framework every month for 15 years and never learn the same framework twice

Switch your tech stack or programming language or development framework to something that you enjoy more.
If it requires to switch the company, do it!
If it requires to learn something new and you think that you don‘t want to, then it‘s probably the wrong goal.

We need to normalize not being a passionate CS guru. You can be good at your job and not have passion for it. You don't have to dedicate your life to your career in every facet.

I don't expect plumbers to sit around their house all day during their free time hooking up water lines. Why is it expected that I'm always reading some dev book or learning some new framework or reading some tech blog?

I do other shit, and that's fine. My job earns me a paycheck and I'll improve on the clock, and when I walk out at the end of the day I leave that shit there.

At most I might converse with you informally about tech but I'm not going to spend my little free time going to meetups and pretending like I care more than I do. If you do that's great, but I'm not you and that's fuckin fine too.

Everything about the company is a mess. The only thing that is decent is the people. And by that I mean they aren't shit.
Workflows are fucked.
Clients are fucked. You're pressuring me to get this shit production ready before new year's eve and you still don't know what the text should say and want to make changes to the UI? The fuck?!
Design is a complete shit show. There is a design team. They only make a fucking psd to show clients how an interface would look like. No mobile version (but it's still expected to work!), no markup. Resolution is fucking inconsistent and whenever a change is requested, they are nowhere to be seen so I have to actually do designing on top of having to use this worthless fucking framework I hate it so much.
Codebases are turbo-fucked because of said framework.
Databases are an inconsistent, fucked up mess. No foreign key constraints because every single fucking table is using the MyISAM engine.

And the thing that really makes me incredibly angry is all the "custom systems" look the fucking same at the database level. Like 30 fucking useless tables made for stupid HR workflows that make no fucking sense.

So here I am sitting on my dusty laptop gaming laptop (because supposedly it would offer me better performance in compiling code and working with CUDA according to the people above me) at a research institute where I just started working at. I am told that there are some issues with the code and that it fails to build on Windows with MSVC that ships with Visual Studio 2017 and later.

I poor some hot tea from my insulated bottle I brought from home and start reading.

I look in this header file and what do I see - a custom uint24_t struct. Interesting...

I keep sifting through the code base. I find some functions that check and change Endianess. Ok, but the software is developed, built on and runs only on Win7 and later desktop systems. Never mind...

Further I find a custom "allocator" that is used throughout the whole code base. It has three inline static class member functions: allocate, copy and deallocate plus some private constructors. And these just wrap around the standard new and free calls. Some flavours of this class actually only deallocate (with a comment above them: "This allocator does not allocate. HANDLE WITH CARE!!!", which is btw the only "code documentation" I have managed to find).

But wait! What is this? A custom thread and mutex. Oh, and string, and vector.

Further down the rabbit hole I find a custom math library with a matrix class that does not support multiplication between a matrix and a vector. Perhaps not a use case I guess...

I continue and come across some UI-related calls. Interesting, I wonder what they are using as a framework. Oh, my...We have an extensive GUI custom framework written from scratch (drawing buttons and all).

All of this is to load an OBJ file and render it on the screen on a standard Windows PC in some way.

Very nice... ;_;

FUCKING FUCK ANGULAR!!!!
LIKE FUCK IT IN THE ARSE AND BURN THE MOTHERFUCKER WHILE LAUNCHING A MISSILE ON IT TO BE SURE!

(ﾉ≧∇≦)ﾉ ﾐ ┸━┸

So I am making something on angular and I got everything running in ng serve(development environment) , after handling all issues and showing it to my boss man he approves and asked to put it up on prod for a demo , doesn’t sound like an issue , I make the prod build on cli and BAM! 16 errors ? No issues right?, I’ll just google the issue. Googles.... there aren’t no clear solutions to it as the angular version keeps changing and nobody knows what broke it, I mean people have the issue,but like 100 reasons that can cause it,
HOLY LORD RELEASE A NEWER VERSION AFTER MENDING THE OLD ONE
But nooooooo!

Angular Dev:We fucked this one, lol what should we do boss man?
Angular boss man: lol just leave it, we need to build the new version with newer bugs,

P.S. I like angular, but it’s like a underdeveloped framework, too many issues and too many changes

!rant
I am on vacation from my full time job this week. I wanted to use this week to write a PoC for a potential customer of my side business. really interesting project for me.

potential customer is a window and door manufacturer and needs an application to manage their racks.

their ERP system already has a simple rack management but it is only useable in house.

they want the drivers to be able to scan racks they deliver to a customer with a native app and they want to have a webapp for the customers to see racks that are assigned to them as well as reporting a rack ready for collection. And that all needs to be in sync with their local ERP system.

as i am a .net guy i decided to go with the abp framework (because it got recommended to me) and xamarin for the native app part (because i have experience in this).

i have now spent 4 days implementing this and it has been so rewarding. the framework is so powerful and it's template saved me endless hours.

i even wrote a very basic connector service which synchronizes data between my app and the clients ERP system. Just one way until now because of time issue, but i learned to scaffold an ef core with db first. It is noticable that the ERP system is 2-tiered - meaning the clients directly talk to the db.

Tomorrow i will implement the xamarin client.

4 days just coding what i want to. choosi g my own velocity and making my own priorities without any interruptions or discussions and a bunch of new things to learn.

Probably wasted half a day because of stupidy (implemented some bugs) but fixing and learning is part of the journey and i lime that part, too.

i am so relaxed right now 😁 just wanted to share this without a real reason :P

So lets start here, as i have been preparing myself for a while for that rant. I have been putting it off for a while, but today I had enough.
Fuck react-native and fuck facebook react-native team. Bunch of lazy incompetent twats.
The all amazing framework that suppose to be speed up your development process, since you don't have to compile your code after each change. SO FUCKING WHAT if the god damned framework is so fucking buggy and so fucking shit that you constantly have to fix build, dependancies etc issues. Every day since I work on this project that is using react-native I have to deal with some of the react fucked up behaviour. You got an issue ? don't worry google it just to find out that 100 other people had the same issue. Scroll through down the bottom of the page just to find out that facebook devs have closed the issue as resolved (without fucking fixing it) because there wasnt recent replies to the post. Are you fucking kidding me? It's ok thou, create a new issue just to get an automatic reply from the bot that locks the thread and keeps it locked till you update your React-native version to the newest one. You do that and guess fucking what? Their newest version fucks up remote debugging on iOS(fucking android been broke for over a year) so say good bye to debugging your js code. Documentation is fucking trash. You found a nice function like autoCaptialise on your text input? Great! Ah wait, its not fucking working, what is wrong? You google this just to fucking found out it, function never worked on android, so why the fuck you still have it exposed and still have it in your docs? You want to add package? So fucking ez, just type npm install <name of the package>. Ha! fuck you, you still have to go and add them fucking manually in gradle in android and in pod in xcode, because obviously react-native is a one big fucking bullshit. Oh and a scroll view is a fucking glorious highlight of that framework, try add some styling to it, you gonna have loads of fun. Fuck react-native. And fuck the fucking idiot who convinced my boss that framework is so fucking great and now I have to work on this shit. Sincerely Xamarin Developer.

Imagine if libraries and framework you were using started making chabgelogs like the one they make in the mobiles apps.

*We've made some new features and some buh fixes 💫*

Last year I planned to start a startup. I've started many good things but not the startup yet.

* A new data format
* A new data type
* A new web framework
* A new concept for logging
* And many other opensource tools and libraries

Management has been promising we'd leave .NET framework for 2 years now. Never fucking happens. A new ASP.NET project was just started last week and yup, OF COURSE, its .NET Framework 4.8.

I'd even be happy with one of the earlier .NET Core versions at this point for fucks sake. I have no clue why tech leads are so happy to create a brand new project on a deprecated framework version.

And yes, I have checked thoroughly. Our whole infrastructure works with .NET Core onward. People are just too lazy to learn new stuff.

Stuff like switching to .NET 6, actually doing unit testing, improving our CI/CD pipeline, refactoring problematic codebases, etc. -> all this stuff is the kind of things they promise me I can work on later whenever I'm so bogged down with work that I'm looking for a light at the end of the tunnel. All empty promises.

Ideally we should be on .NET 6 since its LTS and just stay on the LTS versions as the year goes on.

Not planning ahead, just start at some point, adding just a tiny little feature after another, and then wondering why your to do app (just to check out a new framework or language) suddenly comes with Blockchain, a chatbot and a machine learning algorithm that (slowly) learns when the best time to show random cat videos is...

the real truth is that web dev has been running around in circles on itself for over a decade now

"but every framework is 'new' and 'shiny'!!!!"

nah, just more sugar on the same exact concepts that have been around since day 1

Rant

I'm tired of this shit!!!

First I receive a task to create a new functionality for the app that I'm working on and some documentation (this is the only good part of all the rant) but no design.

It's been 2 weeks since I got assigned to this and still no design, no assets, no API calls that ACTUALLY WORK.

Today was testing a plist to get a banner link, and for 1 hour that little fucker didn't returned the image I was asking.

Better, I wasn't getting ANY IMAGE. Turns out that the link sends me to a HTML URL that doesn't have any image... go figure!

So I've been working on this from some images inside the PDF with the documentation given.

Oh! Wait! There's more!

The cherry on top is that I'm implementing a chat/voice call/video call into the app and the framework that I will be using is being created now, and it's not even finished!!!!!!

The wonderful feeling when i need to implement new functionality but it only takes a few minutes bc I actually created a framework that I can reuse instead of writing duct tape code from scratch 😎😊😆😙

Using a new framework without reading the API.

In cour company we need an online dashboard that monitors logfiles from various interface processes.

My collage and me, the newest company members (for almost 2 years) get the task to build this and get it presented as some intern project where we can try out some more recent technologies/frameworks.
Now in the first meeting our senior team leader told us we shoeldn't use the noew hot buzzword js frameworks.
Reason? They are not proven and wil probably lose popularity next year and we don't want to migrate everything every half year. Plus he had negeative experiences with Angular in some project he had to work on, probably just because his limited JS skils.
So he wants us to use jQuery to build a modern web application.

I get it you don't want to migrate to TheNewHotThing(tm) every year. Guess what? You fucking don't have to. If I build sonting in Vue.js now, it won't stop working when a new framework comes along.
Look at our own fucking ASP.NET Web Forms prooject, that stil works. Just don't deny the usability of modern frameworks.

Had a new co-worker I was responsible for training. I am several years his junior, but he is working with a new language/framework I'm fluent in. Day 4 into training, he walks into my cubicle, sidles up next to me, I look up at him, he farts loudly, then (without seeming to realize what he's done) he proceeds to launch into a long-winded question about coding best practices.

If this were an isolated incident, I'd have written it off, but the dude did it again when he came to my desk and asked me to open a jar of pickles for him, and many times over during casual conversation.

First Post since... Long I guess?

I got a new project!! I am currently creating a Webserver Framework in Java. I can create fully functional websites with a few lines of JSON.
(Look below)

Currently I don't have direct Javascript support, but I am working on installable modules. With those the Web-Admin can code little code fragments that can be shown (live) on the webpage.

I am so hyped because it does work <3

(Pictures of development might follow)

(Can I even call it framework? Hm dunno.. )

Everyone I work with: If we use <framework> then we can solve <insert complex low level issue>.
Me: That is great but what is the actual solution design?
Evwryone: We use <framework> to solve <issue>.
Me: Yeah I get that.... But how? What is the plan? The architecture of this new system to support <framework> and are there issues that get created?
Everyone: If we use <framework> we won't have the issue we are talking about.

You know what really grinds my gears more than anything else? Not having anything to work on at work.

That might sound like the most german thing to say but bear with me for a second.

Even though i am almost one year into my job as a junior dev, i consider myself and i probably am very new to the coding world. And even if i weren't new i would still have to continuously learn and improve. And every time i just sit in front of my working station, with nothing to do, i'd rather figure out an incredibly tedious bug, learn lisp or deal with a shitty framework.

Most of the time i don't know what to do. I improve my workflow with some bash-scripts and aliases, i read into the details of certain tools but at the end of it, i can't really get into something deeper and get value out of it because actual work might just be around the corner...

Haha, today I learnt that agile doesn't just stop in the enterprise with SAFe (Scaled Agile Framework), management has continued the theme in my new company with Lean-Agile Center of Excellence (LACE) and Agile Release Trains (ARTs).

Software development in 2021...

Just needing somewhere to let some steam off

Tl;dr: perfectly fine commandline system is replaced by bad ui system because it has a ui.

For a while now we have had a development k8s cluster for the dev team. Using helm as composing framework everything worked perfectly via the console. Being able to quickly test new code to existing apps, and even deploy new (and even third party apps) on a simar-to-production system was a breeze.

Introducing Rancher

We are now required to commit every helm configuration change to a git repository and merge to master (master is used on dev and prod) before even being able to test the the configuration change, as the package is not created until after the merge is completed.

Rolling out new tags now also requires a VCS change as you have to point to the docker image version within a file.

As we now have this awesome new system, the ops didn't see a reason to give us access to kubectl. So the dev team is stuck with a ui, but this should give the dev team more flexibility and independence, and more people from the team can roll releases.

Back to reality: since the new system we have hogged more time from ops than we have done in a while, everyone needs to learn a new unintuitive tool, and the funny thing, only a few people can actually accept VCS changes as it impacts dev and prod. So the entire reason this was done, so it is reachable to more people, is out the window.

So my IT teacher wrote his own web server framework for NodeJS and he forces us to use it for assignments. Would be fine if:
1. It worked properly.
2. It had any kind of documentation.
3. He knew how it worked.

But no, we have to debug his shit and edit the js files in node_modules to get shit working.

Is he open to suggestions? Not really. If you have a fix, you have to create a gitlab account and send a pr. Even if you tell him what exactly is wrong. He won't do anything about it.

Why use express when we can learn something we'll never use again?

At this point I think we're using it only so that he gets downloads on npm.

Oh ya, he also copies package.json from project to project instead of creating a new one with up to date dependencies.

🙃

PM: I need a brand new feature that we haven't had before and it has to have a framework backing it so that we can extend it to anywhere in the future. It also has to have X, Y, Z, it has to be able to tell the future, cure cancer, fly, and have a return on investment for us of 1000x. How long will that take?

Me (or any dev ever): Umm... well, that's kind of asking for the moon. The first few pieces will take as least 5 sprints. When do you need it by?

PM: Tomorrow. When can you have it?

Me: ......

Seriously, at what point did the good, kind, selfless souls who write tutorials and guides online turn into fucking food bloggers?

I've been an engineer about 15 years, so I still have to google most of the code I write as I write it, and this week I've been learning a new framework.

Ten years ago it'd be "here's how to..." then the thing you want to do.

Now it's "For the longest time, I didn't want to use Gradle..." followed by a summary of the last week in their life.

I really don't care about your Journey with Rust, I want to know how to define an optional parameter. I don't give a rat's fucking dick how much faster this is than that, my hands are tied by whoever started this mess - just tell me how to make it work.

I guess there's something to be said for remembering things between sessions.

Started a new job as a senior dev but with a framework I've never worked with and I just feel like I'm slow AF and just not qualified for the job. I'm sure it doesn't help that I'm greiving my dog that passed last Tuesday.

You wrote a little simple and clean mvc framework to work faster on some new projects. It can "compile" tags as {% var %} or {% array.key %} in the html code with support of {% for arrayOfHash in hash %} foreach construct and nice features, it can call api's callback in a smart way as ghost methods of a class, he can make routes with the route provider. You tested it and made a little example, after you went in the bathroom you read the index code and you started staring at the beauty and elegance of it. You go to bed happy and sleep. The day after you wake up and realize that it's unuseful because there's a lot of mvc framework that surely are better and ready to use, so you lost useful time. Have you ever feel this way? MVC: Me Versus Creativity.

Its hard for a developer. Started to learn a new framework or CMS. By the time one gets familiar and fluent, a new and better one is already out.

Just the fact that you wrote your simple single page "contact us" website in React shows that you have no idea what you're doing, nor do you have any idea what the actual benefits of React are and in what situations it actually shines. You're just jumping on the React bandwagon for the sake of saying "I wrote it in React," and your decision to use React for that simple website is going to effectively increase It's development time without adding any additional benefits.

Each framework has its advantages and disadvantages. It's worth it to pay attention to these advantages/disadvantage, and choose the best framework to fit your needs. Don't just use a particular framework because it's the hot new craze. Use a framework because it's the right choice from a technical standpoint, and presents you with advantages that fit your application needs.

When you work with other developers who would, for any feature, small or large, plop in a new library or framework of which they will utilize 1% of... I'm talking about things that we could develop in house in less than a day and have significantly less code bloat... and when you tell them this they smile, nod, and say yeah gotchu, and continue on... AND YOU HAVE TO MAINTAIN THE DAMN THING.

What you could have:
- simple project structure
- common lib with modular logic
- import logic as needed in you services

What you do:
- waste months to write an opinionated framework that works only if used in a super specific way
- have a fat sample project as example
- use a code generator to copy and rename the said sample project whenever you create a new service
- have everything break whenever something new is added in the framework
- oh and keep the framework in active development while others work on the client services, so lots of things will break often and out of nowhere

Fucking god, i hate when people make pet projects out of work projects

FUCK.
NEXTJS.

...

THIS PIECE OF FUCKING SHIT WORKED 4 DAYS AGO.

I CHANGED ***NOTHING***.

4 DAYS LATER I START THE PROJECT AGAIN AND HALF THE STUFF BREAK. NOTHING FUCKING WORKS!!!!!!!

SOMETIMES IT WORKS SOMETIMES IT BREAKS

MESSAGES GET SENT SUCCESSFULLY 2-3 TIMES IN A ROW AND THEN Random 401 error

Random page glitch flickering when routing to new pages rendering the content blank

Random list map iteration crashes on ui dev side

This is such a fucking SHIT

Now i started my angular and spring boot exact same project that i stopped worjing on since october 2023 AND EVERYTHING WORKS FINE WITHOUT ANY RANDOM ERRORS

RANDOM ERRORS ONLY HAPPEN FOR NEXTJS FUCKSHIT FUCKING FRAMEWORK

FUCKIEST DOGSHIT GORILLACUM MAD FUCKIJNNGG RETARD FRAMEWORK FOR AUTISTICS I WASTED SO MUCH TIME LEARNING THIS PIECE OF FUCKING GARBAGE!!!!!!!!!

The thing that I most hate is when you're approaching a new framework/tool, you follow the official documentation and the first example doesn't work.
I'm trying the official documentation of webpack, I tried the first example and guess! Error! It says that's probably a breaking change. Where the hell should I learn it? I don't have the crystal ball, should I guess how your fucking tool fucking works? Oh my god, it's ok if you introduced breaking changes, but just update all the references, is it so hard?

Just started learning gnuplot yesterday. Sure, it's not the shiniest of tools, but I'd heard enough about its performance to give it a go.

It's like learning vim. You Google thrice to write a single functional line. You spend hours trying to find a single command for a single task.

But. GODDAMN. This thing's the fastest plotting framework I've ever dealt with. I love Matplotlib, but as great as its plots are, when I need to plot shit up in half a second, I've found a new friend.

Also, tutorial suggestions appreciated.

[Last year me]: Dammit, javascript is the worst language ever! Where are my var types? Why are there so many frameworks? Why the people are using it? Why? Why?

[Today me after updating my Linkedin profile with my javascript experience and receiving some good job offers almost instantly]: Oh good Lord, thank you for giving Mr. Eich the wisdom to create such a beautiful language, I'll build a new framework as a sacrifice to show my gratitute.

Rolled out a new application I built almost entirely by myself 2 days ago... But my dev group is understaffed and has a project manager who is literally the most clueless person I have ever met, so as a result, we don't have a functional/useful dev/test/prod framework and no standards for how to deploy apps. So my past 2 days were comprised of fixing bugs in the live system that could probably have been caught if I had the time and resources to get everything thoroughly tested. It's stable now, but damn our management for being generally idiots. Our motto appears to be "Fuck it, we'll do it live"

How is coupling backend + frontend as a single nextjs app a good idea? What the fuck is this?

What if you have to create new replica sets of a backend because of high load pressure? What about load balancers?? What if i want my backend to be a microservice? How do i unit test the backend if its cluttered with frontend? WTF IS THIS

WHY DID NEXTJS THINK THIS IS A GOOD IDEA AND WHY DO SO MANY DEVS LOVE THIS IDEA AND GLORIFY NEXTJS?

Nextjs seems like the type of framework that was built by a frontend web developer who just refuses to learn backend technology at all costs.

---

its been a few hours and the concept of nextjs is bending my mind rn. I thought nextjs is just another frontend framework. A react killer. Only to find out its both a backend + frontend framework.

Cluttering backend stuff into frontend is gonna get messy no matter how much you try to modularize the code. Am i lost or am i right???

---

Scratching my head over nextjs. Looks like a great framework for small-mid project but definitely not large project. The more shit the project needs the more messy shit become. Angular has modularized all of this in separate folders -- components services guards interceptors (now new stuff coming called Signals) etc. All of it is separated in individual folders and kept frontend-only. Simple enough. No backend clutter

---

Can i even use nextjs strictly as a frontend framework while it uses my custom backend built in java spring boot? For example use nextjs /api/ folder to handle custom routes built outside of nextjs framework?

Am i insane here

Every new front end framework these days, i remember the time when I used bootstrap through cdn link... Yup those were the good old days

So I recently started a new job and there's a boot camp as part of the on boarding process. I'm new to scala, I have python and golang backend experience.

During the scala session, the CTO shows us some examples and gives us an exercise to create a Todo REST API with user authentication, then goes to a meeting.

He was using a library called "bacon" in one of his examples, so we were busy struggling to get shit to work and googling "how to do x with scala bacon lib" with no results and we finally gave up.

CTO comes back 30 minutes later and wants to see to how far we got, so we ask him about this bacon lib only to find out that it's their own awesome framework. &$!#%

I can't remember the last time I had THIS MUCH FUN developing an Android app! 😳 Have a paper due, but learning RN is actually making this pet project a huge distraction! 😳 This is a whole new world of mobile development 😆, but what if another framework takes it's place 😵. But there's still people who know Angular, and that's widely used...right 😓 and moble dev has never been this easy, so maybe it'll stick around like Node...

who cares... I'M FUCKING LOVING React Native now!!! 😆

that feel when I am the only one in team who knows at least one framework.. and coworkers refuse to learn and instead copy and paste code parts from old, insecure apps into new apps... 😐

I was working on a project for a presentation and had a really bad cold. I was building something in JavaScript and the framework was all new to me. No one else wanted to touch it so I said i would have a go.

Basically I put everything I could into it and the director walked in and started using it, ignoring me who wrote it, talking straight to my boss about loads of changes.

I sat there and quietly and thought whatever I did they would change it again as they don’t know what they want.

I felt crap the next day because of the cold and the previous days experience, so I called in sick. I got a load of abuse about the deadline for the presentation and this time I gave it back and said maybe someone else should have stood up and taken that project then. I wasn’t taking anymore of that crap.

I spent most of a day a few weeks ago tracking down and fixing a NaN bug in a framework I use. I hacked it into my local copy of the framework's code.

Today I have the same bug, and after several hours of searching I finally realize I'd updated to a new version of said framework and so had overwritten my fix....

FML

We recently hired a new developer, fresh from uni. Very little real experience as I can see.
Unfortunately I weren't available for the interviews, so they chose a dev without me.

All his code is messy, over complicated and uses symfony framework for _everything_
He can't do shit outside of it.

He was tasked to find and replace some links in a few hundred excel documents, he spent ages trying to parse the xlsx documents and the replace the links and write to the document. Spent all day on it, with no results. Even though I often asked him how he was getting on, he said all was fine.

End of day, I get a tad furious, whip out my terminal and do the whole task in 10 minutes with basic bash

Hi Everybody,
Here by I introduce you the new Java Script framework and package manager that is going to change your life forever. We have considered all the problems developers are facing during their everyday career. We use latest techniques used in configuration files (xml, yaml, json, etc.), package managers (npm, gulp, yawn, etc) and other frameworks (require-js, vuejs, reactjs, etc) into consideration to bring you a framework that has them all together in ONE BIG PACKAGE! HAHAHAHAAHAAA!
Nope. I'm just kidding :-D

I was given 6 whole months to rewrite some old monolithic web app exactly 5 months ago today. Now I have to show my boss the progress I've made. How do I explain him that I wasted my time in this order:
1.- heavy procrastination
2.- try new frameworks to work with, pick one, start writing the app, regret and start over again using a different framework.
3.- devrant
4.- existencial crisis and self doubt.

Now all I have are a bunch of incomplete buggy modules and a mental breakdown.

A little background on project fubar:

Project fubar was started a couple of years ago, by an entirely different set of devs, against an entirely different set of requirements which were never made transparent to this day, on a new platform and framework.

That means it had APIs either outdated or deprecated, front-end logic that did things it wasn't supposed to be doing and lots of scope creep and technical debt.

I had to support and fix fubar for the last few months to prime it for UAT. It was the equivalent of plugging leaks which created more leaks.

Finally, I couldn't take it and asked for a week off. I timed it so it would be right after what would have been the final UAT deployment and I'd be back after they completed their test rounds, so I could fix any new or returning defects.

Today I just found out that fubar got put on hold, that UAT was a failure and all fubar-related work had to stop. I have some mixed feelings on this: I worked hard to get fubar working as business wanted, and I was proud of that. But I also didn't like that fubar was constantly changing in scope and function.

I wonder if anyone else has ever felt the same thing?

lambda lambda lambda!

So I was tasked with porting a bunch of code to a new set of libraries a few years ago. I didn't have a whole lot of experience with the framework at the time. I just fixed issues with what I thought should be in there. I mean it compiles right?

Fast forward 4 years:
Coworker: Uh, Demo, this printing code doesn't work. A customer is complaining.
Me: I didn't work on that.
Coworker: Yes, you did...
Me: Oh, yeah, I remember that. I just guessed. I didn't know what I was doing back then. It looks like I am not waiting for the printer. I will put a lambda in there to notify when the printer is ready. Then another lambda inside of that to delete objects when that is done. Hey! I put a lambda inside lambda!
Coworker: Thanks, it works now.

Talking to my boss later. I had just explained how I fixed the issue:
Me: I put a lambda inside a lambda! Wait, I have a new goal. Putting a lambda inside a lambda inside a lambda!
Boss: Uh, I am not sure that is a "good" goal...

*sees a new tech/framework/language*

*dives straights to download just checking for windows/mac/linux*

*downloaded product doesn't start/gives error/complains because some prerequisites are not met*

*after some frustration it starts to work*

*To not offend the Gods, writes "Hello World"*

*Carry a "Hackerman" face all day*

*Updates resume*

FUCKING MOZILLA!
>Quantum
>over9999 times faster
-Ughm, okay, but what is the trick?..
-THE TRICK IS THAT NONE OF YOUR FAVORITE ADDONS WILL WORK!!!

Seriously this is fucking insane! Several of my addons which were essential for me to stay sane is gone and I don't even know how to live without them. And all this bullshit is happening because these idiots in Mozilla decided to enforce use of WebExtensions. For ones who unaware, WebExtensions is much, much poorer framework and many cool addons simply unable to work under WebExtensions because of its limitations.

Are you the one who loved the speed and joy of using mouse gestures? GUESS WHAT ­— IT'S GONE.
Maybe you made your browsing activity super efficient with use of the “Tab Groups” addon that used to allow you to group your browser sessions? SAY BYE-BYE TO IT!
And many more!

Most importantly, I cannot understand why would a company enforce use of a framework that will decrease functionality of a product.
Anyway, it seems like Firefox is not a browser for addon enthusiasts like me anymore; got to find a new one, any recommendations?

Betrayals and Affairs ..

After trying development with vanilla js, then with the help of jQuery, then AngularJS, then Angular, then Vuejs, then React,

I spent the last 3-4 years of my life loving React and devoting all my frontend projects to React. React was so simple and straightforward and I ... I committed to it

but, I recently checked out Svelte, and maybe i shouldn't have let curiosity take the better of me but i did and, im heartbroken to say, I can no longer love react the same way. as nice as react was, like in any relationship, we had some ups and downs, i got bothered by some little details that i learned to live with, but Svelte .. Svelte solved these little twirks and it just felt even simpler...

I created a new Vite project today, and it asked me what framework to initialize, and i kept hopping between React and Svelte. for 10 minutes i was thinking of all the history i shared with React, of how scary it is to commit to something new, but i clicked on Svelte.

I know i may have betrayed a commitment to React, but sometimes things pile up and i .. I had to listen to my heart

Forgive me and thank you for reading my confession

That feeling when you're almost done with your personal project using an entirely new language and framework :)) been working on it for the last 2 weeks. 62 commits in!!

F*ck JavaFX. I mean, how a GUI framework doesn't have a standart navigation procedure? It is not even possible to create a page by constructor. In many other framework when I wanted to pass a data to a page, I just had to write
"new MyPage(SomeClass someObject)"
but in javafx I have to first create a constructor, link the fxml file to it then show the page.
Actually I am not angry. It is a big mistake to wait a good GUI framework from a company that has a website something like that in 2018.

I wish we’d stop coming up with “the new best js framework out there” every fucking quarter of the year

New day. New legacy project that needs triage.

The project has existed since before 2000 so it all "works" and has no known business logic bugs. It does however have performance issues which sure I can have a look. It can actually be quite fun and rewarding to optimize performance.

This is a titanic dotnet framework leviathan consisting of over 12,000 cs files using razorpages, entity framework, and... nhibernate? I have my gripes with both EF and NH but they are both fine if used correctly, like any other tool. I've never seen them used together however.

As It Turns Out™, NH was implemented first and at a time when NH did not support async operations. It made sense if you look it up and it's meant to delegate commands via a separate layer, but different story.

Then for... reasons... EF came in and gradually took over.

Because of the way this is all set up, everything will faceplant if you try doing anything async, even if it has nothing to do with calling the db. Any attempt in making this work leads you down a slippery slope of having to rewrite the entire thing, which is out of the question in terms of their budget and expectations.

Sometimes it's a detriment when it works in spite of its issues.

So when we started this project like 4 years ago... new to the framework, kickstarting lot's of forms with file uploads. Everything seemed to work fine, uploads and downloads worked..
First version of the project got deployed to prod and for weeks or so users have been registering and submitting stuff...

Only problem was: most files were overridden by consecutive uploads as our central upload lib stored files with the same name on disk (normally the ID of the db row was injected but most files were saved before the db row was - resulting in 0 IDs...)
Yeah so... that hurt :(

I'm finishing up the most depressing client engagement ever. Ultimately it all traces back to their worthless Expert Beginner EA who thinks he's a genius but can't write code. I don't mean that he's not great at it. It's some of the worst I've ever seen by a person in his position.

In the time I have left here I could do so much to help them clean this stuff up so that future developers could ramp up more easily and there wouldn't be tons of duplicate code.

But I've just given up. You can't help someone who thinks their code is perfect. I don't even bother suggesting stuff any more (like don't have two methods in a class - a "real" one and one for unit testing) because he gets mad or just says that's his "pattern."

If I have a useful improvement, first he'll want me to put all new code in some new library, which is fine as an end result but you don't start with putting single-use code in a library separate from where you're using it. You work with it for a while to see what's useful, what's not, and make changes. But, you see, he just loves making more libraries and calling them "frameworks."

He tells me what he wants me to name classes, and they have nothing to do with what the classes do. When you haven't done any development yet you don't even know what classes you're going to create. You start with something but you refactor and rename. It takes a special breed of stupid to think that you start with a name.

I've even caught the dude taking classes I've committed and copying and pasting them into their own library - a library with one class.

The last time we had to figure out how to do something new I told everyone up front: Don't waste time trying to figure out how you want to solve the problem. Just ask the EA what he wants you to do. Because whatever you come up with, he's going to reject it and come up with something stupid that revolves around adding stuff to his genius framework. And whatever he says you're going to do. So just skip to that.

So that's the environment. We don't write software to meet requirements. We write it to add to the framework so that the EA can turn around and say how useful the framework is.

Except it's not. The overhead for new developers to learn how to navigate his copy-pasted code, tons of inheritance, dead methods, meaningless names, and useless wrappers around existing libraries is massive. Whatever you need to do you could do in a few hours without his framework. Or you can spend literally a month modifying his framework to do the same thing. And half the time his code collapses so that dozens of applications built on his framework go down at once.

I get frameworks. They can be useful, but only if they serve your needs, not the other way around.

I've spent months disciplining myself not to solve problems and not to use my skills.

Good luck to those of you who actually work there. I am deeply sad for the visa worker I'm handing this off to. He's a nice guy and smart. If he was stupid then he wouldn't mind dragging this anchor behind him like an ox pulling a plow. Knowing the difference just makes it harder.

When you’re struggling, learning some new framework or concept and your friends still think the entire internet is made solely with html and css because they took desktop publishing in 9th grade.

The more I investigate mobile development the more it becomes apparent to me that modern development is a *massive* pile of technical debt thats going to burst, crash, and burn one day, along with the entire industry.

If it takes a newbie more than ten minutes in your framework to add a fucking *button* and navigate to a new screen, then your framework is shit.

* Start maintaining/upgrading new project at work
* Read book on best practices for the framework
* quickly realise all the "don't do this" parts of the examples in the book is EXACTLY how everything in the project is done
* cry self to sleep

Salesforce lightning web components have such bullshit limitations that they claim is because of security but it's just because it's overengineered garbage.

Want to use web components? Nope.

Want to pass in a value to a function in a click listener expression? Nope.

Want to use scss? Nope, compile it to css yourself.

Want to use the fucking document object? Guess what it's overridden except for very specific third party frameworks.

Who in the fuck thought it was a good idea to override the document object? Your app isn't more secure, literally the entire internet uses the document object and it still becomes available in runtime anyway so what the fuck??

LWC is the biggest garbage I've ever seen, you know a framework's a big red flag when there are developers solely for the framework.

There is a new security release coming out that apparently removes some of these nuances (understatement) so there might be some light at the end of the tunnel.

Last night I looked at an Android app.
Going to put it bluntly, I don't like java much.

But Android takes it to a whole new level.
I was talking to our (SlimRoms) framework dev about how the database transactions used to take 400ms, and it was cut down to 10ms by, changing to xml with some kind of a reflector (so xml would be saved in the background).
This is atrocious. As a web developer, I live in a world where you can do thousands of transactions in that time (albeit on faster hardware).

So how is it that all of the abstractions in Android add up to a single read/insertion in Android (and I'm talking about an app written by Google) takes 400ms?

Every time I go in that channel to talk to them, I find something screwed up. Gah.

So this company called me for an internship interview. They told me to learn a new framework and develop an entire system with it within a week so as to get a chance for the internship. Jokes on you. I ain't coming back you SHITHOLES.

!rant.

I must say I love learning new things!!! Took a quick detour to build a small custom music player, now it doesn't seem to be that quick as I am learning a new framework. Only about 11 pages of many more still to go, and the funny thing? The main part I need - how to play audio, is in the last section of the tutorials.

I have a programming tutorials website I built from scratch in the PHP framework Laravel 5.4. Recently my friends have been pushing me to use WordPress instead.
I haven't worked with WordPress yet but I just hate it. I always think that it will not give me the flexibility I might need when adding new features.
This has put me in great doubt and anxiety about what I'm doing.
Is wordpress a better choice? I'm I just being lazy about the WordPress stuff?
I'll appreciate any advice on this.

When your boss ask to convert the system to the new framework version, but still ask the other team add new module. Then said why your work never done hmmm.

- And also today I completed my to-do list
- Did you carry all the tasks out?
- No, just a new JS framework

When the CTO/CEO of your "startup" is always AFK and it takes weeks to get anything approved by them (or even secure a meeting with them) and they have almost-exclusive access to production and the admin account for all third party services.

Want to create a new messaging channel? Too bad! What about a new repository for that cool idea you had, or that new microservice you're expected to build. Expect to be blocked for at least a week.

When they also hold themselves solely responsible for security and operations, they've built their own proprietary framework that handles all the authentication, database models and microservice communications.

Speaking of which, there's more than six microservices per developer!

Oh there's a bug or limitation in the framework? Too bad. It's a black box that nobody else in the company can touch. Good luck with the two week lead time on getting anything changed there. Oh and there's no dedicated issue tracker. Have you heard of email?

When the systems and processes in place were designed for "consistency" and "scalability" in mind you can be certain that everything is consistently broken at scale. Each microservice offers:

1. Anemic & non-idempotent CRUD APIs (Can't believe it's not a Database Table™) because the consumer should do all the work.
2. Race Conditions, because transactions are "not portable" (but not to worry, all the code is written as if it were running single threaded on a single machine).
3. Fault Intolerance, just a single failure in a chain of layered microservice calls will leave the requested operation in a partially applied and corrupted state. Ger ready for manual intervention.
4. Completely Redundant Documentation, our web documentation is automatically generated and is always of the form //[FieldName] of the [ObjectName].
5. Happy Path Support, only the intended use cases and fields work, we added a bunch of others because YouAreGoingToNeedIt™ but it won't work when you do need it. The only record of this happy path is the code itself.

Consider this, you're been building a new microservice, you've carefully followed all the unwritten highly specific technical implementation standards enforced by the CTO/CEO (that your aware of). You've decided to write some unit tests, well um.. didn't you know? There's nothing scalable and consistent about running the system locally! That's not built-in to the framework. So just use curl to test your service whilst it is deployed or connected to the development environment. Then you can open a PR and once it has been approved it will be included in the next full deployment (at least a week later).

Most new 'services' feel like the are about one to five days of writing straightforward code followed by weeks to months of integration hell, testing and blocked dependencies.

When confronted/advised about these issues the response from the CTO/CEO
varies:

(A) "yes but it's an edge case, the cloud is highly available and reliable, our software doesn't crash frequently".
(B) "yes, that's why I'm thinking about adding [idempotency] to the framework to address that when I'm not so busy" two weeks go by...
(C) "yes, but we are still doing better than all of our competitors".
(D) "oh, but you can just [highly specific sequence of undocumented steps, that probably won't work when you try it].
(E) "yes, let's setup a meeting to go through this in more detail" *doesn't show up to the meeting*.
(F) "oh, but our customers are really happy with our level of [Documentation]".

Sometimes it can feel like a bit of a cult, as all of the project managers (and some of the developers) see the CTO/CEO as a sort of 'programming god' because they are never blocked on anything they work on, they're able to bypass all the limitations and obstacles they've placed in front of the 'ordinary' developers.

There's been several instances where the CTO/CEO will suddenly make widespread changes to the codebase (to enforce some 'standard') without having to go through the same review process as everybody else, these changes will usually break something like the automatic build process or something in the dev environment and its up to the developers to pick up the pieces. I think developers find it intimidating to identify issues in the CTO/CEO's code because it's implicitly defined due to their status as the "gold standard".

It's certainly frustrating but I hope this story serves as a bit of a foil to those who wish they had a more technical CTO/CEO in their organisation. Does anybody else have a similar experience or is this situation an absolute one of a kind?

Last week me and my friend have been changed from a legacy PHP project to new Ruby on Rails-based setup. What, in first instance, looked like a great improvement, now becomes a nightmare.

All this convention-over-configuration is awesome - but only if you already know the conventions, or if somebody told'em to you.

And everything is going even more out of control because the damn project is based upon Spree gem and several other extensions, that MUST be changed to meet out company needs.

I'm getting really mad with all this pressure. Ruby seems to be a great language, but I'd rather be working with Laravel. Its overall organization, the centralization of CLI commands in artisan, and the astoundingly clear, eloquent, direct and well-designed documentation made my adoption curve there a little more pleasant.

I mean, legacy PHP systems are awful, but Laravel framework sounds way more easy-to-learn and well-constructed when compared to rails.

But given all this nightmare, I really want to be proved the opposite.

New day, new rant, same shit.

So basically, if you are following my rants you already know I'm working with a crappy framework forgotten by God and you should even be aware my manager is not an IT expert.

So anyway, we have this requirement to implement: a step-by-step process.

They asked us to make the UI design.

My big ass manager couldn't hold his expertise so basically he told us he would make the UI design.
He is a self-entitled UX designer, just saying.
I still don't know who he is, why he is there and why he is doing all this damage. (I only know he is a friend's ceo )

Today I got his UI mockup. It's a fucking nightmare. xD I mean, you would shoot yourself in the foot. If I was the customer I'd just leave the page. You may ask yourself: "How bad a UX process can be designed?" Well, a lot.

The interaction on the page is a clusterfuck.

I'd give you an example but it's so complex to describe I'm just leaving this rant as it this.

I'm implementing this... I'd like to say sorry to all our customers, it's not the devs fault.

Googling for Angular (>=2) documentation and finding AngularJS instead feels like cancer.

If Google was going to "update" to what is functionally a new framework, they should've named it differently instead of trying to piggyback on the popularity of AngularJS. Sure, there's similarities, but let's be realistic here.

Admitting a few things: I found myself ranting multiple times about multiple programming languages and how it's their fault things didn't go my way, I'd like to take the time to admit that I was wrong, not understanding the language was because of my lack of experience with it and patience to understand. So here's my two cents : if you're ranting about a programming language/ framework being bad, you're probably inexperienced and don't know how to use it right. I was retarded for blaming languages such as php and using typescript as being bad even though I was clearly inexperienced with them, sometimes I see a bunch of retards bashing great languages and libraries such as bootstrap, bitch if you can't manage to understand how to copy paste some css classes then you will probably never be able to write css and should consider working as truck driver. It's been a month now in my new company and my skill level has increased exponentially, we are almost ready to launch our app and I have in someway become super excited about learning new tech.

Hello guys. A newbie to the app. I would like to ask - start a conversation with you about adopting new technologies, if should we follow or just wait? I am a PHP developer. I would set myself around mid to senior level. Since I graduated and I start working on a Marketing/Development Company, I have been develop a lot of websites, platforms with pure PHP, JavaScript, SQL. Later I start using framework like laravel. Now I am thinking about JS frameworks such as node, vue, react, angular and maybe later noSQL. The problem is that there are many new technologies that companies required when you apply. I want to learn new technologies but I don't know if that would be helpful than focus on LAMP and get better and better to that. Many orgs have implemented their own technologies and each company is getting mad to it. You see each company adapt these new technologies even if they don't want em or projects required it. So my question is: are we talking about dramatically speed and light use to server when we use new frameworks like these, previous mentione + etc? Or companies are just trying to look cool by mentioning many techologies while projects could never ask for em? (Nothing serious, I am just trying to make conversation and clear my thoughts by getting others opinion)

procrastinative coding is a bad habit of mine. I've been using php for 10+ years and just recently got into laravel. I have to say I love it but at times I wish I could have learned the entire framework before starting my project some time ago. as I am coding I learn new tricks with laravel on how to do things and have to waste time and go back and change existing code... or tell myself "I'll come back to this after the launch".
I'm just wondering how other people handle taking on new frameworks

I’m new to coding. I decided to pick JavaScript to learn how to code. For a while I was confused as I couldn’t grasp the fact that jQuery wasn’t a language of its own even though multiple people on devRant told me it wasn’t (or was?)
Anyway thanks for baring with me. I’ve decided to drop jQuery. It seems kind of outdated even though a new version of the library was added quite recently.
I’m now delving into ReactJs. Some people say it’s a framework, others say it isn’t. Again one of those confusing debates which is beyond me. Anyways I’m amazed at how easily I can get a basic web page up and running with React. So far I’ve only managed to launch an application using the create-react-app command in the command box. Oh and I’ve also been able to add a button to the html with a counter increment.
Fun times ahead!

How the hell am I meant to get a new job in Edinburgh/Glasgow so I can learn React/Angular/Vue when no-one will hire someone without experience in those frameworks?!

I was in 2 roles back to back and in that time, every single Front End Development role now available in the market requires commercial experience in React/Angular/Vue in order to proceed.

Even the 18k Grad/Junior Development roles require commercial experience in some sort of JS Framework yet I'm certainly not a Grad/Junior.

HOW DOES ANYONE USE IT COMMERCIALLY IF THEY'VE GOT NO EXPERIENCE.

I'm doomed.

For the record, I'm a Front End Developer with 3 Years of experience with personal study experience in React.

Starting a new job on Thursday after 2 years as software engineer at a different company. I feel like a know no transferable (language) skills; I was mostly "the expert" of the framework at the previous company and now feel like I'm starting from scratch.
How do you handle starting a new position? Do you prepare yourself or just go and see? Am I overthinking?

JEZUZ CHRIST FOR GODS SAKE MOFO FRAMEWORK DEVELOPERS ... if you've built an awesome framework once, you have ONLY ONE JOB: maintain it - keep it up to date with fucking browser changes and fix security holes. Changing the core concepts every major is not part of this. If you got visions, start a new one ffs, become a mofo prophet one OR BURN IN HELL POWERED BY THE REMAINS OF YOUR ANCESTORS FFS!

I'm trying to convert a legacy .NET Framework web api to .NET Core, the project and its supporting libraries are in awful conditions and to make things worse at a certain point someone has the genius idea of introducing Uncle Bob's "Clean" Architecture into a part of it so stuff which could simply look like this

public string doStuff(string input){
// Do the stuff
return output;
}

becomes a convoluted mess like this

public class StuffDoerRequest {
public string Input{get;set;}
}

public class StuffDoerResponse {
public string Output{get;set;}
}

public interface IStuffDoer {
public StuffDoerResponse Execute(StuffDoerRequest request);
}

public class StuffDoer {
public StuffDoerResponse Execute(StuffDoerRequest request) {
// Do the stuff
return new StuffDoerResponse() {
Output = actualFuckingOutput;
}
}
}

Edit: sorry for the lack of indentation, apparently DevRant trims leading whitespace

You know what i really like about right now? That is not like in 2016 when a new Javascript framework was release every day that does the same as jQuery but different, now days i can use it and everybody says "nice" instead of "you should do this with X.js with 4000 libraries on ES^N edition" to quote an articule i read on the time "I need to display data on a page, not perform Sub Zero’s original MK fatality."

I've been using dotnet and aspnetcore for years. I've heard people complain about MVC but I never really saw the problem. The controllers are easy to set up for basic endpoints, I have my domain models and DTOs, and our views I guess is our standalone webpage just consuming jsons.

Only now I'm having to work with an *actual* aspnet MVC stack - server-rendered cshtml and all - and it's dawning on me like a truck what people were actually referring to.

Out of all the issues I've had so far, they have all been due to black box enigmatic voodoo because don't worry about it, the framework takes care of it - it should just work. But what if it doesn't? I have no idea because the trail ends at the bit that should just work.

I should know better than to criticize an entire framework and paradigm made by devs with vastly superior experience and expertise than me, and my issues are absolutely due to being new and unfamiliar with this, but imagine coming up with an architecture to obsessively separate the MVC concerns, then you make cshtml.

It wasn't really the project itself, but more the execution of it

Last semester we were tasked with writing a new programming language from scratch. We were a team of six people, everything went great to begin with. We discussed language features, the framework runtime it should run on and even what language to write it in.

Fast forward two weeks, nobody is doing anything but me, the two dudes tasked with helping me were both no-shows and the others were busy documenting the syntax and semantics of the language.

I basically ended up having to write the whole language myself with no breaks no help and no guidance.

A few weeks before deadline I completely burned out and couldn't do anything other than just sit and stare at the code; mentally exhausted and not in a mood to do anything other than doing mindless unrelated tasks. But alas work had to get done.

And it did get done... Sorta.
Our beautiful statically typed, statically scoped concurrent programming language that was supposed to compile to BEAM code was neither statically typed, statically scoped, and the output ended up being half-working elixir code that only worked on the most specific of cases.

I don't want to work with those guys again.

When you are trying to get through "Get started" section of a new framework/lib but get so many ideas that suddenly you find yourself creating 5 applications at a time without any idea what the fuck are you doing.

I’m sooo excited when any new frontend JS framework is available. Angular, React, more recently Vue, Svelte. Bring ‘em on. I wanna try them all.

Just kidding…
As long as the tools at hand allow me to get the job done, keep clients and end users happy, I don’t give a fuck.
This meme is actually the epitome of what I hate with a lot of web developers I’ve encountered

Finding an awesome new library / framework then finding the documentation is all "this is what it is" rather than "this is how you use it" *sigh*

My ideal dev job, would be a job I can show compassion towards. A team I can be proud of and learn from. And a vibrant workspace with likeminded individuals who just want to improve themselves even if they feel their at their pinnacle.

My current office tries to make use of new technologies, we've embedded docker, vagrant, a few ci systems on an in need basis per team, and a lot of other tools.

My only real qualms are they feel indifferent towards new languages and eco systems ( Node.js, GoLang, etc ). Our web team is still using angular.js 1.x, bower, refuses to look into webpack or a new framework for our front end which is currently being bogged down by angulars dirty checking.

Our automated quality assurance team is forced to use Python for end to end testing, I've written an extensive package to make their lives easier including an entire JavaScript interface for dispatching events and properly interacting with custom DOMs outside of the scope of the official selenium bindings.

Our RESTful services are all using flask and Python, which become increasingly slow with our increase in services. I've pushed for the use of Node or GoLang with a GraphQL interface but I'm shot down consistently by our principle engineers who believe everything and anything must be written in Python.

I could go on, but tldr; I'm 21 and I have a ton of aspirations for web development. I'd like to believe I'm well rounded for my age, especially without any formal education. I'd love to be surrounded by individuals who want the same, to learn and architect the greatest platforms and services possible.

MaterialUI? Is it shit?

A brand new code base. Old codebase (old employees) used MaterialUI, locking in a lot of the styling and layout in their grids.

I'm trying to identify the pros/cons that can come from experience using the framework.

Some questions to spark discussion:

Anyone used this in production for a period of time?

Did it hold up? Did the designers hate it?

How was mixing this with SASS etc.

Cheers

Dev: Now that I finally know PHP and JS it must be really easy to find a good framework and use to build my beautiful website.

The options are limited: AngularJS, ReactJS, Ember, ActivateJS, BackboneJS, ExpressJS, Laravel, RactiveJS, Node.JS, Meteor, Knockout, Symphony, Codeignitor

And yes, you thought if you don't like AngularJS you can easily switch to ReactJS. But guess what, every framework will use their own scripting languages like Jade, Blade, Typescript making it learning something new extremely smooth.

The documentation will be part of another rant

I always thought wordpress was ok, not great not terrible, from a coding perspective. Now every new framework I have worked on makes me see why Wordpress is on 40% of the internet.

Now I love wordpress not because of what it did do, but because of all the really stupid things it managed to avoid doing including: over abstraction, trend chasing, using "new transformative technology" that disappears in 2 years, breaking plugin economy with updates and making devs start over, making everything OOP for the sake of making everything OOP, making adding on a bit of code take multiple files of multiple formats and boiler plate code, boiler plate code, compiling dependencies, composer, twig, laravel, one page applications, react, angular, vue, javascript only stacks (MEAN), not letting you control sql queries, protected/private scopes and design that doesn't let you fix or alter bad code others did, and the list goes on and on.

Wordpress did a lot right, and devs should try learning from it instead of making more problems to solve. Sure it's not elegant, but you known what it does do? Focus on a solving a problem. Then it does. Without inventing new ideas or concepts to inject into the code and create new problems.

And you know what else? Hooks are actually very well implemented in Wordpress. I've seen it done much worse.

Honestly my main gripe with the entire platform is a slow moving to OOP for no reason and the database design should separate post type into different tables, the current design makes it less scalable for large data sets for multiple reasons so I'd fix that.

Question for you desktop guys. I was thinking of making a desktop app with a GUI as a side project. It's mostly going to be business-like CRUD, no fancy stuff. I was thinking of using electron (since I'm a web developer) but I read that it's slow and bloated. On the other hand I would like learning something new. I don't want to spend too much time on the GUI so I would prefer a framework/language that already has some nice open source gui packs available. I have only ever used JavaFX before for a tutorial, is that a good choice? Also, I would like it to work on both linux and windows.