rzarate

Kudos to the author(s) for building LiteFS, it really does seems like an interesting project. However, I can't see this being a popular pattern moving forward (or at least I hope that's not the case).

Replacing APIs with DBs in real production workloads? Really? I don't have much else to say. Also, the value proposition is not quite clear to me. Using replication to have local, read-only replicas of an SQLite db might admittedly be beneficial for high read-throughput workloads but I'd imagine that the DB might have serious size/read-throughput constraints due disk space and network overhead from replication.

My takeaways are: a) This doesn't sound like a reliabile pattern to build distributed services. b) It's bad PR for fly to publicly push for the adoption of this pattern. c) It's even worse PR that fly is using this internally.

  Location: Mexico (PST/CST)
  Remote: Yes
  Willing to relocate: Yes
  Technologies: Mostly Golang, Python and C++. Have done some JS (and TS) in the past.
  Résumé/CV: https://drive.google.com/file/d/1hW8Xqd31C0zzMWkfVfGWfklXjMzNrnjY/view
  Email: rafazrte [at] gmail.com
  Github: https://github.com/rafazrte

About me: I'm a self-taught SWE currently based in the UK but in the process of relocating back to Mexico. Looking to go back to startups after trying (and disliking) big tech.

Experience: ~5 YOE as Software Engineer. I have experience working at various early stage startups (including one YC startup) and, currently, at FAANG. Previous roles include: backend engineer, data engineer and SRE.

Looking for: Fully remote, (full|part)-time backend engineering roles.

I was expecting the link to take me to a landing page for a database implementation based on wood analogies.

Can you elaborate on the kind of in-house tooling that is essential to keep monorepos sane?

Ugh, php...

I agree, that's closer to what an intern would make in NYC rather than a director. I'd consider changing industries, maybe engineers are not as valued in marketing agencies as they would on other more tech-heavy industries.

I recently faced the same realisation. I'm a software engineer with several years of experience and somehow felt like I didn't know enough about formal computer science/math to tackle the problems I found most interesting (usually very abstract, foundational stuff).

One day I decided to go to a physical bookstore and buy a bunch of books from the Math and Computer Science sections and started from there. It was probably not the best way to start but A START nonetheless. Given that I really enjoyed reading about these topics, I decided to enrol into an online university to pursue a degree in Mathematics.

The book I found the most useful was "How to Prove It"[0]. From my point of view, it was a great starting point for two reasons: * It is approachable (specially for Software Engineers) without being boring. You start building intuitions and it really ignites your curiosity. * It is also sufficient for understanding proves and mathematical notation/language. This is an important building block that will allow you to start tackling the branches in Math you are interested in.

[0] https://www.goodreads.com/book/show/739735.How_to_Prove_It

I'd love to see a violation category for error handling (ie. making sure that all exceptions are handled appropriately).

After using Golang for an extended period of time, coming back to Python has been frustrating at times because it is not as straight forward to handle errors/exceptions (especially when using external libraries that aren't well documented).