Feels like this is missing some of the key points of using generic bucket storage for me:
1. Archive pricing for really large old documents.
2. Cross-provider backups; especially for critical documents.
How much did they end up costing? We do a similar PCB medallion every year for another event and haven't been able to get quite that fancy due to cost. We usually only manage to get some LEDs and a processor in our lower budget range.
The total ended up being about $10/badge for 60 (5 for badge, 5 for eink), and we made the mistake of not ordering enough, so we ordered a couple more that were about $1 more expensive each. We bought all the badges from JLC and the prod files are in the repo if you want to see how much they come to in higher order quantity!
We've been doing this with simple mkdocs for ages. My experience is that rendering the markdown to feel like public docs is important for getting humans to review and take it seriously. Otherwise it goes stale as soon as one dev on the project doesn't care.
I went through a similar transition. Used to spend hours in dark table each shoot, but for a hobby it got tedious. Eventually I got my in-camera configuration right enough and haven't touched a raw in months. I'll still sort and crop; but no need to fiddle with things the camera is good enough at already.
I was afraid that no one would bring this up. I’m developing a strange relationship with Wikipedia over the commonplace role it serves as an online resource. But I appreciate how it normalized the practice of looking things up and to get a general overview of a thing, leading to internal and external references. Credit is due to search engines also in this case I reckon.
I think that's sort of what I got from the article - open the right tools for what you're actually working on, not everything you might need for all the tasks in your backlog.
I actually agree that the code is one of the most important things to get right at a software company. Still. I would argue very few companies win on code merit alone either though. Strategy, customer communication, market timing, etc on the business side; design, system architecture, dev velocity on the technical side. So many factors are important beyond the quality of the code.
reply