Articles from sprkl.dev

Articles from sprkl.dev

Flat companies conflated the idea of “Full Stack” to mean “everything and the kitchen sink” when it was originally intended to mean Javascript frontend and backend using Node.js. (sprkl.dev)
2023-3-14 JavaScript Full Stack

Couldn't agree more with this guy: Don't let the QA department run tests except for sanity checks or extreme corner cases. They should only look at test results, approve/block releases, and add tests to the existing test suites. (sprkl.dev)
2023-2-28

I couldn't agree more: a single engineering team doesn't need a team lead, a PM, an engineering manager, a technical program manager, a scrum master, and a product owner. After a while, it can look like those photos of 6 construction workers standing around waiting for the guy with the shovel! (sprkl.dev)
2023-2-16 Scrum

A demonstration on how to implement an observability stack based on Jaeger and OpenTelemetry in node.js services and how to debug simple issues in a microservice distributed environment. (sprkl.dev)
2023-2-16 Node.js Microservice

Get diff observability summary for your Pull Requests ready for code review (sprkl.dev)
2023-2-7

"I don't like debuggers. Never have, probably never will" Linus Torvalds. How much time do you spend on debugging? (sprkl.dev)
2023-2-1

A major difference between Amazon from other orgs I worked at is that Amazon likes writing docs. People write documents for everything. Every design decision & meeting has an engineer write a doc. We spend 15 mins in a meeting discussing the doc & making decisions. Holy, I'd probably kill myself (sprkl.dev)
2023-1-31 Amazon

I've been fixing bugs for 6 months now, and I don't know how much longer I can just keep fixing bugs. I asked if new projects are coming in and have asked about carving out time to create the test suite. My manager told me that we need to improve the quality of the code and that means fixing bugs. (sprkl.dev)
2023-1-29

The developer observability tool I'm familiar with - gonna choose not to name and shame because, from what I can tell, this is a common problem; it lacks intuitive ways to surface the information. You can probably guess what it is. Agree? (sprkl.dev)
2023-1-26 Programmer

A bunch of devs work on different areas of the code but it doesn't matter to the APM, I can push code to one microservice and my colleague to another, and yet when we log into the APM, we get the same view. How do guys deal with this problem when working on a huge codebase? (sprkl.dev)
2023-1-9 Microservice Push

I couldn't agree more: a single engineering team doesn't need a team lead, a PM, an engineering manager, a technical program manager, a scrum master, and a product owner. After a while, it can look like those photos of 6 construction workers standing around waiting for the guy with the shovel! (sprkl.dev)
2022-12-21 Scrum

Top VSCode extensions for developers in 2022 (sprkl.dev)
2022-12-18 Programmer

Quality code: Node.js design patterns and dependency management (sprkl.dev)
2022-11-30

I agree with avoiding the "Too many cooks in the kitchen" syndrome with lots of opinionated senior folks. How many junior devs are on your team? (sprkl.dev)
2022-11-14

Performance: Rust and its relationship with Node.js (sprkl.dev)
2022-11-6 Rust

Previous Page Next Page