↓ Skip to main content

·98 words

People want local development but I feel a lot of the reasons and movements described here are valid.

https://dx.tips/the-end-of-localhost

When I try to unpack it, it’s usually not even very clear what ’local development’ means but I think it’s something along the lines of: 1. Being able to manipulate the system under development immediately using the command-line. 2. Not being able to break an unrelated system and not having somebody else break your development environment. I get that those two things are essential but there’s nothing in them that requires them to take place on your physical laptop.

Alper Cugun
Author
Alper Cugun

Related

A short guide of how a team can turn around the work they need to do on a legacy system and come out the better for it. I’ve seen lots of teams struggle with this but as described here a lot of it is in the approach and the praxis of doing it and working together.

·31 words
A lot of very uncomfortable questions in this list of staff engineering program dysfunctions. It seems this is quite widespread and we’re collectively figuring out how to shape this path.

Highlights for Domain Driven Design

·973 words
Good programmers will naturally start to abstract and develop a model that can do more work. But when this happens only in a technical setting, without collaboration with domain experts, the concepts are naive. That shallowness of knowledge produces software that does a basic job but lacks a deep connection to the domain expert’s way of thinking.