3 ms·
You should certainly blog if you did something different, something that is innovative, if you solved an interesting problem. But.. lets be honest, political co
by lossolo 10y ago
You should certainly blog if you did something different, something that is innovative, if you solved an interesting problem.
But.. lets be honest, political correctness aside. Most software engineers have nothing to blog about, they just glue some libraries and make couple of db requests and that's about all they do. Nothing what they do is innovative or worth blogging about. Not every engineer should blog or we would see tens of thousands of new links everyday on HN that would point to another blog that writes about how someone wrote an api and did 3 mysql requests - That's called spam. We already have thousands of resources/articles/blog posts that solved those problems and unless you are bringing something new to the table, what you wrote was already written.
- noobiemcfoob 10y agoThe specific problems encountered and methods that proved to be a workable solution for an engineer when gluing any set of arbitrary modules is practically guaranteed to be unique information, though mired in a ton other, more mundane information. It'll be the mark of a good writer to properly cut the content from the fat. But this isn't about being a good writer. It's about improving your own understanding and simply widening our dataset of known engineering practices.
- katpas 10y agoSometimes gluing together libraries in a certain way can produce an error or behaviour that's not documented (as it's outside the scope of each individual project) as either nobody has tried to do that before or they've not written about it. Multiple times now it's been an obscure blog post found on google that's given the answer to those issues.