Loading…
Remote Work
7 posts about Remote Work. Every summary links to the original.
The 2026 Developer Survey is now open (for human developers only)!
The 2026 Developer Survey is open to gather data on software builders' tools, working lives, and emerging practices. Marking fifteen years since its initial 2011 release, the annual survey focuses heavily on the role of artificial intelligence and autonomous agents across the software development lifecycle. Past survey results indicated that while developer adoption of AI and agents doubled, user trust declined alongside escalating concerns regarding generated code quality. In addition to modern AI trends and financial return considerations, the questionnaire maintains traditional inquiries regarding day-to-day technologies and developer workflows. The survey is hosted on the Qualtrics platform, which requires users to pause third-party ad blockers and adheres to regional access restrictions across multiple countries.
Ryan DonovanWorking at the intersection of data and AI with Kenza Boulisfane
Thumbtack software engineer Kenza Boulisfane develops an artificial intelligence tool called the Marketing Analytics Agent to democratize access to complex cross-channel marketing data. Non-technical staff across Data Science, Growth, Brand, and Product can ask natural language performance queries without requiring SQL expertise or manual reporting. A primary technical challenge involves unifying fragmented data across multiple advertising platforms that define metrics differently while maintaining data reliability. The system interprets natural language queries, analyzes underlying performance metrics, and translates results into actionable, data-backed recommendations for next steps. Boulisfane also notes that virtual work environments enhance collaboration by encouraging clearer documentation, intentional communication, and focused individual productivity.
Thumbtack People TeamEngineering the right opportunities for Thumbtack Pros.
Ashmann Syngle, a backend software engineer on Thumbtack's Pricing team, focuses on systems that connect local service professionals with homeowners. To improve matching and revenue operations, the team recently deployed new pricing features, launched experiments, and partnered closely with Data Science and Monetization Experience groups. Current engineering efforts center on infrastructure enhancements, specifically upgrading alerting and monitoring across owned services to raise system reliability and operational efficiency. Because the team maintains complex monetization systems within a codebase that has evolved over many years, engineers conduct deep system analyses to evaluate edge cases before implementing foundational platform modifications. Thumbtack supports these initiatives through a virtual-first operational model complemented by regular in-person offsites.
AshmannsyngleSupabase ·
Supabrew - Never Code Thirsty
Supabase presented SupaBrew, a mock non-alcoholic beverage engineered specifically to address developer thirst during extended coding sessions and large pull request reviews. Developed following a survey of 80,000 registered developers, the recipe relies entirely on three ingredients consisting of barley, hops, and water in strict adherence to German beer purity laws. The mock packaging design features bottles manufactured from recycled cathode-ray tube monitors and labels repurposed from leftover Ubuntu conference stickers. The fictitious rollout introduces tiered pricing models, including free access for indie developers, Pay-as-you-Drink consumption billing, and dedicated enterprise tiers. Supabase concluded the announcement by confirming that the product release is an April Fools joke.
Ant WilsonSupabase ·
Should I Open Source my Company?
Software founders often hesitate to make their companies open source due to concerns regarding code scrutiny, security exploits, and intellectual property theft. Supabase operated as an open-source business from its inception, finding that community scrutiny actually accelerates code refactoring and surfaces security vulnerabilities early through public reporting channels. In addition, rapid execution and developer experience provide stronger competitive defenses against larger competitors than proprietary code obfuscation or software patents. Open repos also transformed the company's hiring strategy by replacing traditional take-home tests and LeetCode interviews with evaluation of real-world pull requests and asynchronous discussions. Finally, external contributors expand product capability by independently developing niche integrations and platform adapters that core startup teams lack the bandwidth to build.
Ant WilsonSupabase ·
Supabase Beta December 2021
Supabase announced a series of platform updates, educational content, and community milestones for December 2021. PostgreSQL instances now include the pg_sodium extension, enabling users to perform encryption, decryption, hashing, and cryptographic signing directly within database queries and functions through the Supabase Dashboard. The release details educational video guides demonstrating remote procedure calls from JavaScript, invoking external HTTP endpoints from database functions, and setting up triggers to run SQL on table modifications. In addition to ecosystem updates featuring new Python library releases and integrations with Divjoy and n8n, the project surpassed 26,000 GitHub stars and opened fully remote job positions across engineering, marketing, and human resources.
Paul CopplestoneSupabase ·
How we launch at Supabase
Following their participation in YCombinator, Supabase sought a structured method to maintain product momentum and recreate the urgency of an accelerator internally. The team established Launch Week, a quarterly shipping sprint using a fixed-timeline and flexible-scope model where a major feature or announcement releases each day for a week. Each cycle begins with a broad distributed planning session that maps high-level goals and generates ideas, followed by execution and finely scheduled launch days covering coordinated social media, blog posts, and community engagement. Following the launch, team members transition into maintenance mode and downtime to handle support, bug fixes, and open-source contributions. Finally, a structured retrospective evaluates successes, failures, and process relevance before carrying lessons into the next planning meeting.
Ant Wilson