TLDR Dev 2024-08-07
OpenAI structured outputs 🤖, spicy parts of Google ruling 🌶, Blue Screen of Death 🔵
Full Text Search over Postgres: Elasticsearch vs. Alternatives (5 minute read)
This article compares different full text search (FTS) options for Postgres databases, focusing on Elasticsearch and Postgres' native FTS. While Postgres FTS is simple and real-time, it lacks features and performs poorly on large datasets. Elasticsearch requires ETL pipelines, leading to data freshness issues and operational overhead. The article introduces and compares alternative search engines like Algolia, Meilisearch, ParadeDB, and Typesense.
Tracking supermarket prices with Playwright (11 minute read)
This article goes through the process of building a website for tracking supermarket prices in Greece. The main challenge was scraping JavaScript-heavy websites, which was solved using Playwright. The scraping pipeline was automated using Concourse CI and ran on a Hetzner server, with the author's old laptop acting as an exit node to avoid IP restrictions.
Does anyone really use angular anymore? (Reddit Thread)
Angular is still used in enterprise-scale applications a lot, such as in banks and government agencies. React is seemingly more popular with startups and scale-ups though.
"20% for tech debt" doesn't work (10 minute read)
Dedicating 20% of engineering capacity to technical debt doesn't work as effectively as it seems. This article highlights five common traps that hinder this approach, such as creating separate backlogs for product and tech, failing to communicate the value of technical work, and diluting focus on specific initiatives. Technical work should be integrated into the product roadmap and clearly demonstrate its business value in order to actually be prioritized.
What's hidden behind "just implementation details" (12 minute read)
The phrase "just implementation details" often underestimates the complexity and difficulty involved in building and deploying software. Designing good software involves challenges like designing a maintainable system, having robustness and observability, and providing a good user experience. The perception that "CRUD" applications are simple is not true since they also require careful database design, production support, and handling of background jobs, user logins, and permissions.
Plunk (GitHub Repo)
Plunk is an open-source email platform built on top of AWS SES. It allows you to easily send emails from your applications.
Fleak (Website)
Fleak is a low-code serverless API Builder for data teams that requires no infrastructure and allows you to embed API endpoints to your existing modern AI & Data tech stack.
Introducing Structured Outputs in the API (28 minute read)
OpenAI has introduced Structured Outputs in its API, allowing developers to have model-generated outputs adhere to provided JSON schemas. This guarantees output consistency and format compliance. It's available in the API today.
All the spiciest parts of the Google antitrust ruling (10 minute read)
The US v. Google antitrust ruling revealed that Apple considers Bing an inferior search engine and wouldn't switch to it, even for a huge payment. The judge declared that TikTok and other social media platforms are not competitors to Google Search because they lack the ability to index the entire web. The ruling further stated that AI search technology is not yet advanced enough to replace traditional search engine methods - this was used to justify the final call that Google is a monopoly.
Can we trust Microsoft with Open Source? (10 minute read)
There was a controversy surrounding Microsoft's commitment to open-source development, specifically regarding the .NET framework. Microsoft was seemingly starting to shift away from open-source practices by removing features like "Hot Reload" from the .NET SDK and making them exclusive to Visual Studio. However, the community's strong reaction to this prompted Microsoft to reverse its decision and bring back Hot Reload as an open-source feature.
There is no mystery over who wrote the Blue Screen of Death, despite what some may want you to believe (3 minute read)
The Blue Screen of Death, a notorious part of Microsoft's history, has a clear authorship for each of its iterations. Steve Ballmer is credited with the text of the error message in Windows 3.1, which was not a true "blue screen of death" as it displayed a black screen with an error message. The Windows 95 kernel error was actually brought to its final form by Raymond Chen. John Vert is the author of the true "blue screen of death" associated with Windows NT.
The most important software engineering news in one daily email
Join 450,000 readers for
one daily email