He's explaining it wrong and its detracting from his point. Webforms was basically the server side ancestor of the currently very popular AngularJS. Pieces of functionality (not just UI) were encapsulated in components ("web controls") that had their own life cycle, would ensure ids were unique, could contain their own css and scripts in their own DLLs.
You'd then drop them on a design surface (or stick them in XML code), sure. But that was just a convenient way of inserting the snippet. You weren't designing your app Front Page style or anything, it just didn't work for anything meaningful.
The issue here is with the framework providing an overly complex leaky abstraction over too many things, and the issue remains if you use Emacs to do it. Again, case in point: the problem is absolutely there with AngularJS. But since you don't drag and drop the controls there, and it has a marginally better architecture (ie: its not dog slow), people feel better about it...
Too many people confused the IDE with the framework (TFA contrasts PHP, a language with a web framework that revolves around pure text rendering, usually wrapped with 3rd party MVC frameworks, to a heavyweight component based framework). It would be kind of like blaming a Ruby on Rail IDE for a programmer's reliance on Rail's scaffolding.
Typing speed is squarely in the 20. Hunt and peckers? No, but I may as well be. On a 1 month project, there's probably, what, 8 hours of typing at most? Even if you could make me type so god damn fast that I would type the entire code -instantly-, that would only save 1 day of work. The biggest part is the thinking, discussion, architecture, the stuff you don't even need a computer to do.
Then once you sit down, its about reading the code, analyzing it, re factoring it, debugging it. For all those things, typing is almost irrelevant. If your typing efficiency actually makes a dent in your productivity in the grand scheme of things, your job is probably outsourcable.
Now, as I mentionned in another post, in some type/size of projects, IDEs like visual studios may actually slow to a crawl to the point that non-typing-related tasks may get bogged down by performance and inefficiency. Then yeah, its time to switch editor.
But until then? If you can type 30 character per minute and are doing something significant, you're probably not slowed down much.
Notable exception for prototyping and testing out snippets in unfamiliar environments (like when learning a new programming language). You're likely to type/run/type/run/type/run a LOT.
Except no one has used visual studio's GUI wizards for web apps in ages. They're barely maintained, and in the javascript heavy world, they don't even work.
People who are "dependant on visual studio" use it for the integration tools (source control, though thats becoming less true as GIT is becoming de facto standard even in the Windows world, and its integration with Visual Studio is not so hot), its add-ons (a lot of people who use Resharper are quickly lost without it).
Coding in a normal editor is crippling. There's a few exceptions. I'm a big fan of Visual Studio, but the application I work on right now is simply too massive (its separated in independent modules, but my particular department tends to have cross cutting responsibilities so when we debug stuff, we go through countless modules in one session and you really want them all open), at which point its just too slow.
That only happens once your source code weights in the gigabytes though. At which point I prefer using Sublime Text. VIM and Emacs though? No real reason to use them anymore.
Only the crappy ones who can't get a better job (with a few exception of those who don't live in a tech center and have a good reason not to move...I feel for those people).
That said, I'll take a 80 hour week over living near a fracking site, thats for sure.
Thats why no one is calling it a sport. They needed a different term that people would understand without it being explained. So e-sport it is. Video game at a competitive level.
No one thinks you're gonna lose weight doing it, there's no confusion. No problems.
Well, one of the primary requirements in the summary is to not use the public cloud in favor of a private one (so stuff goes straight to your PC without touching dropbox/google drive/whatever).
While I think that's kind of a waste of time, it was pretty clear.
Even among programming languages you have the same issues.
You have a high level framework that seemingly does everything magically (think Ruby on Rails, or AngularJS), and the moment you throw a real world problem at it, things get really complicated. Subtle user experience things like validation (should it happen on blur? as you type? on submit? Server or client side? That date, should it be validated as the client's local, server's local? Should you be able to input it in multiple formats?)
So while the big high level framework makes the easy easier, the hard is just as hard, and often harder.
With non-textual programming, being via pretty graphics or other tricks, this problem is just magnified.
Coding is becoming more akin to writing now though. As in people would benefit from the basics in their day to day job.
A project manager writing a quick query on the timesheet system.
A designer writing a photoshop macro.
An accountant coding a plugin for his favorite spreadsheet.
A logistic specialist adding a screen to the ERP system.
An exec writing his own report real quick.
And so on. Thus why knowing the basics would help...this isn't a speciality skill anymore. Oh sure, actual software engineering or computer science is still its own field and a specialty. Understanding hardware is very similar to your example with cars. But understanding variables, conditionals and loops, is somewhat different.
At the end of the day, coding is just a form of applied math. Sure, not 100%, but relational database is just relational algebra, UI programming is geometry and other stuff like matrices, functional programming is...well, yanno. And so on and so forth.
You probably can squeeze in some programming in math courses so people understand the basics. Not everyone should be expected to become a master programmer, or even a code monkey, but people should know the very basics, just as how they taught me the basics of how to bake a cake or whats the difference between the basic forms of investments in school.
I don't know about free, but a ton of vendors have "personal cloud" offerings now. Western Digital network drives all have that kind of stuff now, basically all the consumer grade NAS devices do, complete with all the iphone/android apps to access it Dropbox-style and crap.
I'd be surprised if there isn't an open source stack that does it too, since the bundled hardware offerings are always a bit behind.
To go that route it has to be specific languages. English isn't my first language, yet putting aside talking to my mother, my primary language has been useful exactly once in the last 4 years. I can go out and learn Lao for giggles, that isn't exactly going to bring much to my life aside abstract cultural benefits.
If you say we should learn some mandarin, spanish, or hindi, yeah, I guess. But many other languages will not bring much more than taking a couple of international culture classes of some kind would. Or hell, just traveling a bit.
Except that stuff happens all the time, with a bunch of different countries as the source, and many predate Snowden's events by a very, very long time.
Kind of. The problem is those are companies everyone wants to work at. Maybe not you, definitely not me, but they're dream companies for a lot of people. So someone who wants to work, for, let say, Google, really will only consider an alternative offer coming from Amazon/Apple/Twitter/Intel/Whatever. All those big names. If its not a well known company for engineering, its not on their radar. So a handful of that subset fixing salaries would affect that whole segment, as they only need to outbid each other. If someone is picking between Apple and Amazon, and, let say, Amazon isn't part of the deal, then Amazon just needs to tack on 10k on top of Apple's fixed salary to beat their offer.
Yes, companies outside of that circle, the ones with less mind share, absolutely just throw money at people. They're not as cool, they can't handle the logistic to have free gourmet lunches and shuttles or be blessed by Steve Jobs, but they can just tack on an extra 40k/year and 60 grands in RSUs to outbid by a large margin. Often its not enough though to make someone turn down an offer from a big name, but it does work a lot.
Salaries go up but compared to other equivelent professional positions the share of company revenue/profit is significantly low. If you take reasonable comparisons with key professionals in other industries then you would expect software engineers to be making betweem 25%-40% than they are currently making.
Aside for Wall Street parasite, name one profession that has a better effort to salary ratio if they're good at it and have a few years of experience. Just one. I can't think of any.
Even with this kind of crap happening, salaries for good engineers keep spiking, with employers fighting each other, one upping each other, piling more bonuses, more vacations, more perks, year after year after year.
Once that trend stops and things start going down, maybe. But until then? Why would you want to standardize/equalize something when you benefit from the chaos? The companies with standard compensation packages based on specific rules almost all pay less than the others.
I just never bothered (I'm in my early 30s). I lived in suburbs near big cities, or in big cities proper all my life across a handful of countries, and there was rarely anywhere I needed to go that I couldn't reach via public transportation of some sort, with the very occasional (2-3 times a year) place I'd just take a cab to.
There's a few annoyances (when moving I hire movers, but if I'm packing myself, carrying all the empty boxes and packing material from wherever I get it is a pain), but all around its just a whole lot less worry.
Didn't save me any money though, considering how brutally expensive a houses near main subway lines are though. So its really just because I prefer this lifestyle.
Interesting. Everything i can look up, including on the US immigration site and in the docs they gave me when i got my green card about the other visas, says 1 year out of the last 3.
Slashdot Mirror
He's explaining it wrong and its detracting from his point. Webforms was basically the server side ancestor of the currently very popular AngularJS. Pieces of functionality (not just UI) were encapsulated in components ("web controls") that had their own life cycle, would ensure ids were unique, could contain their own css and scripts in their own DLLs.
You'd then drop them on a design surface (or stick them in XML code), sure. But that was just a convenient way of inserting the snippet. You weren't designing your app Front Page style or anything, it just didn't work for anything meaningful.
The issue here is with the framework providing an overly complex leaky abstraction over too many things, and the issue remains if you use Emacs to do it. Again, case in point: the problem is absolutely there with AngularJS. But since you don't drag and drop the controls there, and it has a marginally better architecture (ie: its not dog slow), people feel better about it...
Too many people confused the IDE with the framework (TFA contrasts PHP, a language with a web framework that revolves around pure text rendering, usually wrapped with 3rd party MVC frameworks, to a heavyweight component based framework). It would be kind of like blaming a Ruby on Rail IDE for a programmer's reliance on Rail's scaffolding.
IDEs are 80/20 solutions.
Typing speed is squarely in the 20. Hunt and peckers? No, but I may as well be. On a 1 month project, there's probably, what, 8 hours of typing at most? Even if you could make me type so god damn fast that I would type the entire code -instantly-, that would only save 1 day of work. The biggest part is the thinking, discussion, architecture, the stuff you don't even need a computer to do.
Then once you sit down, its about reading the code, analyzing it, re factoring it, debugging it. For all those things, typing is almost irrelevant. If your typing efficiency actually makes a dent in your productivity in the grand scheme of things, your job is probably outsourcable.
Now, as I mentionned in another post, in some type/size of projects, IDEs like visual studios may actually slow to a crawl to the point that non-typing-related tasks may get bogged down by performance and inefficiency. Then yeah, its time to switch editor.
But until then? If you can type 30 character per minute and are doing something significant, you're probably not slowed down much.
Notable exception for prototyping and testing out snippets in unfamiliar environments (like when learning a new programming language). You're likely to type/run/type/run/type/run a LOT.
Except no one has used visual studio's GUI wizards for web apps in ages. They're barely maintained, and in the javascript heavy world, they don't even work.
People who are "dependant on visual studio" use it for the integration tools (source control, though thats becoming less true as GIT is becoming de facto standard even in the Windows world, and its integration with Visual Studio is not so hot), its add-ons (a lot of people who use Resharper are quickly lost without it).
Coding in a normal editor is crippling. There's a few exceptions. I'm a big fan of Visual Studio, but the application I work on right now is simply too massive (its separated in independent modules, but my particular department tends to have cross cutting responsibilities so when we debug stuff, we go through countless modules in one session and you really want them all open), at which point its just too slow.
That only happens once your source code weights in the gigabytes though. At which point I prefer using Sublime Text. VIM and Emacs though? No real reason to use them anymore.
Only the crappy ones who can't get a better job (with a few exception of those who don't live in a tech center and have a good reason not to move...I feel for those people).
That said, I'll take a 80 hour week over living near a fracking site, thats for sure.
Yes, but the e-sport itself isn't whats helping, its stuff related to training but unrelated to the game.
That being said, there are a LOT of overweight e-sport athletes. They're the minority, but there's a lot.
Thats why no one is calling it a sport. They needed a different term that people would understand without it being explained. So e-sport it is. Video game at a competitive level.
No one thinks you're gonna lose weight doing it, there's no confusion. No problems.
Like you said, 1 to N, then its just the primary key to store.
Even if you only use 1 character, you still need link tables for display text, translations, etc. So this doesn't add much.
Well, one of the primary requirements in the summary is to not use the public cloud in favor of a private one (so stuff goes straight to your PC without touching dropbox/google drive/whatever).
While I think that's kind of a waste of time, it was pretty clear.
Even among programming languages you have the same issues.
You have a high level framework that seemingly does everything magically (think Ruby on Rails, or AngularJS), and the moment you throw a real world problem at it, things get really complicated. Subtle user experience things like validation (should it happen on blur? as you type? on submit? Server or client side? That date, should it be validated as the client's local, server's local? Should you be able to input it in multiple formats?)
So while the big high level framework makes the easy easier, the hard is just as hard, and often harder.
With non-textual programming, being via pretty graphics or other tricks, this problem is just magnified.
Coding is becoming more akin to writing now though. As in people would benefit from the basics in their day to day job.
A project manager writing a quick query on the timesheet system.
A designer writing a photoshop macro.
An accountant coding a plugin for his favorite spreadsheet.
A logistic specialist adding a screen to the ERP system.
An exec writing his own report real quick.
And so on. Thus why knowing the basics would help...this isn't a speciality skill anymore. Oh sure, actual software engineering or computer science is still its own field and a specialty. Understanding hardware is very similar to your example with cars. But understanding variables, conditionals and loops, is somewhat different.
At the end of the day, coding is just a form of applied math. Sure, not 100%, but relational database is just relational algebra, UI programming is geometry and other stuff like matrices, functional programming is...well, yanno. And so on and so forth.
You probably can squeeze in some programming in math courses so people understand the basics. Not everyone should be expected to become a master programmer, or even a code monkey, but people should know the very basics, just as how they taught me the basics of how to bake a cake or whats the difference between the basic forms of investments in school.
I don't know about free, but a ton of vendors have "personal cloud" offerings now. Western Digital network drives all have that kind of stuff now, basically all the consumer grade NAS devices do, complete with all the iphone/android apps to access it Dropbox-style and crap.
I'd be surprised if there isn't an open source stack that does it too, since the bundled hardware offerings are always a bit behind.
You never learned of subjunctive, conditional, imperative, indicative? All native english speakers I talk to said they did.
French is my first language, and it is pretty silly with all its extra tenses. Not too sure what it brought to your life to learn them...
To go that route it has to be specific languages. English isn't my first language, yet putting aside talking to my mother, my primary language has been useful exactly once in the last 4 years. I can go out and learn Lao for giggles, that isn't exactly going to bring much to my life aside abstract cultural benefits.
If you say we should learn some mandarin, spanish, or hindi, yeah, I guess. But many other languages will not bring much more than taking a couple of international culture classes of some kind would. Or hell, just traveling a bit.
Except that stuff happens all the time, with a bunch of different countries as the source, and many predate Snowden's events by a very, very long time.
Of course, but his sample for a developer was also obviously not one of the higher scale ones that can be gotten on the west or east coast, either.
Kind of. The problem is those are companies everyone wants to work at. Maybe not you, definitely not me, but they're dream companies for a lot of people. So someone who wants to work, for, let say, Google, really will only consider an alternative offer coming from Amazon/Apple/Twitter/Intel/Whatever. All those big names. If its not a well known company for engineering, its not on their radar. So a handful of that subset fixing salaries would affect that whole segment, as they only need to outbid each other. If someone is picking between Apple and Amazon, and, let say, Amazon isn't part of the deal, then Amazon just needs to tack on 10k on top of Apple's fixed salary to beat their offer.
Yes, companies outside of that circle, the ones with less mind share, absolutely just throw money at people. They're not as cool, they can't handle the logistic to have free gourmet lunches and shuttles or be blessed by Steve Jobs, but they can just tack on an extra 40k/year and 60 grands in RSUs to outbid by a large margin. Often its not enough though to make someone turn down an offer from a big name, but it does work a lot.
Salaries go up but compared to other equivelent professional positions the share of company revenue/profit is significantly low. If you take reasonable comparisons with key professionals in other industries then you would expect software engineers to be making betweem 25%-40% than they are currently making.
Aside for Wall Street parasite, name one profession that has a better effort to salary ratio if they're good at it and have a few years of experience. Just one. I can't think of any.
Even with this kind of crap happening, salaries for good engineers keep spiking, with employers fighting each other, one upping each other, piling more bonuses, more vacations, more perks, year after year after year.
Once that trend stops and things start going down, maybe. But until then? Why would you want to standardize/equalize something when you benefit from the chaos? The companies with standard compensation packages based on specific rules almost all pay less than the others.
I just never bothered (I'm in my early 30s). I lived in suburbs near big cities, or in big cities proper all my life across a handful of countries, and there was rarely anywhere I needed to go that I couldn't reach via public transportation of some sort, with the very occasional (2-3 times a year) place I'd just take a cab to.
There's a few annoyances (when moving I hire movers, but if I'm packing myself, carrying all the empty boxes and packing material from wherever I get it is a pain), but all around its just a whole lot less worry.
Didn't save me any money though, considering how brutally expensive a houses near main subway lines are though. So its really just because I prefer this lifestyle.
Yeah, because the average QA is a master of cryptography. You need to hire security specialists for this....and they did.
Now, after all of that, they want to make sure nothing slipped.
jQueryUI makes sure your client side programming does NOT work =P
Dart has an actual VM of its own. Its probably what they're benchmarking. It can be cross compiled, but it doesn't have to.
Agreed. Now though, we have LEDs, which are basically better in every ways (and are getting fairly close in price) and don't have the disposal issue.
Problem -> solved.
Interesting. Everything i can look up, including on the US immigration site and in the docs they gave me when i got my green card about the other visas, says 1 year out of the last 3.