Pretty sure they meant to not have review. Dropping peer review in favor of pair programming is a trendy idea these days. Heh, you might call it "pairs over peers". I don't agree with it, though. Pair programming is great, but two people, heads together, can easily get on a wavelength and miss the same things. It's always valuable to have people who have never seen the new changes take a look. Also, peer review helps keep the whole team up to date on their knowledge of the code base, a seriously underrated benefit. But I will concede that trading peer review for pair programming is less wrong than giving up version control. Still wrong, but a lot less wrong.
docAvid
joined 1 year ago
Or gets promoted, and keeps moving on to new and bigger projects, leaving a trail of destruction, because all management sees is they close tickets faster than the people who are busy picking up the pieces behind them.
Emacs Magit is so much better than the CLI, and I don't say that lightly. And it's available on Linux.
I barely know Vim, I'm an Emacs guy. Every time I pair with a colleague using an IDE, I find myself having to exercise great restraint, and not complain about how slow and fussy everything they do is. When I've worked with skilled vimmers, I have to admit that they invoke the deep magic nearly as efficiently as I do. Hotkeys? Pshaw, child's play.
Saying that some projects, at some point in their lifecycle, don't need certain things, is not saying that those things have no place. Also, if one can't design a monolith that isn't bloated and tightly coupled, one definitely has no business designing microservices. Using microservices is neither necessary, nor sufficient to achieve decoupling.
Monolithic services are the ideal way to begin a project, as using basic good practices, we can build a service that does many things with minimal coordination, and as it grows and requirements change or are discovered, we can easily refactor to keep things simple. As the software matures, we find the natural service boundaries, and find that certain pieces would perform better if they were separated out and could scale independently, or act asynchronously. Since we have followed good practices, this should usually be a simple matter of removing a class or module to a new service, and replacing it with a facade, such that the rest of the monolith doesn't have to change at all.
I do rather like science.
I think Vim is more popular with sysadmins because, historically, you could count on Vi or Vim being available on just about any server you had to do some work on, while Emacs might not be. That's still probably somewhat true, although in the world of clouds, containers, and source-controlled, reproducible configuration, it's probably less common to edit files in place on a server.
However, with Emacs tramp, you can edit files just about anywhere you can access, by any means, even if there is no editor installed there at all, using your local Emacs, with all your accustomed configuration. Like popping open a file inside a container running on a remote server by ssh, something I've done a lot of lately, debugging services running on AWS ECS.
Just use a single instance of Emacs to edit everything everywhere all at once. You can even use vim keybindings if you have no taste.
Fucking apeshit craze-balls, makes sense, business as usual.
Medication helps a lot of people, and CBT is very effective for others. I've never heard of a "technique" that's effective against depression that can be reasonably described like that, but I'm not an expert. Would love some concrete examples.
Programming is the art of juggling of state and control flow
Sure, stateless functions deal with and impact state in some way. If that's what you meant by your previous comment, that's fine, but that's honestly not what would typically be meant by "juggling" state.
The part about declarative languages has nothing to do with state. Declarative languages do not give the programmer control over flow, the other part of your definition.
Learn Lisp, and you will never again be so certain about the difference between a programming language and a data format.
Exactly. Dependency injection is good; if you need a framework to do it, you're probably doing it wrong; if your framework is too magical, you're probably not even doing it at all anymore.