434 karma · joined September 3, 2016
This great advice, works for blog posts too.
For my main blog [1], I manually update the feed.xml, on my „micro“ blog [2] I have a cron job doing it.
[1] https://www.conradbastable.com/essays/the-germany-shock-the-...
The SQL thing the article mentions is also true. Even if you work with higher level tech like Spark. SQL gives you a good feel for joins. I also like the fast feedback cycles you get from SQL compared to something Scala/Python based.
Micro blog: https://atoms.franz.hamburg
- Instagram-like, private photo feed, where my partner and me can share pictures of our kids with relatives and friends. Posting works via e-mail, cron job generates the feed html. Imagemagick output multiple image formats, supports iOS live photos too. The feed isn't paginated, but with lazy loading the images it's still very performant.
- Most recently and still ongoing: A recipe clean-up tool. Removes all the gunk and fluff from online recipes. Shows just the ingredients and instructions. Also understands units and quantities, so unit conversion is up next. Here it is: https://pretty-recip.es/recipe?recipe-url=https%3A%2F%2Fwww....
Some other approaches I spent a lot of time on:
* Extracting Structured Data From Recipes Using Conditional Random Fields [1]
* Chef Watson [2]
* Ingredient Parser - Model Guide [3]
[1] https://archive.nytimes.com/open.blogs.nytimes.com/2015/04/0...
[2] https://blog.kitchenpc.com/2011/07/06/chef-watson/
[3] https://ingredient-parser.readthedocs.io/en/latest/guide/ind...
[4] https://pretty-recip.es/recipe?recipe-url=https%3A%2F%2Fwww....
Sweet sweet complex software programs.
Real-estate is surprisingly hard to get rid of. Depending on the size they might be stuck with a multi-year lease. Cutting snacks and lunch doesn't substantially change the equation.
That said, I'd start looking for another job. Layoffs AND a paycut for those that remain doesn't fit well. Might as well layoff more people and keep the others "happy".
edit: This comes off as a rhetorical question. I'm really just interested what happened here. The project was assigned to both of you. I imagine that implies some responsibility for the whole of the project. You spent your "free" time learning React. Was there an organisational blocker that prevented you from helping him out, in any capacity?
Regarding the causes of many bugs, your guess is as good as mine. You'll continue to have bugs and you'll have to continue looking under the covers to understand them.