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.
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.
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.
How about prefixing your commit with a ticket number?
If a commit message has too much information, then the commit has too much changes
Oops, my bad. I confused moonlight with moonshine. Guess my spirit was a little too strong.
How many moonlights did you see?
But how does your team collect works as a reference or whatever? Like just upload then to the cloud or something?
There are places that hire developers, but don’t use a version control? I’m so shock at this.
For agile thing. I would ask them to describe how they do agile also. You can have a waterfall that called agile as well. Or Agile that estimate ticket with time instead of complexity.
So, the history table have every column, but the user table has only user id and version, right?
user_history table user table
How do you update it to unoublish? Add another timestamp column and who’s the latest win or just set published_at to null?
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.