• 2 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle







  • I think I’ve learned to get less attached to opinionated terminology in code and database design because I see it happen all the time where the usage of the value/field/thing can evolve naturally over time as the business needs evolve. And refactoring field names (as an example) from UI to database is often a painful exercise, not without significant regression risks. (Depending on the size and complexity of your systems, of course)

    So while I totally agree with you and others that ideally naming would be consistent throughout, my real world experience with the issue has taught me that this isn’t the hill I die on.

    My 2 cents from 10 years experience in the industry.





  • Oh awesome! That’s great to hear! I’m experimenting with the idea of offloading this to an off-device process so that all users can have consistent results regardless of their devices. Unfortunately, that cloud infrastructure is already costing me a decent amount of money… So gotta figure out how to solve that problem as well (without annoying users too much with cost or ads)









  • Couldn’t agree more. We used Crucible as a code reviewing tool, which allowed us to develop directly on main while being able to pick-and-choose commits to add to a review. This closed that CI gap for us in a meaningful way.

    However, Crucible seems to be reaching end of life (my company even denied renewal of licenses for it). So now we’re forced back into Gitflow, and it’s sooooo painful.