The problem I've seen in CS grads over the last 10-15 years is they have little to no engineering background (even when their degree is "Computer Engineering"). Most applications are complex systems. And most CS grads don't understand systems. I've been able to teach EEs, a chem E, a civil E, an MD and a CPA (among others) how to program. And they've had no trouble implementing solid class hierarchies and robust applications. It's much harder to teach a CS grad about structural integrity, analyzing a design for weaknesses, and root cause analysis. In some cases they won't accept those are even an issue since "software is so different from physical structures". So they keep building things that pass all the tests but repeatedly fall down once they get to production.
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
If anything it's getting too easy to get a "software development" job. Lot's of "programmers" work their way up to all levels of "software development" without expanding their understanding of software systems. Lots of others do learn along the way and belong where they rise to. But there is a lot of learning that needs to be done and many colleges don't even give a broad base to start with so even that's not always a good start. My guess is that healthcare.gov had too many people who knew how to program (i.e. "programmers") and not enough who understood systems/engineering ("software engineers" though that term is misused often since people don't understand the "engineering" aspect which takes a lot of learning )
If you want to see "exclusion" from a job try to help a sheetrocker, electrician, or plumber be allowed to be the lead architect for the next 70-story skyscraper. Or see if they can work their way up to that responsibility over the next 20 years without "requiring rare talents, grueling training, and total dedication".
Is the IG obligated to tell the people anything? Or is this an attempt for them to find out (and cover up) any wrongdoings before we find out?
"Mr S found out about a part of project X. We need to tighten security on that project before the wrong workers find out about the rest of project X. Also start monitoring all of Mr S's personal communications and arrest him if anything looks suspicious and save anything that we can use to attack him publicly and destroy his credibility if he tells a reporter that we are doing something illegal and didn't stop when it was pointed out."
Lego skills are very useful for engineering. I've been in software development 30+ years and still apply skills I learned from lego, lincoln logs, and erector sets in the 60s and 70s. You can use these sets to build almost identical looking structures in many ways . Some will fall over when you barely touch them. Some can be rolled and even tossed a short distance without falling apart. Software is the same. You can put classes together to make a robust & stable system, or use similar classes to make a similar looking fragile system.
An understanding of structural stability is the biggest lack I've seen in developers the last 10 years. Non-software engineers are generally better than software engineers right out of school because the physical engineers got some understanding of structures in school. You can't test stability in. You need to be aware of it in all phases - design, throughout implementation, and finding root causes when there are problems rather than just fixing the bug (which needs to be fixed but may or may not be the root cause).
Think of all of the warnings we hear from scientists/experts.
Mudslides, floods, hurricanes, earthquakes - there are lots of places we just shouldn't live because some day there will be a disaster.
Bridges, buildings, subways - there are lots of man-made structures we need to repair. some will collapse
Diet, medicine, excessive - it will harm society if we are allowed 20 oz drinks or salt at the table.
We could probably list legitimate warnings all day. And I'll probably experience dozens of things today that scientists have warned about. This situation is tragic but it doesn't mean anyone is to blame. With 1000s of warnings from scientists, some will happen - but most don't.
If there's anywhere to focus it's on how to evaluate and prioritize warnings across a wide variety of areas (natural disaster, diet, structures, etc). We don't have the resources to fix everything we are warned about - where do we start?
The other thing we may want to learn is that the media should not over-hype all warnings. People need to know better what warnings to pay attention to. When we watch the news and scientists say "just about everything you do today" may kill you (or the planet), why even try to fix anything?
I voted for the way I like to eat them raw. But I want a big range when I'm cooking depending what's cooking and who it's for.
Detection of extreme weather events hasn't been consistent so it's hard to say for example if there are more or more powerful hurricanes now than in the 1930's. Hurricanes need an eye witness to label them. These days we see something on radar and send a plane. In the 1930's it depended on having a boat in the area or making landfall in a populated area. One result is that there are a lot more recorded cat 1 and 2s now than 100 years ago but not so many more 4s and 5s (very likely they usually made land or were big enough that a boat recorded them before as now).
Around TAR timeframe this was not a generally accepted explanation so skeptics were called wrong when they pointed it out. But now it is more accepted and the latest IPCC report reduced their confidence that AGW will make hurricanes worse.
We can "prove or dis-prove" a lot if you're talking about 20-30 years. When you go back further it's much harder to say things are worse. Methods and devices have changed. We don't always even have access to those devices or the people who used them, especially if you want to go back 100s of years. We know about a few decadal oscillation and 60 year oscillations and there's evidence of multi-century natural oscillations. We don't know enough about the longer oscillations to say where we are in them and how extreme weather events are affected by them vs AGW. The medieval warm period and little ice age could cause problems for AGW supporters if it ends up that there is a multi-century cycle peaking that contributes to these extreme events. But, we really don't know much about those centuries or weather events in them.
I liked what I saw co-workers able to do with it and saw potential once I got it figured out so I kept at it. It took me a few weeks to get used to it but once I did, I loved it.
I was part of dozens (20-40) of projects at a time and it was great for keeping all of my notes about each project organized as I went from meeting to meeting. After I left that job (too many meetings) I didn't have a paid version of office. I've been more than happy with substitutes for everything else but have missed OneNote.
The government should be studying civilization, but if this is where NASA decides to spend money, we need private businessmen funding any space related science. Maybe we can get the USDA to fund the next Mars mission.
another way of saying "jack up parking fees".
That's what I've seen in a very big company (100s of web sites)
Once you've met accessibility laws and blown this year's budget on new cookie laws and have done a lot to ensure privacy and security is a big cost and risk to be mobile friendly.
Add to that creative agencies who are GREAT at non-interactive but just getting good at desktop Web usability and mobile is tough. Agencies aren't always good with you going somewhere else for Web/mobile. And the interactive agencies aren't always good at understanding brand equity which is VERY important to the overall marketing strategy.
There are many other reasons (crappy old CMS). But I'd put legal and creative as the two biggest by far.
The front door on my house works great for me. A bank wouldn't want to use it to protect their vault.
My router does fine for me. I'd like my politicians, and boss, and many other people who's decisions & actions affect me to be better protected than I am, but I can't build a custom router for them.
Credit card companies could google all of the numbers for cards they have issued and take care of it themselves. Why would this be google's responsibility?
Many development project don't need a 'rock star'. They can be done with "typical" architectures, existing frameworks, and just need "assembly-line-type" workers for all of the steps. I'd even say "most" projects are like this and any project can survive without a rock star.
There are also different types of 'rock stars' and they can help on even the most basic project. In general, the 'rock star' can do any/all of these things, but what do they do on a day to day basis varies based on their individual "specialty"
* some can architect the "difficulty 10" projects so it can be implemented in assembly-line fashion by "typical" developers
* some can implement the "difficulty 10" projects that wasn't architected well (when a team of N "normal" developers would end up with a late and buggy implementation)
* some can debug like nothing most people have ever seen (they don't usually create difficult-to-find bugs but are a huge asset to the team when the bugs come up which can happen on even the most trivial project)
* some just implement so well (speed of development + lack of bugs) that they literally will be cheaper than a team of N people (so, to the manager they aren't necessary but would be preferred)
* some can mentor, and find other people's strengths, and reorganize efforts on the fly. they can help everyone else be more productive, and can adapt the process/team as requirements change and can be critical to delivering on time and above requirements especially when things go wrong.
* some can help where ever needed (front-end, db, back-end, sysadmin, security, build, etc) and can step in without losing a beat when another member of the team is out (sick, vacation, left for another job).
* some can find bugs in 3rd party libraries or system components (without the source code). find workarounds and/or patch those libraries to continue development quickly while sending the bug fix and appropriate level of explanation to the library developer to get a permanent fix. If you've ever been on a "difficulty 5" project which found a show-stopper bug in a critical 3rd party library during QA, you'll really appreciate this skill. I have seen one case on a "trivial" project where this skill was necessary and a few other cases where it really helped.
I've worked with a very small number of "rock stars" over 30 years. They all had multiple of the above skills. I've worked with 3x as many people who were considered "rock stars" (by themselves and sometimes others) but weren't. In almost all cases, the "fake rock stars" slowed the project down more than they helped and the team would have been better off with one less member.
I have a low-end phone. It came with a number of google apps that "work" (google play music/books/mags, youtube, google+). When I set "automatically update" it gives me new versions that eat up the battery, run in the background when I don't want, or fail to update because they are too big. I can't disable the new apps unless I uninstall back to the original and I can't uninstall the original but only disable it. So I have to update manually and only get the apps I want to update.