Not sure if can be considered a software essay, but a goldmine (imho) is Patrick McKenzie's - Don't Call Yourself A Programmer, And Other Career Advice:
I'd reckon they would have audits in place to trace who accidentally made this post?
Either way, just for the fun of things, post your (fun and wildest) guesses on how this probably happened below...
My take is someone about to post a news article, left the view and their pet (thinking a cat) ran through their keyboard and posted the article. And since the cat has gained awareness, they were able to move the article from draft to an actual post. =)
Is it a fair point to say that the meaning of love here could be interpreted in so many ways, depending on whose vantage point you are viewing it from.
One could certainly love (or like) a corporation if that company provides some meaningful semblance to one's life.
For example, if you are that company's employee and you have been well-provided with means to live a comfortable life while also being aligned with your values, I can't even think how you will have an ounce of contempt for that organization.
If the company provides you with products or services that enhances your way of living, then definitely there would be room for adoring them due to the positive impact that they have.
In the case of the OPs example, the company will be enforcing actions that have different repercussions depending on where you are on the side of the fence.
If you are from the outside where you publish products or services that needs to live within the company's digital ecosystem, then surely that additional tax is an impact that will hurt your finances overall. Anything that hurt your finances will a chain effect that can hurt your business, your decision making, and to some degree, your well being.
Its different when you are within the walls of that company. That additional margin would likely translate to increase compensation (if you are an employee) or better profit (if you are an investor).
The thing here is that, loving or liking or adoring a company hinges on how it impacts your personal bottom line. At the end of the day, the rationality of the decision is based on what each entity perceives as what is best for them. What's best for someone may not be the best for everyone. And that's reality.
It's just reality that (most) companies with no transparent in their compensation, existing employees will be put on the salary bracket that will give the company the most leverage - either by being able to dangle a good counter offer (whenever the employee is about to transfer to a different company) or simply saving on salary expense.
Corporations will always mark an employee simply as an entry on their ledger. When the time comes to get new hires on similar work level, they know they need to up their game in terms of how much they can generously pay while still maintaining the bottom line of the organization.
Many people tend to gain a good understanding of React by building on top of it. Unfortunately, majority of the tutorials, lessons, recommendations, and paid courses usually start off using a framework where a lot of stuff have already been added. The effort to simply understand a complex setup as compared to starting React with the bare minimum and slowly adding whatever packages / libraries are needed.
React should start by a simple initialization:
-> Setup React
-> CSS library
-> State management
And then, other packages or libraries can be considered to be added whenever the current needs of the application exceeds what the bare minimum setup has provided.
While in the end the set of packages and configurations performed may tantamount to what a framework already provides easily, the cognitive load starts on a piece that is well understood and grows alongside the evolution of the software product being delivered.
I initially thought that no modification that will impact the amount of fuel was performed on the machine. That in itself will be an amazing feat.
This can be considered great if they made advancements in engine / combustion design that increased the distance traveled on a per liter (or gallon) of fuel.
Given that it is Glassdoor's interest to provide employers with pretty much the power to veto negative reviews, then the data points in terms of satisfaction will greatly be skewed favorably to the companies.
While we can acknowledge that a lot of negative reviews will also stem from employees who were terminated / laid off / dismissed as the company may be undergoing financial / economic challenges, there can also be a lot of valid ones.
But then again, each individual (who will do a review) knows the adage to _never burn the bridges_, hence, either they use Glassdoor as a venting platform, or have the courage to stand up and speak their minds.
Unless there's a net benefit upside to the individual providing a negative (albeit constructive) criticism, it'll really be hard to weed out what's really helpful from what is written out of anger and desperation.
Lots of $$$ poured into consultants and very little to the folks who actually do the work and implementation.
And of course, a project (or program in corporate speak) of this magnitude will have a lot of meetings involving a lot of people that usually ends up in very meaningless decisions.
At times, I still fall for buzzwords in the technology space.
Looks shiny and most of the very vocal devs are harping about it - maybe worth a try.
At the end of the day, in the absence of buzzwords and hype, I sit back and come to the conclusion that tried and tested technology will still be able to do the work 99.9999% of the time.
I hold the .00001% for those possibilities where you are doing something breakthrough that in itself merits to be associated as a buzzword.
Until then, always proceed with caution and rationalize whether it is only hype or it is something worth adding to your arsenal.
I don't quite understand the logic where people being laid off from their positions / responsibilities and the jobs being posted are similar in nature.
For one, are you really saving costs when you're losing some individuals with deep knowledge of the job for which you would need to re-train a new individual to come up to the same speed and productivity as with the previous person doing the job?
Doesn't this also make productive / talented / hardworking people shy away from your job posting when they know that your company recently laid off employees?
> "service abuse reports seem to make no difference"
Microsoft email services are being used to create these spam accounts as they are much more easier to setup and get running. And if a spammer is using a Windows based OS, setting up multiple mail accounts using the Mail app is almost a breeze (including managing those multiple email accounts).
Every solution/alternative would always impose challenges that can be considered an edge case initially until it becomes permanent.
For example, if Google wants people (who have a tendency to lose their 2FA devices more often) to always use this feature, and in case they lose access to their device, they could use a trusted designate who can verify on their behalf that they are the ones signing into the service. But then again, this alternative will impose some new challenges such as:
- What if the designate is not available?
- Designate is available but also lost their access to verify the other person?
As with this case being raised here, it will always be a process wherein Google (or any other organization) will have to explore and find meaningful solutions that is both inclusive and considerate on specific conditions.
The variability alone of such premise is huge that I am quite sure when the next edge case comes up, there are other edge cases boiling down that will become the next set of issues.
I think the reality that there's little (to none at all) job posting which would only require application development in vanilla CSS/JS/HTML is the main reason why frameworks dominate the land.
While I see the value of using vanilla stuff, the complexity of software requirements, ever evolving browser APIs and features and increasing ease of using libraries (i.e. date-fns, lodash, etc.) has definitely increased the appeal of frameworks.
My SAP experience in a nutshell (working for two large organization who has deeply entrenched SAP software)
1. It is extremely challenging to integrate with. Your basic option is to overhaul your existing software to at least match the available integration options.
2. It requires constant care. SAP Expert Consultants hired by the companies initially for two years, which was supposed to be the timeline when SAP would have been fully adopted (and turned over), still works as the complexity and evolution of updating the software itself is tantamount to a new system adoption.
3. Users (Majority I would say) hate it. The only reason they live up with it is because someone higher up the decision and authority chain imposed the software after being sold to the premise that it is a game changer to the organization.
With the transfer of the crown to King (Prince) Charles, is there an explainer article that provides a comprehensive information on who is deemed the next in line in multiple scenarios (i.e. assume next in line dies, the heir/heiress are incapable, challenging someone's ascension to the throne, etc).
This would make for a good read and understanding of how the royalty works.
On the topic, I think what Queen Elizabeth has done despite of the challenges within her sovereignty is being a living example on how to rule and govern, without negatively interfering with how the affairs and progress of the state needs to be carried out.
1. Was this sponsored by DJI, which they could potentially use for any of their promotional / advertising efforts?
2. Is there a raw version? I would think that there should be more shakiness or variability in the captured footage, given the high altitude and assumption that the air flow would easily disrupt the flight of the drone.
3. What period of the year was this taken? Usually you'd hear that Mt. Everest is always packed with mountaineers, and being able to get a shot with very few people on the mountain slopes is quite uncommon.
Side note: This is a spectacular feat - man and machine.
I have the MSI Prestige 15 and it has been very reliable and a pleasure to work with.
I've had a Lenovo initially, but had all these problems with the web camera. It was a decent computer, but the camera is quite essential in this age of remote / hybrid work arrangements.
https://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-pr...