Maybe they do, or maybe they don't. In many cases, I'd argue that it's more about teaching how to think and learn, rather than "an understanding calculus will be required for everything you do in the rest of school / career / life"
It really depends on the target market, regardless. Plenty of people will be quick to tell you how many enterprise companies are still stuck with IE6. And most of them are willing to write fat checks to maintain that status quo.
Maybe this is something that many grads might not realize too, as it's quite different in contrast with hiring processes associated with Enterprise Company XYZ.
It's one of my favorite parts about startup culture in general, though. Whenever I hear people saying stuff like this (re: hiring performance vs experience) my first thought is almost always "where do I sign up?!"
The second problem is even further exacerbated as early startups don't want "employees". They want "Employee #1"; someone who is passionate and ready to help push the company forward.
I'm in my senior year of college here in the US and this definitely nails it for me. I've had some solid internships where I've done actual coding / ops / etc, but I don't feel like I'm at the technical level where I could graduate and make huge impacts for a startup.
Are startups who are past the "Employee #1" phase (or even employees 2-5, I'd imagine) in a different position in regards to this? (ie more willing to bring on a recent grad, because they already have strong technical employees/leadership pushing the company forward)
This reminds me of how we figured out in our high school computer labs how to circumvent the monitoring/control software the teacher would use.
First it was succeptible to killing the process, easy enough. Once that was blocked, we figured out that some clever use of some default applications in windows would cause it to crash and give us freedom. After those vulnerabilties were fixed or blocked, and we had tried pretty much anything else we could think of, someone figured out that hitting ctrl + alt while we logged in would prevent it from even loading in the first place!
Unfortunately it was pretty easy for our teacher to catch us in the silly act of banging on our keyboards at login.
It limits who sees it in their default stream. Anyone could still go to your page (assuming it's public) to see your tweets that start with a username, however.
I've had similar thoughts, albeit only for Google's sites. I would imagine this would be something more likely to be seen through Chrome (or even the Chromium OS).
My gut reaction is that most people wouldn't want Google on top of every other site they visit. Of course, I'm also amazed at how many toolbars I have seen people install and run concurrently in IE, so I could easily be wrong.
I believe noelsequeira is referring to the stream, which is what Facebook calls the "news feed".
It would be nice to be able to set relative ratios for how often posts from different circles show up, to result in varying frequency of the top or recent posts from each circle.
If it's for the life of the blog, I don't think anyone would have a problem paying a one-time fee. I'd also be interested in hearing if you can import posts back into Tumblr as well. (This would be useful for people who want to clone a secondary blog into a primary)
EDIT: Based on the signup page[1], there are a handful of steps that likely represent what you'll do when you backup the blog. They seem to indicate more of a one-and-done process.
That's what it's sounding like. Minecraft seems to have restored services; EVE Online has confirmed it was a DDoS[1] and is still investigating. Escapist Magazine still seems to be down.
I think the only thing they're really proving is what we already know: nearly everyone is vulnerable in one way or another; robust security is tough.
>sometimes projects do start with very simple UI and focus on application functionality, so it could be hugely helpful to consider the context of UX.
I've found this is one of the more powerful and easy ways to prevent feature creep, at least for the smaller/shorter projects I have worked on. When I start with a UI, I find it's easier to ask what the bare minimum of a) inputs and b) feedback/guidance for the user that needs to exist. In the projects where I've started with a backend first, I often end up having to create more noise on the UI side to complete it.
I think this just goes back to your first point, how developers are more effective when we're involved in creating the requirements. Practicing good design is going to be more effective when you choose to focus on it up front, instead of relegating it to something to check off a list when the application has been developed.
This is one of the toughest things I've learned in the last year or so while interning (in IT) for a fairly large insurance company. It's especially hard to affect UX when developers are typically given requirments from someone who has a specific (bad) design in mind.
Anecdote:
Just the other day we had a request come through to have a flash video (with music) automatically play on the splash page for one of our bigger applications. We ended up taking it down the very next morning after the original requestor was getting bombarded with emails and phone calls about it. I hoped they might have learned from it, but their initial response was to just move the video to another page and continue to let it play automatically. We didn't let them make the same mistake twice, though.
[1] http://www.mikewirthart.com/wp-content/uploads/2010/05/howla...