That's impossible to determine because the units don't match.
Your market worth is your labor and skill, almost totally separate for how much you pay your robots. Low margin x high scale is as good as high margin x low scale. High margin at high scale doesn't exist outside a monopoly.
Like everyone else, scientists are so convinced of what they know that they won't listen to other opinions.
The problem is that scientists think their knowledge is truth because it comes from "the scientific method." They fail to internalize that the whole point of that method is that no knowledge is sacred and everything should be doubted to the degree at which evidence exists to the contrary.
A crackpot conspiracy theory with a single anecdotal source of data is sufficient to create doubt in the soundest of theories. Just not much.
When someone who refers to their monitor as "the CPU", and can't tell the difference between a programming language and an operating system, starts telling you how you should be doing your job because you've got it all wrong...
How much do you listen to their opinion?
(Unless of course that matches your manager to a T).
You smile and say, "I appreciate your input. I value it and consider it a good starting point. I am not certain it alone provides the level of support necessary for me to consider a different path, but I would consider both additional data and reducing the amount of evidence I require with a good reason."
I appreciate your input. I value it and consider it a good starting point. I am not certain it alone provides the level of support necessary for me to consider a different path, but I would consider both additional data and reducing the amount of evidence I require with a good reason.
I've started telling new grads / interns that ask me "how 2 get jerb" to cut their resume to 1/3 of a page. Because we still need interns and juniors, and we already know they don't know a damn thing, and the only thing that would stand out at this point is _not_ making me read half a page about your capstone.
We have all the titles we need. We have junior for "that guy who can't do a fuckin' thing unless you tell him exactly what to type." We have senior for "that guy who can take a ticket and implement it." We have lead for "that guy who can take a business idea and implement it."
That should just be the title without prefix really, a Senior Developer should be providing more value than just ticket implementation.
These are just my opinions though, it differs from company to company. One place the difference between a Developer and a Senior Developer was a senior could be expected to own a feature and all the moving parts to get it deployed, eg: taking it to the board, organising all the approvals and business requirements with other teams etc. Other places senior just means "not junior" and the roles are the same, you just expect more talent from the senior.
I spent about three months consulting for some crypto company as a distributed systems engineer.
They paid me to design an eventually consistent, self-healing data store with a cache layer / write ahead log, with peers determined by paxos consensus, transfers metered by finops and govered with kademlia, and a storage layer capable of byzantine fault tolerance, which we implemented via signature chains.
See, they had this crazy idea that they'd make a cryptocurrency that they could sell to western digital, who could offer hard drives that "filled themselves up" with other people's data when idle. WD would obv make a buck and maybe sell these drives for much cheaper than the component cost. I'm not exactly sure of the economics. I think the idea was to have half the drives be "receivers" and half be "senders" and actually sell the "senders" for way more than component cost, but provide trivial effort file backup.
I think they're still building it. I dunno if it'll be a scam or not. I had fun though.
Given how much OCD I have about naming variables and writing unit tests, I think if this was in front of my house, I'd take a sledgehammer to it. Fences shall be straight, damnit.
When I want "this will run forever," I write it in Rust.
When I want "this will compile forever," I write it in ANSI C.
When I want "this will live forever," I write it Python 2.7 and make it the backbone of the entire org's infra templating. Bonus points if it's a custom Ansible module.
