imsky

8 ms·

31.
by imsky 13y ago
Right, that's the fallacy being made constantly here - as if Weebly and Google Maps are taking jobs from developers, when really there would have been no need for a site or a mapping component in their absence.
32.
by imsky 13y ago
Good point, but we've always been automating software, and so far the market for it has been booming. The idea of "peak software" seems to involve assumptions that just don't work in the case of software development. It&
33.
by imsky 13y ago
Thanks for bringing that up, excellent article.
34.
by imsky 13y ago
Good point, but it touches on a refrain I've seen in the comments: that it might be better to keep the world in an inefficient state. Standards rise up after the complexity of interoperability becomes too much to handle. As to your poi
35.
by imsky 13y ago
Exactly right, it seems many people assume that automation or offshoring will be a smooth and seamless process with no trade-offs. That's not the case at all, offshoring and automation present their own kind of problems.
36.
by imsky 13y ago
@timr: > Well, first off, you're just shifting the goalposts and redefining what it means to "program" to suit your needs: it's inconvenient for your argument that there's now software that does what programmers
37.
by imsky 13y ago
Knowledge workers are definitely not immune to automation, I've acknowledged that in the post. They do set the bar quite high for software and intelligent agents, however. Regarding your last point, I think a knowledge worker smart eno
38.
by imsky 13y ago
The first part is technically true - the automation team can exceed the original team, but this may be a special case of "engineers untangling a mess of functionality accumulated over the years." The second part has an exception o
39.
by imsky 13y ago
@lightcatcher: >Previously, most people would say that it requires programmers to make a website. It hasn't required a programmer to build a website in many years now - HTML and CSS were declarative to begin with. It's only wit
40.
by imsky 13y ago
That's a gross oversimplification of what I wrote. If you take only Baugues's conclusion ("don't be reckless, save and network, things may not always be so great") and ignore his premises, you're reducing the a
41.
by imsky 13y ago
That's a good point - there can be serious career opportunities in managing, supporting, and modifying ostensibly "automated" solutions. The core may be automated, but the ecosystem doesn't have to be.
42.
by imsky 13y ago
Great point. The nature of the work changes as old complexity is automated away, and new growth possibilities arise as a result.
43.
by imsky 13y ago
@nrivadeneira: Yes, the point Ford made works, but it works because of the _nature of the jobs_, not because of any inherent property of theirs that influences their compensation (implied by Ford to be the knowledge/labor distinction).
44.
by imsky 13y ago
A good point, but an obvious one to economically-literate readers. The counterpoint to it is that it requires fewer developers to automate a process than it requires to write it. In the short run, unemployment may increase, but in the long
45.
by imsky 13y ago
No, this part: "A common misconception about automation is the idea that it will primarily impact >low paying< jobs that require few skills or training. To illustrate that this is not necessarily the case, consider two very diffe
46.
by imsky 13y ago
A website is not a program, let's be fair. It's at most a minimum amount of logic wrapped around content. Automating it is easy, and it has long ago lost its prestige. Re MBA guys - maybe we have a different understanding of MVP h
47.
by imsky 13y ago
We've had the tools to automate software development for years and there's been almost no movement in that direction.
48.
by imsky 13y ago
We do have programs that write programs. Who's using them? I like your optimism, but the average guy with an MBA definitely can't throw a MVP together, especially not in 2013 when the low hanging fruit have been steadily picked of
49.
by imsky 13y ago
Ford's point is a good one, but it's a bit dishonest. A radiologist's job is processing information - it's easy to move overseas or stick into an algorithm. A housekeeper's job is managing a house and the people liv
50.
Not the autoworkers of our generation(imsky.co)
81 points by imsky 13y ago|63 comments
51.
by imsky 13y ago
This is more than a year old. It was featured on Badass JS in January 2012. http://badassjs.com/post/16583192105/seriously-js-a-realtime...
52.
by imsky 13y ago
That's the founders' job though. They don't hire developers to critique their strategy, they hire them to implement it.
53.
Done - serverless GTD app, built with Twitter Flight and OpenKeyVal(donegtd.com)
2 points by imsky 13y ago|0 comments
54.
by imsky 13y ago
That's an excellent set, though I haven't seen it mentioned in any icon font roundups. Thanks.
55.
by imsky 13y ago
Great job, would it be possible to expose a public API?
56.
by imsky 14y ago
The outdated hardware often makes the savings not worth it.
57.
by imsky 14y ago
Here's my theory. Apple has made its reputation in the 90s with the film/graphics/illustration market, and that's where the Power Mac/Mac Pro was a critical product. Once the switch to Intel was made and laptops started catching up in speed
58.
Holder.js - client side image placeholders using canvas and data URI(imsky.github.com)
2 points by imsky 14y ago|0 comments
59.
cssFx.js - standalone polyfill that automatically adds CSS3 browser prefixes(imsky.github.com)
3 points by imsky 15y ago|0 comments
60.
by imsky 15y ago
Switched to it and the animations really look smoother now. Sweet release, can't wait for 1.6.1!

More ›