Cool little project. If lowest cost is the goal, I am wondering if you could do it too by not having neither sqlite and litestream, and store each log as a separate object on S3.
If the goal is to acquire a skill, it's about deliberate practice... I have to come up with a project I want to do, make sure I have energy for it, set time aside for some days, and take a step forward each day (or each other day..)
If the goal is to acquire new knowledge and explore new fields, setting 1h aside each day to read (and study/highlight) non-fiction books works very well for me. I am very strict about this, almost like a second job. For me, it's about acquiring and digesting knowledge gradually. More than 1h a day does not work for me.
I set up my own consulting company and, when not working for clients, I am trying to work on some of the common issues I found in businesses I worked in.
I just launched a simple tool: http://stackbiller.com - it's a tool to keep track of all the SAAS subscriptions a company may have. It's a small tool but hopefully will be useful.
I have been thinking about how to approach this in several projects, and while scheduled lambda calls do the job, besides being AWS specific, do not integrate well with the "old way": launching shell commands.
The beauty of shell commands to me was that you can launch them both with cron and manually. Arguably you could do the same with lambda, but here we go, another service to set up (api gateway).
I built http://croningen.io - which is a hosted version of cron that schedule jobs on clusters of servers, with central error reporting. It is in my opinion as easy to use as cron, with most annoyances removed. Early days, but feedback welcome!
20 years of experience in Python, 6 in Django and GeoDjango, 20 years in Linux administration, 5 of which doing Devops in Ansible, 5 years as an architect and head eng, 1 year as a CTO. Experience also in Go, Clojure, JS, Puppet, Salt, Terraform. Many years of exp in AWS and GCE, and Docker.
I can help planning and executing complex projects spanning product planning, devops, backend, management. I have done so in high growth startups of small and large size.
I am available for a quick call to talk about what your project needs and how I can help.
Ideally looking for contracts or a position that gives me a chance to learn what I don't know. I have a ton of experience in python / django, and still quite a bit in other tech stacks as I like to try them all :)
I agree with the author... In the context of startups that are very much in "discovery" mode (still doing big changes to their product) breaking the repositories in subparts is just a source of confusion for the tech lead. I would also argue it is bad for devs because they then need to manage version-binding between different repos.
Many repos approach is only justifiable if you have many teams with many tech leads each independently doing releases.