Yes. The recruiters who troll LinkedIn must just search for one specific skill and spam everyone who has it. I always get offers for jobs I'm either not qualified for or would never willingly do.
Last year I realized that I'd never changed my LinkedIn job profile info to "not interested" after starting my new job a year earlier. I'd been getting a lot of pings from recruiters, and I thought that might discourage them. Nope. Saying I wasn't interested made the recruiters even more interested in me!
Which would be great if any of them had a job better than my current one, but they never do. Everything is more boring work I'm less qualified for, for less pay.
Our local Rotary Club gives free dictionaries to all the 3rd graders every year. I checked, but it's not the OED Junior, it's a special edition "Dictionary & Gazetteer" compiled by The Dictionary Project (https://www.dictionaryproject.org/).
I think we're going to see a lot of disruption in enterprise software. A lot of companies are currently resting on past success, counting on the fact that it's really hard for companies to completely replace critical business software.
At the same time, innovations in development frameworks, team management, and a better understanding of UX are allowing upstarts to create better enterprise applications.
I'm guessing Salesforce might not be around 10 years from now.
Even the government is culpable. The national lab where I live has frozen wages so many times that the PhD's working there are on the bottom end of the pay scale for people with their degrees.
Mind you, I have to wonder where those people on the top end are. Really, who *is* hiring PhD chemists and physicists and paying them so well?
I recently updated my LinkedIn settings to say "don't contact me about job opportunities." I like my current job and don't expect to find a better deal anywhere else (decent salary, great coworkers, WFH).
As soon as I put up the "don't contact me" marker, the number of pings I get from recruiters doubled. Still offering the same depressing-sounding jobs with long commutes. I guess saying you're not interested piques their interest.
Don't get caught unaware by the next major CME. Read the space weather forecast from NOAA.
I was thinking it sounded like whuffie.
Mt. Fuji is more well known, but I wonder how all this seismic activity is affecting Mt. Miyajima in the southern part of Japan? It's another active volcano, one I visited in the 90's. It was actively smoking at the time, and surrounded by lava beds.
There are many arguments against adding the IDE, but I don't agree with this one. People said the same thing when Google came out with Gmail. "We've already got hotmail and yahoo and a million other free email services. Why do we need another?" If this tool is good enough or simple enough to use that it becomes ubiquitous, then it doesn't matter what's already out there.
I got one several months ago because I wanted to try building apps for it. If you absolutely have to play around with the bleeding edge of technology, if you are willing to spend that kind of money on a device so that you can be the one who invents what it's used for, then go for it. Otherwise, it's not worth it.
Time to start working on the darknet in earnest.
I worked on a project this year to completely rewrite a company's signature application from the ground up. Objectively, you'd think that's something you never, ever want to have to do. But, having done it, I think planning a complete overhaul & rewrite into the product's lifecycle is probably a good idea.
Since the application was first written about a decade ago many, many features have been added with each upgrade. The scope and customer base have expanded. And programming technology has changed hugely during that time.
Rewriting the entire application is a massive effort, sure. But to truly modernize and streamline it, to get rid of the legacy cruft and take advantage of new tools that didn't exist 10 years ago, I think it's worth it. I also think it would've been wise to do this sooner than we did (though that wasn't possible in this case for business reasons).
So maybe when you're choosing a framework, don't worry about whether it'll be the right solution forever. Plan to reevaluate your decision every 3-5 years and change frameworks if something better comes along. And, yes, absolutely adopt the MVC model, because then you don't need to replace every part of your application if one becomes obsolete.
A giant wall of ice? Where have I seen that before?
I made the mistake of eating a hamburger in London in 2001. I was on a long business trip and just wanted something quick to eat, so I ducked into a McDonalds.
Little did I know that, thanks to the outbreak of Mad Cow Disease, this simple act would make me ineligible to become a blood donor for years to come.