IT and perhaps all of STEM is becoming increasingly specialized such that you pretty much have to move to different cities and states as demand changes. If you value stability in both location and the type of work you do, IT is probably NOT for you. Sys admin use to be a fairly "generic" field that you could find in any city, but cloudness is moving many of such jobs into cloud "warehouses", which are not likely located where your given house is. Sure, it's a gradual change, but new openings are more likely to be at a cloud warehouse.
It used to be a gov't job in IT was stable, but the fractious and polarized political climate has given gov't IT a boom/bust cycle also. While you are more likely to keep your job in gov't than the private sector, you still may have to move to where-ever the current administration's pork is. (Both parties have their favorite pork.) Plus, gov't pay is typically about 15% lower than private sector. You may get more retirement benefits, but you won't see those until you retire.
Just look at all those Javascript frameworks that rise and fall and don't even try to maintain backwards compatibility
Please, let's not use JavaScript as a representative of the pinnacle of dynamic languages. It's common primarily because most browsers support it, NOT because developers love it. QWERTY Syndrome. And sloppy library writers can ruin anything in any language.
Sorry, I don't follow you. Dynamic languages may give an org more choices about allocating resources (quality vs. features, etc.). If an org chooses to allocate those extra choices/options different then mine or your ideal, that's another matter and is NOT the "fault" of the language itself. I'm just describing the choices it gives. Boss/owner decisions are another matter. You seem to be arguing that compiled/static languages force quality on an org, and that's why they are allegedly better (at the possible expense of features-per-hour). If that's not what you meant, please clarify.
The study itself says nothing about productivity (features per hour), it's only counting bugs after the fact.
A computer big and huge enough that it can someday house his consciousness when his astonishingly healthy body someday craps out, so he can continue to MAGA...
The Orangenator. Thanks for fueling some grueling nightmares, dude. Can I bill you for lost sleep?
It could be you're coming in a tad too high for the work that is up for bid.
While some of IT pays relatively well compared to other careers, it's mostly that other careers have stagnated or shrank. Plus, IT requires constant retraining/relearning (usually on your own dime), and has agism and RSI problems associated with it. It's a risky long-term career.
While IT has done relatively well compared to other careers, it's still fairly stagnated itself if you look at longer term trends and post-40 IT salaries. The rich get richer and the rest get squeezed. The pattern continues. The left say tax the rich to put money back into the 99%'s economy, and the right say rich-tax-cuts and "deregulation" will finally make trickle-down work "properly". Further discussion of those is the usual "culture wars" debate most have heard already.
Votes? Heck no, most voters don't know or care about IT labor. Big corporations simply want cheap IT labor and are lobbying heavily to get it. IT is becoming a bigger part of their costs, and so they are looking for ways to reduce the costs. If they can't get cheap H1B's, then they want cheap Americans. Thus, if schools flood the market with IT workers, corporations can pay less. Many graduates may still be unemployed or unemployable, but that's NOT co's concern; they only care about profits. Unemployment and college debt is somebody else's problem in their minds. "Big Farma" did the same with farming labor: back-braking work for 3rd-world wages. Rinse, repeat, IT.
Since it's just about impossible to actually test the Greisen-Zatsepin-Kuzmin effect over long distances, models, indirect observations, and extrapolation of lab tests are used; but still imperfect. Perhaps I could have used a different description, but it's not far off.
FTA: This direction where most of the ultra-high-energy cosmic rays came from is a place "with an increased density of nearby galaxies," Kampert added. "These galaxies, or some subset of these galaxies, contain the sources of these cosmic rays."
They are probably from "nearby galaxies" based on the direction clustering. This would also imply the rays dissipate or weaken over distance, or else their source should appear roughly uniform across the sky, because "lasting" rays would otherwise be arriving from galaxies all over the universe in all directions. Although red-shifting (expansion) may also account for some distance-based weakening. Magnetic fields, ions, and dust in stuff in between could also weaken the rays over time. The cause(s) of the weakening is only speculative at this time.
Anyone who has ever looked into Larry's history will see that he's a pure con artist. He's like a smarter Trump. There was one executive Oracle used to have who kept champion the idea of longer-term customer loyalty and product quality. He was booted: didn't fit the get-it-now-and-get-it-fast culture of Oracle.
As more topics are piled on, perhaps some do need trimming since there's only so much room and time. The economy used to be geared around physical manufacturing. Perhaps the math education conventions need to adjust to this fact, and focus more on things like category theory and less on physics-related math.
I can't be the only one who is proud of their CS degree. The courses I took challenged me...
The degree gave me an overview of hardware, machine language, and low-level algorithms that I probably otherwise would ignore if I jumped directly into "corporate" programming languages and tools. It can give one a better understanding and appreciation for performance and edge cases, like why floating-point numbers can mangle monetary values under some circumstances.
And a well-rounded education makes one a better writer, communicator, and analyst.
A better survey would follow people for a longer period of time as they move up the ladder into architects, analysts, and management.
There is a difference between brand new ideas and general UI design. Most PHB's making dumb UI decisions are not on the cutting edge, but rather just making dumb decisions on something fairly ordinary, and not being curious about what real users may think of it.
The touch-screen smart-phone may have been a new idea (or at least a rare one) when the iPhone was designed, but Apple probably still tested beta iPhones on actual users. And Henry Ford probably tested actual cars with actual drivers. In other words, go ahead and leap-frog existing ideas, but still test those leaps with actual users.
It appears it gradually became widespread and entrenched such that nobody bothered to put a halt to it, like the parable of the boiling frog. I suspect at one point there was a conversation similar to:
PHB1: What if a program or Windows locks up? How can the user end the program or reboot?
PHB2: Well, the technicians have added a secret key combo: ctrl+alt+delete for that. But that's not very user friendly.
PHB1: How about something a little easier, such as Ctrl+Esc? It's hard to bump accidentally, but easier than ctrl+alt+del.
PHB2: We thought of something like that, but existing software may already use simpler key combos.
PHB1: We gotta come up with something, ctrl+alt+del is really ugly.
PHB2: We are not suppose to certify software that crashes and locks up anyhow. Such are not allowed to use our shiny new Windows logo on their box. I'm sure they want it, people love MS. Plus, we are to make Windows itself more reliable. We are a good team so we'll reduce problems, and the need for users to use ctrl+alt+del will be too rare to care about.
PHB1: Yes, a good team! We deserve raises. So ctrl+alt+del it is, to be rarely needed!
PH2: Rarely needed, I'll drink to that! [clink]
(Based on actual PHB conversions I've heard over the years to justify crap.)
By the way, why is there no "lock screen" option in Windows 10 "Power" options (lower left when you press Windows button)? One still has to use Ctrl+Alt+Del to lock the screen. Gates admitted it was a silly convention several years ago, so why make it the only obvious choice in 10? (Lock is under the "user" icon, which is not intuitive; it should be with the logout, shutdown, sleep, etc. options)
Hillary runs Trump's brain on a home server in her bathroom closet? There's a fun conspiracy for ya. Oh, and it's been hacked by Russians.
I'm sorry that you find reality depressing. Perhaps there is a fitting medication for you.
You got just the quality of writing yuo paid for, sir. Capitolism!
IT and perhaps all of STEM is becoming increasingly specialized such that you pretty much have to move to different cities and states as demand changes. If you value stability in both location and the type of work you do, IT is probably NOT for you. Sys admin use to be a fairly "generic" field that you could find in any city, but cloudness is moving many of such jobs into cloud "warehouses", which are not likely located where your given house is. Sure, it's a gradual change, but new openings are more likely to be at a cloud warehouse.
It used to be a gov't job in IT was stable, but the fractious and polarized political climate has given gov't IT a boom/bust cycle also. While you are more likely to keep your job in gov't than the private sector, you still may have to move to where-ever the current administration's pork is. (Both parties have their favorite pork.) Plus, gov't pay is typically about 15% lower than private sector. You may get more retirement benefits, but you won't see those until you retire.
Please, let's not use JavaScript as a representative of the pinnacle of dynamic languages. It's common primarily because most browsers support it, NOT because developers love it. QWERTY Syndrome. And sloppy library writers can ruin anything in any language.
Sorry, I don't follow you. Dynamic languages may give an org more choices about allocating resources (quality vs. features, etc.). If an org chooses to allocate those extra choices/options different then mine or your ideal, that's another matter and is NOT the "fault" of the language itself. I'm just describing the choices it gives. Boss/owner decisions are another matter. You seem to be arguing that compiled/static languages force quality on an org, and that's why they are allegedly better (at the possible expense of features-per-hour). If that's not what you meant, please clarify.
The study itself says nothing about productivity (features per hour), it's only counting bugs after the fact.
The Orangenator. Thanks for fueling some grueling nightmares, dude. Can I bill you for lost sleep?
While some of IT pays relatively well compared to other careers, it's mostly that other careers have stagnated or shrank. Plus, IT requires constant retraining/relearning (usually on your own dime), and has agism and RSI problems associated with it. It's a risky long-term career.
While IT has done relatively well compared to other careers, it's still fairly stagnated itself if you look at longer term trends and post-40 IT salaries. The rich get richer and the rest get squeezed. The pattern continues. The left say tax the rich to put money back into the 99%'s economy, and the right say rich-tax-cuts and "deregulation" will finally make trickle-down work "properly". Further discussion of those is the usual "culture wars" debate most have heard already.
Yes, it looks really serious this time.
Votes? Heck no, most voters don't know or care about IT labor. Big corporations simply want cheap IT labor and are lobbying heavily to get it. IT is becoming a bigger part of their costs, and so they are looking for ways to reduce the costs. If they can't get cheap H1B's, then they want cheap Americans. Thus, if schools flood the market with IT workers, corporations can pay less. Many graduates may still be unemployed or unemployable, but that's NOT co's concern; they only care about profits. Unemployment and college debt is somebody else's problem in their minds. "Big Farma" did the same with farming labor: back-braking work for 3rd-world wages. Rinse, repeat, IT.
If owners/bosses want to trade quantity for quality, that's up to them. Don't like it? Tough.
There's also turn-around time. If you can get more done in a dynamic language, then you have more time for testing and code review.
Since it's just about impossible to actually test the Greisen-Zatsepin-Kuzmin effect over long distances, models, indirect observations, and extrapolation of lab tests are used; but still imperfect. Perhaps I could have used a different description, but it's not far off.
I'll drink to that!
-Jar Jar fan
They are probably from "nearby galaxies" based on the direction clustering. This would also imply the rays dissipate or weaken over distance, or else their source should appear roughly uniform across the sky, because "lasting" rays would otherwise be arriving from galaxies all over the universe in all directions. Although red-shifting (expansion) may also account for some distance-based weakening. Magnetic fields, ions, and dust in stuff in between could also weaken the rays over time. The cause(s) of the weakening is only speculative at this time.
uh, it was (intended as) a joke
Anyone who has ever looked into Larry's history will see that he's a pure con artist. He's like a smarter Trump. There was one executive Oracle used to have who kept champion the idea of longer-term customer loyalty and product quality. He was booted: didn't fit the get-it-now-and-get-it-fast culture of Oracle.
As more topics are piled on, perhaps some do need trimming since there's only so much room and time. The economy used to be geared around physical manufacturing. Perhaps the math education conventions need to adjust to this fact, and focus more on things like category theory and less on physics-related math.
I'm mostly complaining about the menu design from a newbie's perspective. I'm used to Ctrl+Alt+Delete myself.
They gave an arm and a leg for a supercomputer.
The degree gave me an overview of hardware, machine language, and low-level algorithms that I probably otherwise would ignore if I jumped directly into "corporate" programming languages and tools. It can give one a better understanding and appreciation for performance and edge cases, like why floating-point numbers can mangle monetary values under some circumstances.
And a well-rounded education makes one a better writer, communicator, and analyst.
A better survey would follow people for a longer period of time as they move up the ladder into architects, analysts, and management.
There is a difference between brand new ideas and general UI design. Most PHB's making dumb UI decisions are not on the cutting edge, but rather just making dumb decisions on something fairly ordinary, and not being curious about what real users may think of it.
The touch-screen smart-phone may have been a new idea (or at least a rare one) when the iPhone was designed, but Apple probably still tested beta iPhones on actual users. And Henry Ford probably tested actual cars with actual drivers. In other words, go ahead and leap-frog existing ideas, but still test those leaps with actual users.
It appears it gradually became widespread and entrenched such that nobody bothered to put a halt to it, like the parable of the boiling frog. I suspect at one point there was a conversation similar to:
PHB1: What if a program or Windows locks up? How can the user end the program or reboot?
PHB2: Well, the technicians have added a secret key combo: ctrl+alt+delete for that. But that's not very user friendly.
PHB1: How about something a little easier, such as Ctrl+Esc? It's hard to bump accidentally, but easier than ctrl+alt+del.
PHB2: We thought of something like that, but existing software may already use simpler key combos.
PHB1: We gotta come up with something, ctrl+alt+del is really ugly.
PHB2: We are not suppose to certify software that crashes and locks up anyhow. Such are not allowed to use our shiny new Windows logo on their box. I'm sure they want it, people love MS. Plus, we are to make Windows itself more reliable. We are a good team so we'll reduce problems, and the need for users to use ctrl+alt+del will be too rare to care about.
PHB1: Yes, a good team! We deserve raises. So ctrl+alt+del it is, to be rarely needed!
PH2: Rarely needed, I'll drink to that! [clink]
(Based on actual PHB conversions I've heard over the years to justify crap.)
By the way, why is there no "lock screen" option in Windows 10 "Power" options (lower left when you press Windows button)? One still has to use Ctrl+Alt+Del to lock the screen. Gates admitted it was a silly convention several years ago, so why make it the only obvious choice in 10? (Lock is under the "user" icon, which is not intuitive; it should be with the logout, shutdown, sleep, etc. options)
For all the others, both God and I give him the one-finger solute.
Steve Jobs lied, Apple actually did UI testing.