3 ms·
Startups have limited resources, we prioritize the best we can. As a staff engineer it's my responsibility to bring this to my company, but it's not an overnigh
by RSHEPP 2mo ago
Startups have limited resources, we prioritize the best we can. As a staff engineer it's my responsibility to bring this to my company, but it's not an overnight process.
- soperj 2mo agowhy wouldn't you use those limited resources to test things before they go to production, instead of creating more crappy things that go to production?
- rhdunn 2mo agoWhat do you test? How much time/effort do you spend testing each of those things? How do you know those will be performance issues? There's only so much you can do -- making reasonable assumptions, choosing suitable data structures, database indices, testing various workloads, etc. -- in a limited test environment. You may spend a week optimizing a feature that only 10 people use or that never gets to the point where it becomes an issue. Or you may have something that can't easily be tested at scale, such as various counts or other dynamic data that are determined by complex queries that you may (likely) find you need to cache but don't necessarily know which values will become issues until you start using the system.
- soperj 2mo agoWe have a test team that runs various test suites(automated) and manual testers that test functionality. They spend their entire working day, every day testing.
- fn-mote 2mo agoFrom this argument, it sounds like your company is making a rational choice to go with what you’re seeing. Even if you don’t like it.