jbmsf

12 ms·

91.
by jbmsf 5y ago
When I set up a product deployment system, I want: 1. IaC for the network, database, container definitions, and other cloud things. I use terraform here. 2. CI/CD for the application software, which ultimately builds a container image
92.
by jbmsf 6y ago
I think it's economy of scale, not kool-aid. I can run PostgreSQL myself but there's a ton that goes into running it with redundancy, backup, encryption, etc that takes deep expertise to well. I know from experience that it's
93.
by jbmsf 6y ago
Strong agree. Plus I've seen more than a few efforts at multi-cloud that resulted in a strong dependency on all clouds vs the ability to switch between them. So not only do you not get to use cloud-specific services, you don't rea
94.
by jbmsf 6y ago
I take your point, but I still don't quite agree. There are obviously plenty of companies that are willing to couple themselves to a single cloud vendor (e.g. Netflix with AWS) and plenty of business continuity risks that companies don
95.
by jbmsf 6y ago
I can't agree, at least not in general. The optionality of being cloud agnostic comes with a huge cost, both because of all the pieces you have to build+operate and because of the functionality you have to exclude from your systems. I
96.
by jbmsf 6y ago
It's always a trade-off though. You say you write most of your own software, but that's probably not true for, say your OS or programming language, or editors, or a million other things. Cloud software is the same; you might not b
97.
by jbmsf 6y ago
Coming from a software generalist perspective, I found this phrase very familiar: "experienced hands, high coordination, and focused research objectives—are great for answering questions but not for asking them". The best engineer
98.
by jbmsf 6y ago
Because context matters, everyone is going to have different opinions on some (or all) parts of this one. From my experience, I've run into a few challenges with some of the claims For 1: If engineers always operate their code, you wil
99.
by jbmsf 6y ago
I no longer have to implement Kahn's algorithm twice a year!
100.
by jbmsf 6y ago
This is great! Thank you.
101.
by jbmsf 6y ago
At my last company, the system that eventually became our Knowledge Graph started out as RDF. It seemed like a great fit, but we didn't really have much luck. There was an unnecessarily complicated process for schema definition and the
102.
by jbmsf 6y ago
Perfect. Thank you for the reference.
103.
by jbmsf 6y ago
That's not really helpful. Let's assume you have a distributed system; you probably don't want all of your system components connecting directly to TimescaleDB. You also probably want to have some layer that implements queuin
104.
by jbmsf 6y ago
I'd love to hear more about how your data ingestion works. I'm thinking of implementing TimescaleDB myself, but in my initial read of the docs, the focus seemed to be managing the database, not getting data into the database...
105.
by jbmsf 6y ago
One of the reasons duplication is used badly is that it is one of the easiest abstractions to recognize. One of the ways I've seen DRY go horribly wrong involves reusable code units evolving into shared dependencies that often interdep
106.
by jbmsf 6y ago
Always happy to learn about more good ways to use PostgreSQL!
107.
by jbmsf 6y ago
You know you can prefix your ddg search with !g to use Google? Useful for technical searches, where ddg is sadly, not good enough.
108.
by jbmsf 7y ago
As always, it depends. I've seen staged releases work quite well at multiple companies and fail miserably at some others. That said, continuous deployment is the right choice in many/most contexts. I'd just prefer that people
109.
by jbmsf 7y ago
I think you make some assumptions that are context-specific. The decision to always be backwards compatible is just that, a decision. It comes with some really nice benefits around CI/CD, but also adds overhead for certain kinds of dev
110.
by jbmsf 7y ago
Unless I've missed something, it's worse than that: even if you do verify the token, it only lasts for ten minutes, so you are obligated to tie it to some other form of auth unless you want your users to re-authenticate every ten
111.
by jbmsf 7y ago
Location: San Francisco, CA Remote: Yes Willing to relocate: No Technologies: See CV. (Python, Node, AWS) Résumé/CV: https://cv.jessemyers.com/ Email: jesse (dot) myers (at) gmail (dot) com I've been developing pr
112.
by jbmsf 7y ago
There's a brief mention of the load-balancer (nginx) in front of the Go servers; I'm curious if there's anything interesting happening there. I'd imagine that if you lose a server, all of the clients will try to reconnec
113.
by jbmsf 7y ago
I've used Alembic extensively for Python projects and sequelize somewhat less so for Node projects. It's not a huge sample space, but Alembic's design is much better IMO because it can detect and manage conflicts across merge
114.
by jbmsf 7y ago
I like the idea, but it feels a bit heavy handed outside of a very large team. I think the first step here is to get away from the assumption that importing a module will have "interesting" side effects. This is not only a problem
115.
by jbmsf 7y ago
Enough that I don't technically have to work, not so much that I won't keep working.
116.
by jbmsf 7y ago
We had a bizarre experience. Our acquisition was motivated by the value of our contracts and came with a number of earn out goals to ensure that management kept these going for a year. All of the money for the acquisition was held in escrow
117.
by jbmsf 7y ago
Aren't you using a technology to solve a social problem? I don't have the experience with Kubernetes to have an informed opinion, but I've solved plenty of social problems in software organizations. Those are usually approach
118.
by jbmsf 7y ago
I'm definitely guilty of using and promoting anemic models. I find that teams have a hard time deciding whether logic is service or domain or whatever and gravitate towards putting everything in one place if domain objects are allowe
119.
by jbmsf 7y ago
How many companies put thought and effort into defining how they want communication to work? I've seen Slack work when there is both intention to how channels are organized and leadership nudging people to follow these intensions.
120.
by jbmsf 7y ago
There's a lot to unpack here, but I'll focus on #2, specifically the client dependency. My approach is to assign projects to teams with members who can work on both the client and server layers so that the question is less of clie

More ›