Amazing analysis of what developers REALLY want to work on
For me, the weekends are mostly about spending time with my family, reading for leisure, and working on the open-source projects I am involved in. These weekend projects overlap with the work that I do in my day job here at Stack Overflow, but are not exactly the same. Many developers tinker with side projects for learning or career development (or just for fun!) and at Stack Overflow, we support all types of technologies, from professional to hobbyist. Whenever people are working, we’re available to answer their questions. But what languages tend to be asked about on weekends, as opposed to weekdays?
Read more from the source: Stack Overflow Blog
There are so many unseen downsides to estimation. Instead, prioritize and get to work.
Software Estimation is a Losing Game – Should we even bother?
Let’s call it, Budget-Driven Development, or BuDD for short. In BuDD, development teams are given a set of resources and develop what they can until the budget is gone. I’m sure I just gave someone a heart attack, but when you think about it, it’s not too unreasonable. Many contracts have fixed time and costs. You make a guarantee that the customer will get a specific number of man-hours of development. Given a prioritized backlog, developers work on the three most important items. I imagine it would work similar Pandora’s prioritization model, but not be constrained by time.
You guarantee quality to your customer by:
- Delivering capability often.
- Allowing the customer to prioritize development.
Read the full article at: rclayton.silvrback.com
User experience begins with strategy and requires layers of feature scope, site structure, site skeleton, and “surface” or the graphic interface
In a post adapted from a short talk Mike Atherton gave at the SODA Social meetup in London on May 14th, 2015 he writes:
In UX there’s no ‘one-size-fits-all’ design pattern for a given situation. Despite what clients ask, there’s no more a ‘best practice from a UX perspective’ than there is a ‘best recipe from a cookery perspective’.
“Give me six hours to chop down a tree and I’ll spend the first four sharpening the axe.” – Abraham Lincoln
It’s about research, understanding, and evaluation. Figuring out the right problem to solve, before dipping into our toolbag of methods and patterns to solve it.
Read the post at Medium
Study up: here’s a peek at what interview questions you may face the next time you look for a job
Glassdoor did some research on which questions are asked in an interview.
Some you might not expect include:
– What would you look to accomplish in the first 30 days on the job?
– What motivates you?
– Who’s your mentor?
– What is the name of our CEO?
– What would your direct reports say about you?
– What was the last book you’ve read for fun?
– What is your favorite website?
– What makes you uncomfortable?
– How would you fire someone?
Read all 50 questions at Glassdoor Blog
Don’t be afraid of SVG: it is the intersection of graphic design and UI magic
Realistic motion effects are just the beginning.
View Sara Soueidan’s presentation on Slides
You might think your web site is easy to use, but what if the user is drunk?
Richard Littauer will get drunk for you. He says:
Your website should be so simple, a drunk person could use it. But you can’t test that, so I’ll do it for you.
WHAT: I’ll get very drunk, and then review your website. I’ll send you a document outlining where I thought the website needed help, and a screencast of me going over the website.
HOW MUCH: $250 per site.
Hire him at theuserisdrunk.com