This looks like a lot of fun to use, I loved the example from What If, so many units!
This looks like a lot of fun to use, I loved the example from What If, so many units!
Only if it’s specified and documented as part of a contract with the user. If they’re relying on internal implementation details, well that’s a good lesson for them not too do that.
There are some massive intrinsic advantages of the CLI though, that apply for everyone, not just leetcoders:
fzf
and run the exact same command again.So while I agree with you that there’s plently of elitism around the CLI, you do yourself a disservice if you try to avoid it.
Thank fuck! I’m so sick of rebasing and merging Dependabot PRs.
This is a good way to realise that you don’t need a function for that use case.
No, you missed the homeless encampments, forest fires and car centric cities.
There’s no apt install utopia
.
My proudest moment was getting a PR with typo fixes for PyPI docs merged 😂
Gradle is absolute rubbish, definitely the worst experience I’ve had with a build system. But Maven is also rubbish.
IMO a CLI should be the primary way of interacting with the build system (see e.g. Go, Rust, JS with NPM or Yarn, Python with Poetry) and manually editing the build file should be reserved for edge cases and extensions.
Great post! We solve far too many problems (many of them are very much in the nice-to-have category) with our systems at my work, the systems get huge and difficult to change or maintain. I’m on a constant campaign to stop people building things we don’t need, I’m definitely filling my senior role lol.
You fucking heathen! I only use !
IMO an engineer should be able to develop a complex system which an entire company could potentially be based upon.
A developer who isn’t an engineer would focus more on individual libraries, apps or tools that don’t necessarily require the mindset of an engineer to design and maintain.