stepbeek

12 ms·

91.
by stepbeek 5y ago
I don’t believe that Evans was arguing for pulling every concern in the wider system into a single model (the last third of the book gives techniques for overall system architecture). Different service lines, or products, would surely belon
92.
by stepbeek 5y ago
I’ve been impressed with the Disney app. They had a rocky start but now it’s excellent. Definitely better than Amazon’s in my experience.
93.
by stepbeek 5y ago
I very much enjoyed this comment - it sounds like it was a great experience. It’s a nerdier kind of beatnik prose.
94.
by stepbeek 5y ago
Perhaps as a result of incorrectly classifying K8S or K8SaaS as a PaaS when it’s very far from it. Heroku offers the same - or better - devex without the operational burden.
95.
by stepbeek 5y ago
> It's a disservice to persuade businesses to use smaller projects that don't have a comparable level of support, or flexibility. This is why we use Spring. We have confidence that it'll be supported long-term and will con
96.
by stepbeek 5y ago
I found the real challenge to be that it's very difficult - if not impossible - to determine how spring functions simply by reading code and using it. In simpler libraries or frameworks, I normally just read the source to understand ho
97.
by stepbeek 5y ago
> If I change it unsuccessfully, it will break a core part of the system that people are paying for. This is such an underutilized heuristic. I find phrasing the question as “Should we risk having a detrimental impact on customers for a
98.
by stepbeek 5y ago
That’s very fair - I’ve seen the same thing with confluence. Maybe having slack as a suboptimal knowledge store in these situations beats the alternative?
99.
by stepbeek 5y ago
I've found slack to be a pretty poor tool for knowledge sharing like this in comparison to a more document-driven form of communication. We previously used a wiki-tool for this (I don't think it really matters which one), but in r
100.
by stepbeek 5y ago
Killer feature for me was transactional schema changes. We use flyway for db migrations which works fine but a failed migration is left in a half completed state in MySQL - Postgres can execute the migration in a transaction that rolls back
101.
by stepbeek 5y ago
Great write up, but I’m surprised by SvelteKit being described as full stack. It doesn’t seem to offer anything around normal back-end functionality. I’ve normally understood full-stack to refer to a framework like Ruby on Rails.
102.
by stepbeek 5y ago
This made me laugh out loud. Thank you.
103.
by stepbeek 5y ago
> You seem to think masks matter Do they not?
104.
by stepbeek 5y ago
I’m sorry this has happened to you. I’ve had a chronic sickness for three years now and whenever I’m impacted by it I’m met with polite confusion. “Oh, isn’t that over?” I can’t imagine what a lifetime would be like.
105.
by stepbeek 5y ago
I switched from Scala because I found the interior to be so good. Calling Java from kotlin is easy, and - unlike Scalia - the inverse is also true. I’ve converted several projects from Java to kotlin incrementally and it’s been very smooth.
106.
by stepbeek 5y ago
Have you ever tried kotlin? I've found it to be an encoding of best practices from Java with nullability pinned down. Really made me enjoy working in a most OO/procedural language again after fleeing to scala for a few years.
107.
by stepbeek 5y ago
I don't think bitcoin would escape conventional legal definitions of ownership. I wouldn't want to be the one to test it at least.
108.
by stepbeek 5y ago
It’s an amazingly good read. The follow up - The Unicorn Project - wasn’t as good, but definitely worth reading.
109.
by stepbeek 5y ago
> There's a reason why AWS oncalls are infamous whereas Google's are not. Could market share be a significant factor here?
110.
by stepbeek 5y ago
Given the second principle of devops is amplifying feedback loops, I think a more charitable view could be "the common misunderstanding of DevOps has lead to a terrible dev environment". Fwiw, I'm fully onboard with you, but
111.
Spring Framework 6.0 M1 Released(github.com)
1 points by stepbeek 5y ago|0 comments
112.
by stepbeek 5y ago
I’ve found DDD’s insistence that cross-aggregate aggregation be done through IDs to be helpful here. It makes transitioning to other persistence implementations easier.
113.
by stepbeek 5y ago
I explicitly claim to use a "citadel" archicture [0] when talking about breaking off services for very similar reasons. Having a single microservice split out from a monolith is a totally valid application of microservices, but I&
114.
by stepbeek 5y ago
Thanks for sharing! This line made me laugh out loud: "JRuby is known to consume more memory than MRI. You may want to run standard-2x dynos for optimal performance."
115.
by stepbeek 5y ago
I follow the following blogs for front-end. * https://adactio.com * https://piccalil.li/blog/ * https://stephaniewalter.design/ * https://www.baldurbjarnason.com/ This post
116.
by stepbeek 5y ago
I'm in a similar boat to you - I've built non-trivial side projects in other tech stacks, but I'm a JVM developer at heart. I've been conflicted about whether to dig into ruby/rails more to jump ship recently becaus
117.
by stepbeek 5y ago
This sounds dreadful. I don’t think microservices are with talking about with these basics figured out.
118.
Cube CSS(cube.fyi)
2 points by stepbeek 5y ago|0 comments
119.
by stepbeek 5y ago
It’s pretty customizable. I’d argue that changing from default colors, fonts and spacing results in a very different aesthetic. With pico, this is easy to do with a handful of css variables - so you don’t even need a pre/post-processor
120.
by stepbeek 5y ago
I’ve been structuring my styles with CUBE.css ( https://cube.fyi ) for a few months now and a classless approach fits the composition piece very well. Example: In a particular context (say the <h3> tag in the <header>

More ›