Have you ever wondered what exactly is in a nuget to see if it’s right for you? You read the description, you like the name, but, if you’re like me, you probably ended up in GitHub reading the source code to decide if you want to use the library.
This announced last week but after I posted last week round up. What a straight awesome idea. Incredible.
Hi, I’m Nat Friedman, future CEO of GitHub (when the deal closes at the end of the year). I’m here to answer your questions about the planned acquisition, and Microsoft’s work with developers and open source. Ask me anything
After the big announcement on Monday of Microsoft acquiring GitHub, it’s pretty interesting to read some of the Q&A.
Eric Lippert (@ericlippert) and Gor Nishanov (@GorNishanov) discuss C++ co-routines, probabilistic programming, undefined behavior, and more. Eric Lippert was the first dev interviewee on @Ch9. In fact, it was his interview that really made us believe that we were on to something with unscripted conversations in video format… Great to see Eric again! He still has the boyish looks and sly grin. Amazing, the things he and team are working on, which should have impact across the industry. Gor loves C++ and he is quite the personality. His co-routine design is on the path to standardization in C++20. We (Service Fabric team) use his current implementation in many places, including code that runs in the Windows kernel. We love co-routines!. We must get him to spend more time on camera and share his passionate insights.
Pretty interesting listening to the gripes about Node and interesting to see the prototype project Deno with TypeScript.
You’ve spent months re-architecting your monolith into the new microservices vision. Everyone gathers around to flip the switch. You navigate to the first page…and nothing happens. Refresh…still nothing. The site is so slow, it won’t respond for minutes. What happened? In this session, I’ll walk through a post-mortem of a real-life microservice disaster. I’ll show the modeling, development and production problems we found, and how we slowly morphed the new distributed monolith into our final picture of sanity. While we can’t prevent project failures, we can at least identify problems early on in our design so that our final product results in a clean, robust distributed system.