3 ms·
This is developers thinking like engineers when they should think like VP of Sales. What does writing a blog say about you? That, given the choice between pay
by patio11 16y ago
This is developers thinking like engineers when they should think like VP of Sales. What does writing a blog say about you? That, given the choice between paying $50 for a Wordpress blog template or paying $5,000 for your salary for two weeks, you'd pick the second option and deliver a crappier product at a hundred times the cost in a field that the decisionmaker doesn't care about anyway.
Better to spend those two weeks working to make your online portfolio/resume/sales letter (every developer should have one) absolutely sing.
- puredemo 16y agoDepends on what the end goal is. Your method is poor for the engineer who wants to learn as much as possible about his trade.
- jrockway 16y agoOf course, if you write a blog to learn new skills, you now have two things; new skills, and code to prove it. You are not in the top 0.001% of candidates looking for work (if you are looking for work, which most people that write their own blog aren't; they already have good work).
- jrockway 16y agos/not/now/. What a terrible typo :)
- jacques_chester 16y agoIs there a particular reason why I can't show that 1. I'm smart enough to get designers to design (the $50 template), and 2. I'm smart enough to write this generation's version of a text editor?
- astine 16y agoIf your stated purpose in developing your own blog was as a demonstration of your skills (or practice) and not solely the need for a blog, then writing your own makes perfect sense.
- spc476 16y agoWell, I wrote my own blogging engine (back in 2000 and I'm still using it) and I've gotten my past two jobs because of it (or rather, what I've written for it). So I would say I've gotten my money's worth out of the code. I've also avoided every exploit dujour that seems endemic with popular blogging engines (mainly due to half-thought out features that interact badly). The other aspect about writing your own blogging engine (if you can) is that you control every feature that goes in and are not dependent upon a third party to implement (or not). Besides, it's a learning experience. I'm not saying that everyone should write their own blog engine, but to say that no one should because it's a waste of time is just as bad in the other direction.