|
Friday 15th September’s issue is presented by Flatfile |
 |
Turn “Flat” Files Into API-Ready Data
Flatfile’s Data Exchange Platform allows developers to build customizable data file import workflows that meet any requirement, using code to drive data logic, without having to build or maintain the underlying plumbing yourself - win win.
Take advantage of AI data matching, faster validation & cleaning, and human-in-the-loop data review, all while maintaining enterprise-grade scale and security. |
|
|
4 Engineering Slides CEOs Love
tl;dr: The article shows the layout of four key slides, designed for an audience of non-engineering CEOs, presenting: (1) Overall Health Update - Snapshot of the team's production pipeline, efficiency, and developer experience compared to industry benchmarks. (2) Engineering Investment Strategy - Impact and execution health of ongoing projects, guiding resource allocation decisions. (3) Engineering Investment Updates - Highlights key project investments, detailing headcount, budget, business impact, and execution scores. (4) Engineering Health Update - Review of engineering metrics related to operational stability and bug tracking.
Leadership Management |
 |
|
The Ultimate Guide To Developer Counter-Productivity — John Cutler
tl;dr: John highlights 20+ specific areas where developers often lose productivity, including: (1) Reactive, unplanned work. (2) Context switching and startup costs. (3) Non-value-adding admin & compliance work. (5) Ineffective planning. (6) Dependency management overhead. (7) Ineffective meetings and communication. (8) Redundant manager briefing & orientation. (9) Consensus seeking and decision-making drag. (10) Ineffective collaboration arrangements. And more.
Management Productivity Antipattern |
|
|
CSV Import Solutions: A Build Vs Buy Analysis
tl;dr: Deciding between building or buying a CSV import tool? We surveyed companies on their top considerations when building or evaluating a data import solution, and put together an analysis to help you make the best decision for your team. Get the guide.
Promoted by Flatfile
Guide Management |
|
|
7 Simple Habits Of The Top 1% Of Engineers — Leonardo Creed
tl;dr: 1) Use consistent standards - adhering to a uniform coding style for readability and scalability. 2) Write aesthetic, simple code - producing clean, organized, and logical code that's easy to understand. 3) Don't allow surprises - ensuring code predictability through adherence to principles and thorough testing. 4) Communicate often - actively seeking feedback and collaborating for better end results. 5) Detach from the code itself - viewing code objectively, open to revisions for the best outcome. 6) Code fast... and slow - taking a deliberate approach to coding, ensuring quality over speed. 7) Code for the human, not the computer - writing code that's comprehensible to humans, emphasizing its value to both developers and users. CareerAdvice |
|
|
|
"There's nothing more permanent than a temporary hack."
- Kyle Simpson |
|
|
A Systematic Approach To Debugging — Nicole Tietz-Sokolskaya
tl;dr: Nicole’s process involves six steps, each of which she expands on: (1) Identifying the symptoms. (2) Reproducing the bug. (3) Understanding the systems. (4) Forming a hypothesis about the bug's location. Instead of randomly searching through the code, the author suggests forming a hypothesis about where the bug might be located. This narrows down the search and makes the debugging process more efficient. (5) Testing the hypothesis. (6) Fixing the bug. "If you don't understand the bug behavior, you have no hope of knowing if you've fixed it or not."
Debugging |
|
|
Build And Keep Your Context Window — Vicki Boykis
tl;dr: “When humans have no external context as guardrails, we end up recreating what’s already been done or, on the other hand, throwing away things that work and glomming onto hype without substance. This is a real problem in production data systems. In order to do this, we need to understand how to build one.” Vicki believes that we must understand the historical context of our engineering decisions if we are to be successful in this brave new LLM world.
ThoughtPiece LLM |
|
|
UK Air Traffic Control Meltdown — James Haydon
tl;dr: During a routine deployment, NATS, a major UK-based air traffic management company, experienced a significant system disruption. This "meltdown" led to widespread operational challenges. The root cause was identified as a misconfiguration introduced during the deployment. James dives into root causes of the issues that caused 1,000 flights to be cancelled. DeepDive |
|
|
Building A ShopifyQL Code Editor — Trevor Harmon
tl;dr: “This approach enabled us to provide ShopifyQL features to CodeMirror while continuing to maintain a grammar that serves both client and server. The custom adapter we created allows us to pass a ShopifyQL query to the language server, adapt the response, and return a Lezer parse tree to CodeMirror, making it possible to provide features like syntax highlighting, code completion, linting, and tooltips. Because our solution utilizes CodeMirror’s internal parse tree, we are able to make better decisions in the code and craft a stronger editing experience. The ShopifyQL code editor helps merchants write ShopifyQL and get access to their data in new and delightful ways.”
Scale DeepDive |
|
|
Awesome Bun: Curated list of awesome things related to Bun.
LotusDB: Extremely fast key-value store.
Pagefind: Static low-bandwidth search at scale.
Tldraw: Collaborative digital whiteboard.
Vale: A markup-aware linter for prose.
|
|
Click the below and shoot me an email!
1 = Didn't enjoy it all // 5 = Really enjoyed it
1 … 2 … 3 … 4 … 5 |
|
|
|