The issue with nitpicks: different reviewers have different definitions of what a "nit" is.
595 karma · joined March 28, 2010
The issue with nitpicks: different reviewers have different definitions of what a "nit" is.
It looks like that doc https://docs.gitlab.com/development/wikis/ was outdated - since fixed to no longer mention Gollum.
It is fantastically long, but still fascinating !
An LLM is more like outsourcing to a consultancy. Results may vary.
It's more the en-shittification of the Internet, and other media.
1. "Write everything down" culture.
2. Rotate the regular meetings. For example, a meeting around 1000 UTC for Europe / Asia folks on Monday. Repeat the same meeting at 2000 UTC for US / Asia folks.
3. Write good notes for each meeting, so people who could not attend can review asynchronously.
2x meetings may not work for a truly distributed team where you have people all over the world. In which you will need to have 3x rotating meetings which becomes a bit harder to manage.DST changes do happen every six months, or so. We mostly roll with it, and adjust the meeting times as necessary.
99% of the time, no one on the proverbial soccer field honestly cares about your family setup - they are more worried about what's for dinner.
Cars cost around X * $10,000 each. Houses cost Y * $100,000 each. The author is ignoring the economics of producing real world goods.
But there are real-world repercussions of just plain bad working practices
* https://www.abc.net.au/news/2023-03-27/whats-happening-with-...
It's not as bad as a bridge falling down, but this is why there's professional bodies and code of ethics in certain professions.
See also Andor episode 8 (spoilers so I won't post exact details) ;)
If necessary, as others have alluded to, a global timer is best.
If you peek into the source code, I was actually inspired by the ruby-warning gem, and have directly credited it (https://gitlab.com/search?group_id=9970&project_id=278964&re...) :)
Also in Ruby 2.7.2, these warnings that were introduced in 2.7.0 were suppressed by default after feedback from the community.
One thing to note is that because these warnings are runtime, you really need a very comprehensive test suite to find them all. Even then logging such warnings when running in production is probably a good idea.
Agree the Ruby 2.7 => 3.0 change has been handled quite well by the core Ruby team. The kwargs warning is one part of the larger effort to get GitLab onto Ruby 3.0. You can follow along at https://gitlab.com/groups/gitlab-org/-/epics/5149.
Perhaps a bit too much hyperbole, but lots of industries have these cycles of increasing complexity. The necessity of such complexity is in the eye of the beholder.
- Agriculture. Herbicide -> GM plants to resist herbicides
- Automobiles. Manual -> Auto
- Finance. HFT anyone ?
- Construction.
- Medicine.
- Accounting. GAAP
- and finally... Quantum Physics !Enjoy, here's a stackful of documents showing https://covid19.govt.nz/updates-and-resources/legislation-an... how a robust health response works.
Ouch number 5 in NZ is a Credit card payment gateway