A lot of spicy quotes I could steal.
I’m going to ask ChatGPT how to prepare a garotte and then I am going to strangle you with it, and you will simply have to pray that I roll the 10% chance that it freaks out and tells me that a garotte should consist entirely of paper mache and malice.
You have to adopt Emacs and show her that she can even play Tetris on it.
I used to have a cheap mechanical keyboard that has side rainbow RGB panels that can’t be turned off. I thought that would be turned off when I turn off the backlight. Nope.
I guess it’s things like AWS Elasticahe that made them want to provide their own service without sharing the code with their soon to be competitors.
Wait. It’s that long?
Felt like we joke about the announcement 2 years ago. Time fly lol
Guess, it’s to make your code look hand crafted and not copied from Chat GPT or SO for some take home assignment.
I could notice the slowness of Atom when I compared it to VS Code. Sublime is also noticeably faster than VS Code, but the gap doesn’t feel so wide that I want to jump the ship.
I think it depends on the number of characters in the file that make the difference more noticeable.
My wife gossip about me with her boyfriend.
Joke’s on me. 100% wfh, but hours of zoom meeting a week.
They start a paywall if an author wants to monetize their work, which is fine. It’s not Medium’s fault as authors are the ones who decide to monetize their articles or not.
Yup. Have to ensure that you use “no” if you don’t want yaml to equate it to false.
Reading the 3rd paragraph and I see myself 😄. Glad that you and the team managed to add another layer of testing successfully.
You run E2E test before each merge. So, you don’t merge very often?
How about running an integration test before each merge instead of a full fledged E2E and mocking out external dependencies (other services) during the test, then do E2E testing on a schedule like nightly?
I prefer it this way, because mocking out external dependencies cut out network instability and bugginess from dependencies. So, we can merge faster. Agree that test scenarios are overlapping, and if your E2E is very stable then it is probably not worth it, but unfortunately it’s not so stable in my environment.
I learned about this page from The primetime and I mostly agree with the Grog especially on software testing. It’s funny that it came up when I was adding integration testing to our project that’s relying only on unit test with 0 integration testing. So many mocks are required and changing any behavior, while wishing that you don’t forget to update every mock is a wishful thinking.
I learned the hard way that no is false in yaml. Took us a while to realize why our app failed to start in Norway. Too many ways to do something.
How about prefixing your commit with a ticket number?
If a commit message has too much information, then the commit has too much changes
True that. Coming from Windows, I really don’t understand why this feature isn’t built into Mac. Most Linux distros have this feature.
Windows snapping. I use Spectable. It’s a free open sourced software.
It’s still a hot mess. Helped my wife set it up for developing a Java webapp with Tomcat and it’s such a mess to set up, compared to IntelliJ that I could just set up a Springboot easily.