|
ad infinitum...
I suspect one could find a study that confirms just about any hypothesis you might want to propose.
|
|
|
|
|
Work on the AV1 (AOMedia Video 1) codec started in 2015, when Google, Cisco, and Mozilla+Xiph.org pooled together three codecs —VPX, Thor, and Daala— into a new project that aimed to create a royalty-free codec that they planned to make freely available to anyone on the video market. Just in time to kill the radio star
|
|
|
|
|
A team of academics has successfully developed and tested malware that can exfiltrate data from air-gapped computers via power lines. The team —from the Ben-Gurion University of the Negev in Israel— named their data exfiltration technique PowerHammer. Beware of hackers with volt meters
Of course, the first step is, "install malware"
|
|
|
|
|
This isn’t a job title you should accept, unless you have your back against the wall For discussion purposes
|
|
|
|
|
Having worked my way up through working in a shop selling plastic gifts to working as a warehouse worker shifting lorry loads of heavy boxes I am still amazed at how some people think that their first or even second job should be well paid or even interesting.
Having a PhD in AI from Stanford does not mean that you are competent at working in a business with all that it involves - therefore your first job should be as a junior role as you still have a lot to learn in your first 10 years of employment.
Rant over... for the moment...
...well not quite over...
Learning can be summarised in four stages:
Unconscious incompetence
Conscious incompetence
Conscious competence
Unconscious competence
The chap who wrote the article seems to still be at the Unconscious incompetence stage 
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
modified 12-Apr-18 8:24am.
|
|
|
|
|
The owner of the company had an objection at the time that infuriated me. He worried that giving them good job titles would make it easier for them to work elsewhere and wondered if we shouldn’t sandbag them a little. Make them “coders” instead of “software engineers” or throw in a “junior” at the lowest level.
I subscribe to Richard Branson’s wisdom related to this matter (which I think post-dated the conversation anyway). “Train people well enough so they can leave, treat them well enough so they don’t want to.” You keep people by partnering with them and making them feel valued, not by sandbagging them.
[...] The job title, in spite of being a construct whose value I fundamentally question, is sociologically fascinating for an armchair dilettante like myself. Within a company, job titles mostly matter procedurally. [...] But then, when you go to interview somewhere else, they suddenly matter in a very economically tangible way. The loose title consensus across the broad spectrum of companies (and, quite often, the question “how much did you make at your last job”) is how your new company places you in its pecking order.
|
|
|
|
|
My experience has been that current or previous job titles have had absolutely no effect on my ability to get a job.
The two things that have made a difference were skills and current salary.
For some strange reason many employers seem to believe that the more you earn the more competent you must be.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
GuyThiebaut wrote: For some strange reason many employers seem to believe that the more you earn the more competent you must be.
Which is part of the problem. Let's say you accept a position as a "Junior Dev" with a bracket of 40-60k/yr starting at 45k/yr. You kill it and get a raise to 50k/yr. You earn more and more complex work over a couple years and continue killing it. But HR can't promote you. There are no positions. And the company doesn't want to give you a raise because it would shift you out-of-line with other "Junior Devs" on the team - even if the bracket still allows a 10k furtherance.
So you see yourself going nowhere and jump ship. Apply to a bunch of places; maybe some don't give you any attention because of your title; maybe some do. Let's focus on the ones that do. So they see your title as "Junior Dev" and see that you made 50k/yr. Let's say the position is a normal "Software Dev" position with a 55-85k bracket. What do you think they're gonna offer you?
Your previous position was not reflective in title or compensation to the work you ended up doing. But that same title and compensation data will be used to determine how "important" you were relative to the general baseline pay. Something that isn't consistent at all between companies. This could easily backfire into a 55-60k offer even though the value they might get is more in line with 70-75k.
HR doesn't know who you are. They don't look at your GitHub projects. You're just a group of statistics on a piece of paper. If you aren't mindful of how those statistics reflect on you, it could easily stunt career growth. Because as you said,
GuyThiebaut wrote: For some strange reason many employers seem to believe that the more you earn the more competent you must be.
I'm not saying this is always the case. It probably also differs from country to country and market to market. The point is that just because it might not have occurred to you currently does not make it any less of a topic worth considering for the future.
|
|
|
|
|
Yet, titles do mean something. I once worked with someone who was a "software engineer", but had the experience of a junior engineer. He got a job offer elsewhere. To match it, the company policies required that he be made a senior engineer. They did so. But, he still wasn't a senior engineer and it caused all sorts of real problems.
If I see a resume of someone with three years experience claiming to be a senior engineer, I suggest not even bringing them in, let alone giving them an offer. This isn't me being snooty about titles, but long experience of people claiming they are far more competent than they really are.
|
|
|
|
|
I wasn't claiming titles don't mean anything; exactly the opposite in fact. My point is titles are just as important for the employee as they are for the employer. It's definitely a complex issue. Both from an employer and employee perspective.
Your example points out a pet peeve of mine in company-culture - the idea that upward-mobility is inviolable. Not everyone has a position appropriate to their skills. I don't care if you've got 30 years of experience and are a senior developer. If you've refused to learn anything since C and your code is unmanageable like throwing spaghetti into a ceiling fan, maybe you've earned a bit of downward-mobility.
|
|
|
|
|
Unions have been trying to organize software engineers for decades, with little success. Here's a look at the organizing campaign that might turn things around. "Look for.. the union label..."
Also: worst D&D ripoff, evah!
|
|
|
|
|
Researchers have developed a method for generating numbers guaranteed to be random, through the use of quantum mechanics. The experimental technique surpasses all previous methods for ensuring the unpredictability of its random numbers and may enhance security and trust in cryptographic systems. D20 ought to be enough for everyone
|
|
|
|
|
It won’t lick your face, but a new artificial-intelligence system mimics canine behavior to make dog-like decisions. Other animals could be next. Who's a good AI? Who is? You is a good AI! Yes, you is!
|
|
|
|
|
Companies can't prevent you from getting your device fixed by a third party. What about those 'Unlawful to remove' labels on the pillows?
|
|
|
|
|
We all know that AI can be used to swap faces in photos and videos. People have, of course, taken advantage of this tool for some disturbing uses. How to stop an AI from taking over the world? Another AI!
|
|
|
|
|
You're correct. That way one AI will have only half of the world. So the condition of AI taking over the world is successfully averted. Therefore let me just say: I, for one, welcome our two new AI overlords and offer them my services of maintaining some unimportant offline code bases in some forgotten hell hole. Will work for food and survival. 
In order to understand stack overflow, you must first understand stack overflow.
|
|
|
|
|
Kang vs Kodos
Republicans vs Democrats
Death by execution vs Death by electricution
|
|
|
|
|
Unusually advanced campaign infects people visiting a variety of poorly secured sites. I think they could re-use that title weekly
|
|
|
|
|
Hmmmm,
Over the many years... my research has repeatedly shown that the majority of browser attacking malware is actually coming from advertisement servers and ad-serving networks. Those little advertisement banners at the top often come with a javascript, webassembly or some other payload.
Best Wishes,
-David Delaune
|
|
|
|
|
WebAssembly.Studio is an online IDE (integrated development environment) that helps you learn and teach others about WebAssembly. Compile all the Webs!
|
|
|
|
|
This year’s report will give you the data you need to benchmark your activities against other survey participants, get some insights to further improve your developer team and keep up with the rapidly changing industry. They asked over 300 people, so you know it's accurate
|
|
|
|
|
This is a notation mismatch: “equals” should mean “equality”, when it really means “assign”. When in doubt, blame C (not Canada, this time)
|
|
|
|
|
No.
"==" means equality. "=" means assignment. Even in C.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Derp. Read the article and posted without thinking. Sorry about that. 
I'd blame JavaScript, but it's got even more equals (=== vs. == vs. =)
TTFN - Kent
|
|
|
|
|
So does ==== assign "===" to something or does it confirm that it's equal "=="? 
Edit: Quotes intentionally left out.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
