(I don't recall _loving_ it, though I don't have as many bad memories of it as I do for VSTS/TFS, GitLab, GH Actions, Jenkins Groovyfiles, ...)
1,183 karma · joined October 9, 2011
(I don't recall _loving_ it, though I don't have as many bad memories of it as I do for VSTS/TFS, GitLab, GH Actions, Jenkins Groovyfiles, ...)
You'll have to explain the weird CPS transformations, you'll probably end up reading the Jenkins plugins' code, and there's nothing fun down this path.
Berkeley instead offered this alternative solution, because they did not want to pay.
(I also struggled with the schema because crime_scene was singular and suspects was plural!)
It sounded to me like a list of "friends who want to get more involved, I'll let you know who to avoid". Then, I read the interactions that sparked that post, and I could totally understand the frustration from OP's part.
Linus being unwilling to take a real stand on maintainers blocking Rust just because doesn't really help.
(Though, this is more general than uv for Python script deps: https://packaging.python.org/en/latest/specifications/inline...)
The others do sound useful too -- I personally hit a lot of spurious "tab output indicator" notifications in iTerm2, but if it _did_ work I could see how giving it up would be painful.
A real shame, I think Bazel's lack of good IDE options definitely hampers its adoption.
This motivation is pretty clearly stated in the article.
Some people use "fancy TUIs" (the famous editors vim and emacs surely count) and if you don't, feel free to ignore this new option.
Sometimes the "add the missing tests" step depends on other work on your branch.
Is there a Vimcasts equivalent for learning the AI editor tips and tricks?
The VS Code team has kept some APIs in this "preview" mode for many many years. https://github.com/microsoft/vscode/issues/59921 is just one example, which has been requested since early 2018!
I wish it were less destructible! I upgraded to a Paperwhite (2021) when the Voyage's power button broke. Water resistance is nice, but having to get the "signature" edition for a light sensor and an easily scratched plastic display is quite disappointing.
Is this a poor Calibre configuration or are there real limitations to reading books side-loaded on Kindles?
For a Go service? Sure, that's easy and makes a ton of sense.
I think this might be a typo - we're observing X but want Y, or some similar variation. In any case, there's a bug.
Is this hypothetical guy always writing 100% correct code?
Could you say more about this? Were they technical or behavioral interviews?