@Demolishun it will slowly die off though, there are a million different JavaScript frameworks that probably package it along the way.

Personally for load times I don't really look at that unless absolutely necessary. I would rather have readable and maintainable code than a bunch of gibberish in Vanilla JS doing the exact same work.

@retoor there are still use cases and frameworks that come with jQuery. If you need to do any DOM traversal it's a lot clearer in jQuery than native JS.

@Wisecrack I don't get are blog sites that ask to send notifications.

You can mute conversations, set do not disturb, even turn off notification sounds.

I don't know what the issue with Teams is. It's probably the most versatile "one stop shop" application to communicate with coworkers.

Where I work we had to update a database. Would've been easy, except that for some reason they made a description field, the PK for a table....

@Lensflare emotional intelligence is useful for when you need to manage teams of individuals properly. There are some leaders that absolutely suck at that and can't manage or interact very well at all.

@Sid2006 I get to deal with this every 2 days. I swear managers should be proficient in "active listening" before they become a manager.

Next time this happens, make sure to document all interactions you have with a group and keep it in a safe place and only pull it out when you need to CYA. Sucks that people are like that, but you'll learn early how to deal with office politics

@joewilliams007 work reasons. Tech support would have a damn meltdown dealing with basic Linux issues and teaching people compared to Windows.

At the end of the day, it's about the cost of supporting such feature which is why it gets removed unless it's a feature that basically doesn't need to be changed in the future at all, like 10+ years in the future the feature will still be doing its job.

Also, if not enough people are actively using the feature it basically becomes technical debt that only snowballs out of control as the project changes.

So at the end of the day you can either A) spend money on maintaining features not being and increase technical debt or B) reducing the amount of money needed to maintain useless features and reduce technical debt by removing it.

Personally I'd go with option B, specifically to keep technical debt down as unchecked tech debt is just asking for hell when layoffs, retirements or days when your short staffed begin to happen.

Every BIOS update I've done with bitlocker enabled has forced it to be turned off with a message of making sure you have the recovery key on hand or know the pin.

@AlgoRythm AFAIK I think it was mentioned somewhere that the code to run the feature was already implemented into the source code for like the past 6 months. Obviously it got leaked and everyone pointed out the major flaw in it and painted it as a non-technical executive's idea (because they apparently have the best ideas, ofc).

Honestly I could understand deleting the repos if they went by account logging in, rather than activity on the repo itself.

Deleting repos means that you consider that some projects are never "done" or are stable in the sense they aren't going to add more crap in that they don't need. Sure there might be dependency upgrades needed, but let's consider the repo doesn't have any dependencies to it, it still wouldn't need to be updated for a long time.

Honestly it depends on framework and codebase. I know SailsJS provides two methods intercept() and tolerate() so you can chain error handling onto an async/await call rather than wrap everything in a try catch block.

Just because a developer isn't using try/catch explicitly doesn't mean that they are not handling errors at all.

Or for your neighbor to decide that now would be a great time to mow their yard.

Why on earth haven't you updated Node? My place would throw a hissy fit for something that old and out of date.

And by hissy fit, I mean straight up blocking it from accessing the network.

I can totally understand the reason, you assume that the data being sent to the API is invalid in some form so you verify it again on the server.

You have to assume that your user doesn't understand most file types or what they mean, so depending on the user to get the right file type is not a good thing. Otherwise your just creating a classic garbage in, garbage out scenario.

For example, have a non-technical person explain the difference between .doc and .docx file types.

I'll allow 1 liner arrow functions if they are simple and easy operations.

@tosensei then there are the questions where it was an improper closing of a HTML tag which affects the styling of said spot on a webpage so the answers given are brute force the styling in CSS because nobody thought that the markup was wrong.

Copying code is fine assuming the proper license is used. But also make sure you understand what it is doing as well, and don't forget to adjust it to the use case you have.

A lot of times I see developers just straight up copy and paste code from stackoverflow with zero changes to their use case or variables changed.

@Oktokolo I'm a person of cultural, I don't use semicolons in Python but use 4 spaces instead of a tab.

@jiraTicket I don't mind incomplete feedback at all, it's better than sitting around twiddling thumbs waiting for the full list to come through.

I hate being told "Implement X" and then a week later a meeting occurred that I wasn't aware of and "Feature X" is now shelved but I'm not updated until either I ask or a meeting occurs where I'm involved.

Ah the good ole, drop it on you at the last minute BS. Been there done that way too many fucking times to count.

Oh you need this decision made within 3 weeks due to it being time-sensitive? We will have our decision made in 4 weeks.

@fullstackchris That sounds more like an HR problem than anything else.

@Tonnoman the dude straight up didn't know how JS worked, let alone HTML and CSS, or even proper relational modeling to make it somewhat easy to do simple items.

When I first took over the project it looked to be about 80-85% completed. Which it was, but it was so poorly written that 95%+ of what was completed had to be completely rewritten.

@donuts I think it's simple for a combo box, assuming that you need to do simple changes anything overly complex and you lose all the default aero look or whatever the current style default is for its generic look.

As much as CSS can be a pain in web development at least it doesn't randomly decide oh you did something wrong? Here let me revert your input field to the default browser look....

I mean it shows that they are looking for edge cases that might come up.

If you don't have your production checklist or steps documented anywhere and are gate keeping it by mental memory only, expect bottlenecks to arise. Granted I would still put a permissions check in place so only experienced people can do it if there isn't a dedicated team to do it and it can be toggled when needed.

A lot of fresh juniors probably have little to no experience with deployment of apps. Hell even my own alma matter has Databases as an elective and not a requirement to graduate still, but formal languages and automata is required to graduate.

@IntrusionCM They work on the team responsible for the mess that is Microsoft Excel....

If the industry is saturated it's only saturated by incompetent developers who don't know what they're doing and force people after them to rewrite entire projects so that its actually maintainable and money chasers....and both groups overlap each other.

@sariel It's even better when the client is the one who wrote the requirements or if your dealing with statistics programs the calculation instructions....