-
Website
http://thinkvitamin.com -
Original page
http://thinkvitamin.com/dev/web-development-is-moving-on-are-you/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
John Griffiths
2 comments · 1 points
-
Bryan Veloso
3 comments · 1 points
-
Douglas Neiner
2 comments · 2 points
-
puppylove81
2 comments · 1 points
-
GridIron
2 comments · 1 points
-
-
Popular Threads
I have also used them a great deal when creating prototypes/wireframes, I can then share these with developers, who more often than not find even better ways to achieve what I was attempting to demonstrate
> Nowadays, things look different. First of all, for the most part it’s impossible to develop offline ‐ this is because we use hosted services, APIs and most likely you’ll write something that uses some data stored elsewhere on the web.
I disagree -- if you're doing things properly you should be stubbing that API in your test and using git locally, allowing you to work anywhere. Testing the integrated whole must usually be done online, but full integration tests can be always be run later when you've done your piece of work and you're back on the grid.
Chris
You've inspired me to get out there and check out some more hosted services and frameworks!
Because of the sheer volume and talent, people are no longer impressed by new cutting edge technologies. The competition is fierce and speed and efficiency is the most important. It's therefore often just small changes and tweaks that will make an application worthwhile for users.
Developers can do the initial heavy lifting, but only the end-users know what they really want. This will lead non-developers to build upon existing technologies to make them fit their optimal requirements
So very true! Ideas like OpenId and OpenSocial, despite current drawbacks, have great promise. However, while people are quick to point out the issues with these technologies, many of these same people are not nearly as quick to work to improve on those issues.
John Resig recently had a post about this idea, that all web developers have a responsibility to work to improve the technologies we make use of. While his post was aimed largely at submitting bug reports for browsers, the concept applies for other web technologies as well.
The new generation of WebDev practices is making life much easier.
http://jsconf2009.com/
I don't fear it, I welcome it.
Thanks,
GD
Scarface Blog
warhammer online video
And that's what makes the future of the web so exciting - sleek, efficient interfaces. At the end of the day our web applications are generally just front ends for a database, so by focusing on the UI so early on in modern development a better end product is produced.
As a freelancer, I visit a lot of small to medium companies and see how they are struggling with adapting to new technologies or best practices. I think because it's difficult to change workflow (time/money/stress) and they made a choice in their SDK 3 years ago and don't want to throw it overboard, yet.
On the other hand...I work with some great designers. And like you said, the web is becoming familiar for users because of great apps, you need people/designers to think about it this way. I build everything that moves...so I don't really think about design or requirements...they just hand it over to me. Just like I want it.
We get caught up in so many of the technical details. But at the end of the day, it's the user's experience of your app that really matters. The faster you can build a bigger better more useful and easy to use app for the user, the more people your work will reach. (that's not to say quality doesn't matter though :)
teach me how to rap
Although web development has definately moved on, for some people it is still as remote as ever. For example I kow a lot of people who would not even consider making their own website, although like you point out, development is a lot more entertianing these days.
One positive to come out of this is that you can actually get a good quality website developed for quite cheap these days.
The answer. Yes. It's over. You lay out the facts very well in your article. Web development/design is a commodity. There are sites now that will give me valid XHTML and CSS when handed photoshop or Illustrator layouts. I don't know if they are in India, Romania or just a bunch of free lancers in the states. Who cares.
I've written an essay on a very similar topic - how the web is just a mechanism to get working applications to a user. Technologies like CSS have actually raised the bar and made it more difficult.
I will be very honest here. I'm a software engineer who works for a very large ecommerce site. We are top 10 revenue producing in the US. When we need HTML and CSS we hand it off to a few guys who are good with it. Then we get it back and write the real application. Because software is big and messy and web developers do not have the software engineering chops to pull it off.
I realize this may incite hatred. I'm really not trying to start a flame war here. I'm agreeing with the author and pointing out that very large operations who make billions on the web do not really care about web development. Sounds odd right? We want to use frameworks that spit out HTML that is valid in whatever the browsers are nowadays. We don't necessarily need some guy tweaking pixels in IE6 - it's cheaper to make that page design simpler. Use less CSS or do whatever it takes. Companies don't want to pay web developers/designers. They are a pain. Right now, we just have to.
And splatterball, who remembers that!
Ten years from now a lot of how we go about our daily lives will be changed as communication will grow to the point where the web is not just cyber space but literal space.
As a freelancer (first site in 94, occasionaly taught web development for some time, then followed different interests), I'm on the verge of getting back to web development. Because it's the platform of the time and it outlines my deep interests in life : architecture (brick, metal, sound, words, bytes, whatever), and transmission (of knowledge, culture, you name it).
As you may think the shift rises questions in me. What the job, craft, market, became in the meantime? I'm spontaneously as reluctant to SDKs and frameworks as one can be. After a while, in an attemp to think it open-minded, I agreed to build my own Lego out of other's basic material. Ok.
I'd like to stress one point: not only legitimate craftsmaship pride is involved in getting things the "clean" way. Sharing is the genetics of the Net. Sooner, later, all contents will "collaborate" in some way.
Search engines show that in a (very) primitive form. Tomorrow, when they become smarter, they (and others) will drill deeper into content to do their job. Maybe then only the coherence of code will be a competitive advantage. But a huge one. In a way you cannot automate. In a way it can hamper or glorify your online visibility. Life and digital death.
Maybe not today yet. But soon, I guess.
(And sorry for the long post, english is not my native tongue.)
- T -
dog clothes
"# Take time to have a look at the SDKs, hosted services and frameworks out there and write about them instead of showing yet another proof of concept."
Cool site!
posted by a spycams freak.
I think the problem is that so many developers (like myself) have got fed up of the corporate nagging that they've ended up working for themselves and in a lot of cases working on open source systems that average Joe User can set up with a few instructions.
Now I'm not saying it's wrong to empower people-who-aren't-technically-developers in this way OR that the software that has been developed is bad. It's just that it really doesn't suit every use case. Frameworks and SDKs are a little better as their scope is generally more generic, but they're more difficult for Joe User to understand.
Plus, the more generic you get, the more bloated you get, having to cater for possible eventualities that simply might never be. For some of us, that's a factor that we're prepared to negotiate. For others, a competitive solution is the only way to go.
For the past two years I believed I could do it better. The solution I've come up with could be classed as a web app framework/CMS. I guess it's along the lines of Drupal. The key issue for me though is that it's tighter, it does what I need it to, which means it's leaner. It's faster.
You could argue that trimming back is better than building up, but in this case there was also a deep personal development incentive. Will I release the solution as open source? Maybe one day. Will I make people pay through the nose for it? No!
It is a way for me to develop web applications faster and in a way that is extensible as far as existing and future technologies suggest it needs to be. So efficiency is the key for me, without a lack of quality. It's not so much being a control freak, but just being 100% sure that everything I develop with this will be effective in all areas that I need it to be.
If you can get that same sense of satisfaction from another piece of software that already exists... great! If you're not bothered about it... then you should probably be worried...
Insightful.
You've inspired me to get out there and check out some more hosted services and frameworks!