tl;dr in tech - Issue #91

How LinkedIn Adopted A GraphQL Architecture For Product Development#

By: Arun Sethuramalingam

tl;dr: LinkedIn has gone full GraphQL, folks. No half measures here. In their blog, they dig deep into the architectural choices unique to them and why they made those choices. In Arun’s words, “In this blog post, we will cover how the GraphQL layer is architected for use by our internal engineers to build member and customer facing applications.” Useful insight for those of us wrangling API’s and data.

Contrafreeloading#

By: Mike Fish

tl;dr: Not just for the birds, “contrafreeloading” is about working for rewards and taking pride in it. Mike underscores the importance of having “something to do, someone to love, and something to hope for” in your career. As software engineers, we’ve got the “something to do” part covered… multiple times over. 😅

A Beginner’s Guide To Prompt Engineering With GitHub Copilot#

By: Rizel Scarlett

tl;dr: Struggling to get the most out of GitHub Copilot? Rizel’s been there. She improved her communication with the tool by providing context, examples, and clear instructions, and in her post, she spills the beans on how to do it too. “After more experimentation, I improved my communication methods with GitHub Copilot.” Must-read for those in the copilot’s seat. 👨‍✈️👩‍✈️

Rules Of Thumb For Software Development Estimations#

By: Vadim Kravcenko

tl;dr: Vadim shares his wisdom on the ‘dark art’ of project estimations. He might not be a know-it-all, but he does share some handy rules of thumb that could make your life easier. He says, “Who am I to tell you how to estimate projects? I can only give you some pointers…” Estimations may always be a shot in the dark, but Vadim gives us a flashlight.

How To Survive Your Project’s First 100,000 Lines#

By: Evan Ovadia

tl;dr: Evan takes us on a journey through 100,000 lines of code and how his project didn’t collapse under the weight. He credits techniques from his time at Google and game development. He says, “Some of these software engineering techniques came from my time at Google, though ironically most came from my work on the Vale compiler and game development.” This is a survival guide every budding engineer needs. 🏕️

That’s all for this week, folks! Keep on coding and remember - the best error message is the one you never see.

Catch you on the flippity flip!