"As a rule of thumb, if you’re doing the agile thing where you word tasks as user stories, and the user in the story is, well, an actual user — you’re probably a product engineer. If the story is about a developer in your company, that’s a good sign you’re a platform engineer."
So how did developers work in the 1990s? Angel Rivera describes how he got introduced to DevOps before the term was popular.
Gergely Orosz has had his fair share in designing and building large systems. None of them used the standard software architecture planning tools like UML, there were no architects on the teams that owned the design, nor references to the common architecture patterns.
"Searching for code to reuse, call into, or to see how others handle a problem is one of the most common tasks in a software developer’s day. However, search engines for code are often frustrating."" GitHub undertakes a huge project. Tons of comments on HN.
"If we can fail the tests on our machine, we will surely improve our workflow rather than having the test failing on the CI environment, with all the side implications (fixing the test on our machine, testing, re-pushing, running CI)".