/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 blog.risingstack.com
How to Debug Node.js with the Best Tools Available - RisingStack Engineering
| | michaelscodingspot.com
All the Possible Ways to Debug Node.js | Michael's Coding Spot
0.8 parsecs away

Travel
| | Michael Shpilt's Blog on .NET software development, C#, performance, debugging, and programming productivity
| | risingstack.com
JavaScript Engineer Wanted - RisingStack Engineering
1.8 parsecs away

Travel
| | Our goal is to build a highly capable, battle-tested full-stack engineering team who can deliver anytime. Join us!
| | nodogmablog.bryanhogan.net
Debugging an AWS Lambda Function Locally with Visual Studio Code (VS Code) on Windows, Linux, and Mac | no dogma blog
2.7 parsecs away

Travel
| | It is easy to debug an AWS Lambda function locally with Visual Studio Code, all you need to do is install one tool and make one change to the launch.json file. Read on to see how.
| | jmmv.dev
Picking glibc versions at runtime - Julio Merino (jmmv.dev)
12.6 parsecs away

Travel
| In a recent work discussion, I came across an argument that didn't sound quite right. The claim was that we needed to set up containers in our developer machines in order to run tests against a modern glibc. The justifications were that using LD_LIBRARY_PATH to load a different glibc didn't work and statically linking glibc wasn't possible either. But... running a program against a version of glibc that's different from the one installed on the system seems like a pretty standard requirement, doesn't it?...