Yeah, seem to do me the model would work best if you just have a basic income, no questions asked.
Want your shiny iphone and car and house and stuff though? Either starve yourself and save pennies for years, or get to work and pay taxes (that will fund those who choose to do something else).
For programming its pretty common. For a lot of the northern states, Canada is closer than going across the country. TN1 visa is okay, but people eventually want something more permanent for quality of life (TN1 makes it hard to own property, for example), so a lot of H1Bs go to Canadians.
And with all the startups in Cambridge, NYC, etc, its VERY hard to build a team of any significant size, even if you're allowing remote workers, pay for relocation, etc.
While there is age discrimination, there's 2 other things that probably matter as much.
First, people burn out in Software Engineering. Its rewarding, and extremely high paying, but the barrier for entry is low (you don't need a master or a PhD, and in many cases, you don't need a degree at all lately), and the job is hard. That means a lot of exit. This is a bit different from, let say, a doctor, who did a PhD...not something they'll walk away from at the drop of a hat.
Second, its a field where you need to keep your skills up to date. Some of it is just stupid hypes, but some things genuinely get revisited, and the commonly accepted "best way of doing things" change. If you don't keep up to date, you die.
Put those 2 things together, and no matter what, you'll have a steady attrition, much faster than in other fields, keeping the average age down. And well, the push to "bring more people in IT" means the input of new software eng today is a lot higher than the input a couple of years ago, so yet another reason you'd have more younger devs.
I don't use much (3-4gb a month), but i can easily see how someone could do more:
1) watching movies in bed 2) tethering from a coffee shop.
When you have unlimited, some habits also change...I have an unlimited plan now (promotion, obviously I wouldnt with my usage), and I'll do stuff like download a large game while walking to the subway because....I can.
There's how much you can sleep, how much you need to not feel like shit, and how much you need for your brain to work at peek efficiently.
Those 3 things are very, very different numbers.
You can feel great but not have slept enough for your brain to be at its peek. You can be able to sleep 10 hour straight but feel bleeeeeeeeeeeeerg when you wake up, etc.
The former is usually what people "who only need 6-7 hours!!" say. "But i feel great!". Yeah, but you'd do better if you slept more.
Edge isn't bad. The devtools are decent too, so it's not terrible to test your stuff against.
But the fonts. Omg the fonts. With only basic grayscale antialising, unless you have a 4k display and scale at 125% or higher, the fonts are worse than Linux's were in the late 90s.
in the SF and Valley areas, as well as on the east coast (Boston, NYC, etc), the average "half life" of a software engineer before they quit to go elsewhere is ridiculously low. Between 1 and 2 years depending on the city.
There's a lot of reasons and theories for it... "just because they can", "its easier to jump ship than wait for a promotion", "you get bigger raises that way", "seeing more companies make you a better engineer", etc etc etc.
Its almost an habit at this point. Not sure its great for the industry, but for the employees, its an environment thats hard to beat.
That stupid fad is created by small tech startups looking at how unicorn companies run, then bringing that in the big boy world and eventually going "What the fuck have we done?!"
Yeah, if you microservice everything, you can ship those services faster. Much much faster. You redefined what it means to "ship". Instead of shipping a full feature, you shipped a tiny piece of one. But now that thing has to interact and be compatible with everything else that talks to it.
At first, it just makes things easier. Until all the stuff you extracted into microservices become tech debt (well, they were tech debt to begin with: that's why extracting them out increased your velocity, and ignoring them is making you so much faster). You can't forget they existed forever...and it comes back. "Who knows what service XYZ does again?" "Look at that fucking outdated doc on the wiki! Good luck! Its in Perl 3!"
And then you just massively increased complexity and trashed your velocity. It just happens later. Congratz, you can scale devops sky high...for a short of time...maybe a few years if you're good. Then it comes crashing down. But you can tell yourself its because you're not a "big company" and the "nimble startups" are catching up...until they make the same mistake.
I can't find the page right now, but Google publishes an official "update SLA", where they say how long they will update their devices. So far they've always followed it as a minimum, and in many cases pushed updates for longer. It is a bit short for taste though, but you at least get to know what you're in for.
The problem is Mac (though they can run some amount of games) and, more importantly, lap-tops.
Those macbook air don't run games very well. They'll run them, sure. But after 2 years? They'll still work fine for email and word processing and light image editing. But for games? Nope nope nope.
bug specific to the version of jira you use or something? My previous company used jira with 500~ engineer/product people, and almost everyone used Chrome with it no problem... Current one uses the latest version of Jira, about 80 product/engineers, and i think only 2 people use firefox. No one has issues with it.
This time its a bit special, and kind of similar (just a little) to the days of the 9000 series, where an implementation decision completely fucked them over once the next version of directx came out.
The async compute shaders don't quite work as expected on their current cards. I didn't keep up so my info could be up to date, but they were going to partially fix it in software.
I dunno if it happened or will happen and how effective it will be. But any game implementing async shaders in DX12 would tilt things in AMD's favor to some extent.
Most homeopathic "medicines" are unpatented herbal potions
Nope. Homeopathy != herbal remedy, natural medicine, or whatever else. It is something very specific. If it contains anything else but water (on top of whatever it takes to make a pill or whatsnot) and negligible traces, if any, of active ingredient, it isn't homeopathy
It seems to me like it would be purely a supply and demand thing.
If you only look at the pool of devs in a locality, you have, at most, the population within a couple of miles range of that locality. If you accept remotes, you have the entire world. And you only need 1 (or 10, or 100, or 1000, doesn't matter). Your demand is fixed, but your supply changes depending on if you want on site vs remote.
Then you have the fact that the guy who's paying for his million dollar condo in SF/NYC/Cambridge will negotiate a lot harder than the guy who's living in upstate NY.
Obviously, if you made a name for yourself, since highly qualified engineers are hard to find, you basically can bill whatever the fuck you want.
It's the pendulum issue. Once upon a time, people thought all they needed was coders. They would hire anyone that could code, or even outsource the job.
They didn't work so hot, because you actually need someone with critical thinking, business knowledge, experience, and the ability to actually engineer a system, not just code it, to keep it ticking.
So then they go the other way. Coders are useless, I just want the tip top 1% of the 10x devs. Now, even forgetting how hard it is to find these folks, there's another problem: When you're trying to do something stupid, the engineer you just hired will actually tell you. And that hurts your ego, as a product manager, CEO, whatever. Its your job to tell how the product should be built! The fact that the guy or girl you just hired has already done the same damn thing you thought was your brilliant idea before, and will tell you better ways of doing it...that just causes friction.
So then you realize what you really want is someone to acts on your marching orders...a coder!
Then why do I keep reading here that they don't? Is somebody lying?
It's almost as if different universities have different standards. CMU doesn't pay world class robotic professors the same as the local community college pay the CS 101 teacher..
my biggest gripe about Edge is the font rendering. Unless you have a 4k display and upscale to 125% (minimum), it looks like Linux's fonts in 1999.
I'm not that sensitive to these things, but in a browser where i spend most of the time looking at text, something that bad is too much. I don't even mind ClearType vs MacOSX/FreeType. But the grayscale thingy they use in Edge is just useless unless you have god-level DPI.
And why do I care or want web applications to replace native apps? I personally like having the source code to the software I run.
A lot of people care.
Eg: if someone wants to store a trillion data points and run reports on them, it sucks a lot to have to run that yourself. Sure, you could have a fucking desktop app to render the UI that you have to install with dependencies and shit. Its still going to go talk to the server running potentially hundreds of milions of lines of code to make it happen.
If you want to see the javascript of the "web client", Chrome is pretty good at unminifying these days (short of the variable names. You'll live).
Slashdot Mirror
Yeah, seem to do me the model would work best if you just have a basic income, no questions asked.
Want your shiny iphone and car and house and stuff though? Either starve yourself and save pennies for years, or get to work and pay taxes (that will fund those who choose to do something else).
For programming its pretty common. For a lot of the northern states, Canada is closer than going across the country. TN1 visa is okay, but people eventually want something more permanent for quality of life (TN1 makes it hard to own property, for example), so a lot of H1Bs go to Canadians.
And with all the startups in Cambridge, NYC, etc, its VERY hard to build a team of any significant size, even if you're allowing remote workers, pay for relocation, etc.
While there is age discrimination, there's 2 other things that probably matter as much.
First, people burn out in Software Engineering. Its rewarding, and extremely high paying, but the barrier for entry is low (you don't need a master or a PhD, and in many cases, you don't need a degree at all lately), and the job is hard. That means a lot of exit. This is a bit different from, let say, a doctor, who did a PhD...not something they'll walk away from at the drop of a hat.
Second, its a field where you need to keep your skills up to date. Some of it is just stupid hypes, but some things genuinely get revisited, and the commonly accepted "best way of doing things" change. If you don't keep up to date, you die.
Put those 2 things together, and no matter what, you'll have a steady attrition, much faster than in other fields, keeping the average age down. And well, the push to "bring more people in IT" means the input of new software eng today is a lot higher than the input a couple of years ago, so yet another reason you'd have more younger devs.
I don't use much (3-4gb a month), but i can easily see how someone could do more:
1) watching movies in bed
2) tethering from a coffee shop.
When you have unlimited, some habits also change...I have an unlimited plan now (promotion, obviously I wouldnt with my usage), and I'll do stuff like download a large game while walking to the subway because....I can.
No no no.
If Uber was the same price, but with the current service, people would still go for it.
Did you forget how Uber became popular? With Uber Black. They scaled with UberX, but that was NOT their claim to fame.
Uber Black, a service that was -WAY- more expensive than a normal taxi, made a killing. Because taxis FUCKING SUCK.
Thats not true though.
There's how much you can sleep, how much you need to not feel like shit, and how much you need for your brain to work at peek efficiently.
Those 3 things are very, very different numbers.
You can feel great but not have slept enough for your brain to be at its peek. You can be able to sleep 10 hour straight but feel bleeeeeeeeeeeeerg when you wake up, etc.
The former is usually what people "who only need 6-7 hours!!" say. "But i feel great!". Yeah, but you'd do better if you slept more.
Edge isn't bad. The devtools are decent too, so it's not terrible to test your stuff against.
But the fonts. Omg the fonts. With only basic grayscale antialising, unless you have a 4k display and scale at 125% or higher, the fonts are worse than Linux's were in the late 90s.
Its unbearable.
And then if they go through "special" schools, they just get destroyed once they hit the real world, where things aren't so nice.
Then everyone is like "see see?! I told you women weren't as good!"
And you just made things worse.
in the SF and Valley areas, as well as on the east coast (Boston, NYC, etc), the average "half life" of a software engineer before they quit to go elsewhere is ridiculously low. Between 1 and 2 years depending on the city.
There's a lot of reasons and theories for it... "just because they can", "its easier to jump ship than wait for a promotion", "you get bigger raises that way", "seeing more companies make you a better engineer", etc etc etc.
Its almost an habit at this point. Not sure its great for the industry, but for the employees, its an environment thats hard to beat.
I assume a large chunk of those bonuses are going to normal employees (tech companies often have 10%+ in yearly bonus as a normal thing).
Those bonuses are taxed. And then they're spent, and thus taxed again.
I dunno what's the income tax on that side of the world, but I'm going to go on a limb that it's going to be more money than corporate tax.
That stupid fad is created by small tech startups looking at how unicorn companies run, then bringing that in the big boy world and eventually going "What the fuck have we done?!"
Yeah, if you microservice everything, you can ship those services faster. Much much faster. You redefined what it means to "ship". Instead of shipping a full feature, you shipped a tiny piece of one. But now that thing has to interact and be compatible with everything else that talks to it.
At first, it just makes things easier. Until all the stuff you extracted into microservices become tech debt (well, they were tech debt to begin with: that's why extracting them out increased your velocity, and ignoring them is making you so much faster). You can't forget they existed forever...and it comes back. "Who knows what service XYZ does again?" "Look at that fucking outdated doc on the wiki! Good luck! Its in Perl 3!"
And then you just massively increased complexity and trashed your velocity. It just happens later. Congratz, you can scale devops sky high...for a short of time...maybe a few years if you're good. Then it comes crashing down. But you can tell yourself its because you're not a "big company" and the "nimble startups" are catching up...until they make the same mistake.
I can't find the page right now, but Google publishes an official "update SLA", where they say how long they will update their devices. So far they've always followed it as a minimum, and in many cases pushed updates for longer. It is a bit short for taste though, but you at least get to know what you're in for.
Android updates work fine on Nexus. They have an official SLA and they stick to it. Only hiccups are sometimes they're delayed, but they come.
The problem is Mac (though they can run some amount of games) and, more importantly, lap-tops.
Those macbook air don't run games very well. They'll run them, sure. But after 2 years? They'll still work fine for email and word processing and light image editing. But for games? Nope nope nope.
This service is for people who dont want to buy a gaming PC.
And we pushed really hard to increase high skill labor headcount, pushing a percentage of those people up. Great.
Do you think we can keep doing that forever? That everyone, given the chance, can get a PhD?
bug specific to the version of jira you use or something? My previous company used jira with 500~ engineer/product people, and almost everyone used Chrome with it no problem... Current one uses the latest version of Jira, about 80 product/engineers, and i think only 2 people use firefox. No one has issues with it.
huh? Jira works fine (well, as fine as Jira can work) in Chrome, Safari, even Edge (well, shitty fonts aside).
Firefox is just so fucking slow all around.
This time its a bit special, and kind of similar (just a little) to the days of the 9000 series, where an implementation decision completely fucked them over once the next version of directx came out.
The async compute shaders don't quite work as expected on their current cards. I didn't keep up so my info could be up to date, but they were going to partially fix it in software.
I dunno if it happened or will happen and how effective it will be. But any game implementing async shaders in DX12 would tilt things in AMD's favor to some extent.
Nope. Homeopathy != herbal remedy, natural medicine, or whatever else. It is something very specific. If it contains anything else but water (on top of whatever it takes to make a pill or whatsnot) and negligible traces, if any, of active ingredient, it isn't homeopathy
It seems to me like it would be purely a supply and demand thing.
If you only look at the pool of devs in a locality, you have, at most, the population within a couple of miles range of that locality. If you accept remotes, you have the entire world. And you only need 1 (or 10, or 100, or 1000, doesn't matter). Your demand is fixed, but your supply changes depending on if you want on site vs remote.
Then you have the fact that the guy who's paying for his million dollar condo in SF/NYC/Cambridge will negotiate a lot harder than the guy who's living in upstate NY.
Obviously, if you made a name for yourself, since highly qualified engineers are hard to find, you basically can bill whatever the fuck you want.
It's the pendulum issue. Once upon a time, people thought all they needed was coders. They would hire anyone that could code, or even outsource the job.
They didn't work so hot, because you actually need someone with critical thinking, business knowledge, experience, and the ability to actually engineer a system, not just code it, to keep it ticking.
So then they go the other way. Coders are useless, I just want the tip top 1% of the 10x devs. Now, even forgetting how hard it is to find these folks, there's another problem: When you're trying to do something stupid, the engineer you just hired will actually tell you. And that hurts your ego, as a product manager, CEO, whatever. Its your job to tell how the product should be built! The fact that the guy or girl you just hired has already done the same damn thing you thought was your brilliant idea before, and will tell you better ways of doing it...that just causes friction.
So then you realize what you really want is someone to acts on your marching orders...a coder!
And the cycle repeats.
It's almost as if different universities have different standards. CMU doesn't pay world class robotic professors the same as the local community college pay the CS 101 teacher..
my biggest gripe about Edge is the font rendering. Unless you have a 4k display and upscale to 125% (minimum), it looks like Linux's fonts in 1999.
I'm not that sensitive to these things, but in a browser where i spend most of the time looking at text, something that bad is too much. I don't even mind ClearType vs MacOSX/FreeType. But the grayscale thingy they use in Edge is just useless unless you have god-level DPI.
A lot of people care.
Eg: if someone wants to store a trillion data points and run reports on them, it sucks a lot to have to run that yourself. Sure, you could have a fucking desktop app to render the UI that you have to install with dependencies and shit. Its still going to go talk to the server running potentially hundreds of milions of lines of code to make it happen.
If you want to see the javascript of the "web client", Chrome is pretty good at unminifying these days (short of the variable names. You'll live).