2 ms·
You are massively oversimplifying "classic SWE" here. Ultimately it makes no difference. How you handle contract violations between dependencies and third part
by xyzzy_plugh 3y ago
You are massively oversimplifying "classic SWE" here. Ultimately it makes no difference.
How you handle contract violations between dependencies and third parties is not an inherently different problem. What should you do if a data source changes schema? How do you detect it, alert, take action? How are users or customers or consumer jobs impacted? This is all just normal software.
In many ways it feels like you're making my case for me.
- fifilura 3y agoWhenever I get confronted with SWE best practices it is all about version control, unit tests, integration tests and CI/CD. What are some good resources for the other things you describe?
- jimberlage 3y agoI don’t have great links handy, but read up on observability. You’ll want to read up on what people do on error, especially in the case that contracts change (search “api versioning”.)
- fifilura 3y agoThank you! It may be that those topics are part of the SWE process but not generally applicable for example UI work and therefore overlooked. But it may also be something else. That a process can create Grafana dashboards and processes for API updates like a pro. But only the person that really cares about the data and know it from inside out can catch the "unknown unknowns". And for that you need to give access (and hand over responsibilities) to Analyst persons too and in some ways trust them too, even though they may not have as rigorous processes.