Pro tip, if this happens to you split your tickets up into smaller chunks! It has two effects:
One is that you will see progress from one sprint to the next, even if it’s 1 story point at a time.
It also has a psychological effect! If you’re like me you will avoid the huge, nebulous tasks. But if it’s something manageable with a defined start and end, you will do it. You could probably even schedule it.
Rabbits engage in coprophagy to extract more nutrients using their short digestive tracts. Is this analogous to training ML models on AI-generated output?
A manager position is easier to replace than a programmer position. By the time AI is smart enough to replace you, it is also smart enough for you to replace the entire company with and run solo.
A robot won’t replace individual programmers. AI and improved processes will mean quicker code review and less programmers needed. There will be a net loss of programmer jobs but an individual programmer won’t be replaced. Rather the remaining programmers create more (as a percent, not absolute) code with better tools.
Yes. But its by attrition. There won’t be a programmer replaced by AI directly. Their colleagues will take over their work and have higher workloads but be more efficient. That’s ways been the way.
“Only when the last tree has died and the last river been poisoned and the last fish been caught will we realize we cannot eat a machine learning algorithm.” - traditional Native American saying.
Idk why exactly but using IDs for styling has been discouraged for a while and now every application I’ve ever worked on had been styled using classes that are usually unique anyway
In E2E tests you should ideally be finding elements using labels or ARIA roles. The point of an E2E test is to use the app in the same way a user would, and users don’t look for elements by class name or ID, and definitely not by data-testid.
The more your test deviates from how real users use the system, the more likely it is that the test will break even though the actual user experience is fine, or vice versa.
This is encouraged by Testing Library and related libraries like React Testing Library. Those are for unit and integration tests though, not E2E tests. I’m not as familiar with the popular E2E testing frameworks these days (we use an internally developed one at work).
programmerhumor
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.