Recently, I started learning C development and the various build tools and IDEs available for that. I'm not sure which I find more annoying: trying to learn vim bindings, or trying to ignore the fake squigglies in VS Code.
FluentAssertions is switching to a paid license in v8. I just got my team using it, and change does not come easy to us. I get that developers need to support themselves, but $130/dev/year is really steep. I don't want to rewrite all of my tests, but I can't justify that cost.
@davidfowl We're using C# for transaction processing. I'd hate to see that go down for even a minute or misplace a decimal point. I suspect a lot of finance is built on .NET.
@walkingriver It's been a while since I've worked with Linux. My team is entirely Windows, and it largely needs no configuration. However, Linux is far more customizable, especially for always-on servers. Finding that perfect customization will be a long dark rabbit hole
@walkingriver If most of the information is required, could you default to "required" and mark the rest with "optional: true"? Though I'll note that "required: true" is much more common in Swagger, JSON Schema, and other contract languages
To be clear, I have nothing against these rules. They would make my reviews much more meaningful. But is it going too far if a company required and enforced the use of these labels in all PR comments?
Just learned some great advice and resources for writing better pull request reviews (as both author and reviewer) @VSLive. The following rules help reviewers focus and stay objective, but are they too structured for a human team?
https://t.co/xIzxVL3eNs
βMusic notation should be as accessible and as fluid as text is, on the web; that it is not, yet, is something of an afront to my sensibilities. Let us fix this pressing problem.β https://t.co/Pj0KpYl2Ew
@jamesqquick Multiple times, I have created a short script in pure JS because it was a quick one-off calculation. Each time, I've switched back to TS in less than 10 minutes.
At multiple companies, with multiple CI/CD products, I've hit the 260 character path limit imposed by Windows. Each time, it has taken me multiple days to diagnose and fix. Why do I have to relearn this lesson every year?