
Parker looks like an interesting tool for general information about your CSS, but you should take its reporting with a grain of salt.
Parker looks like an interesting tool for general information about your CSS, but you should take its reporting with a grain of salt.
An excellent post from Ada Rose Edwards on Progressive Web Apps. She’s brings up some very real concerns, many of which I share:
Moving in this direction poses a lot of problems for terrestrial data. It could also increase the digital divide.
Ratcheting prices up further will only increase the digital divide, but the difference won’t just be between those who have Internet access and those who don’t. The cost of data limits could also divide the population between those who can take full advantage of high-bandwidth applications like streaming and video conferencing, and those who have to curb their usage for fear of incurring overage charges.
Another brilliant CommitStrip. My transcription follows.
A developer and his project lead are sitting next to one another.
It sucks Uncharted 4 is only available on PS4
…releasing AAAs on just one platform is unfair
Yeah I guess, but it must be awesome for Naughty Dog
They only have to develop, test and maintain their software on one single platform
I guess…
Everyone has the same processor, the same amount of memory, the same resolution…
Just think about it…
…I don’t want to think about it
Pan out to reveal the large table they are sitting at. It is littered with mobile devices.
Does anyone have a phone with Android 4.0.4?
Hmmmm…
The benefits of single platform development are easily reaped by developers, but they come at a cost to the consumer who doesn’t have the right device or specs and (moreover) it limits a project’s potential reach.
This is huge! Many thanks to Steve Faulkner and Léonie Watson for compiling this information!
An excellent post from Dion Almaer on the importance of choosing the appropriate approach for the critical tasks of your web property. He dubs it “time to first meaningful interaction”. This is where progressive enhancement shines.
The other day I got a message from someone I’ve been mentoring via email. His question was one I think a lot of folks in our industry struggle with: > Can you please tell what are keys to success and what should I do to become a successful programmer and software engineer? Anything is appreciated.
No, they don’t. Progressive enhancement, baby!
Images will be blocked. Styles will be filtered. Tables will be munged. Instead of struggling to try to make emails look the same everywhere, let’s embrace their differences.
This is an excellent presentation from Russ Weakley on how to use semantic markup and ARIA to ring dynamic experiences to life. Definitely worthy of a bookmark (or download).
For the non-visual among you…
Programmer sits at a computer with his back to a Project Manager
Hmm, it’s quite a lot of work
Contact form: 5 days
Back-office: 8 days
OK, got it
Pan out to reveal Project Lead sitting next to programmer
I’ll send the customer the quote and I’ll let you know what happens
OK, great
Zoom in on the Project Lead and Programmer
5 man-days for a contact form?? Are You kidding??
It’s half a day at the very most
You’re right…
…But you’re forgetting the 4.5 days to test the new must-have framework
Ha! Someone has to pay for it…
Sadly, this is so true.