# Google Calendar Google Calendar is a calendar product with REST and CalDAV APIs for programmatic interaction, plus tools for building integrations and automations. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## A Case for Time Tracking: Data Driven Time-Management DevFeed: [A Case for Time Tracking: Data Driven Time-Management]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-08-08T22:00:00Z Content type: opinion Language: en Sources: [Khan Academy]() Topics: [Google Calendar](), [data](), [Development](), [Tech Lead]() Tags: [data](), [developer](), [engineering](), [google](), [news](), [tech-lead](), [time-management](), [time-tracking](), [web-frontend]() ### AI overview The author describes tracking all work activities as personal Google Calendar events. They argue that the resulting data provides a clearer view of how time is spent and helps inform decisions, productivity, and confidence about work. ### Source excerpt By Oliver Northwood Tl;dr: Time-tracking everything I do in Google Calendar has made me happier, more productive, and ... Read more ## Calendar API: Local Calendars, Cloud Sync, and Conflict Handling DevFeed: [Calendar API: Local Calendars, Cloud Sync, and Conflict Handling]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-07-25T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [API](), [cross-platform](), [Concurrency](), [Cloud](), [Google Calendar](), [Android](), [iOS](), [macOS](), [Microsoft](), [JavaScript](), [HTTP](), [OAuth]() Tags: [android](), [api](), [apis](), [apple](), [backend](), [cloud](), [concurrency](), [cross-platform](), [google](), [http](), [ios](), [javascript](), [macos](), [oauth](), [offline](), [storage](), [sync](), [synchronization](), [work]() ### AI overview The article introduces a cross-platform calendar API that unifies local calendars and cloud providers through a capability-based model. It covers events, tasks, recurrence, time zones, offline mutations, optimistic concurrency, provider synchronization, and conflict handling. ### Source excerpt The new calendar API handles local calendars, cloud providers, recurrence, conflicts, and offline changes through one capability-based model. ## Announcing the winner of the Build on incident.io contest DevFeed: [Announcing the winner of the Build on incident.io contest]() Original publisher: [Read original article]() Author: Tom Wentworth Published: 2025-09-26T14:50:54Z Content type: news Language: en Sources: [The incident.io Blog]() Topics: [incident](), [Developer Platform](), [API](), [coding-community](), [MCP Server](), [AWS Lambda](), [Claude](), [Google Calendar](), [Slack](), [Docker](), [GitHub]() Tags: [ai](), [api](), [aws-lambda](), [claude](), [developers](), [docker](), [github](), [google](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [integration](), [mcp](), [mcp-server](), [outage](), [platform](), [post-mortem](), [projects](), [slack](), [slack-incident]() ### AI overview The article announces the winner of incident.io's developer contest, which invited creative uses of its developer platform. Submissions included on-call calendar conflict detection, Alexa-based voice access to incident data, and a Severance-inspired Slack bot that delivers wellness interventions to incident responders. The projects were evaluated for creativity, technical implementation, usefulness, potential impact, and overall distinctiveness. ### Source excerpt The "Build on incident.io" contest challenged developers to showcase the platform in the "coolest, weirdest ways" possible, with a MacBook Pro as the prize. Five finalists submitted creative projects including schedule conflict detection, voice-controlled Alexa integration, service health correlation analysis, and advanced monitoring dashboards. The winner was WARP - a Severance-inspired Slack bot that sends "mandatory wellness interventions" to incident responders through interpretive dance emojis, addressing burnout with the show's dystopian corporate wellness aesthetic. ## What's new in Figma: September 2022 DevFeed: [What's new in Figma: September 2022]() Original publisher: [Read original article]() Author: Chandler Sopko Published: 2022-09-28T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Chrome extension](), [Google Calendar](), [Template]() Tags: [chrome-extension](), [component](), [components](), [design-systems](), [features](), [figma](), [integration](), [latest-features](), [use-cases]() ### AI overview A roundup of Figma and FigJam updates from September 2022, including component properties, a Google Chrome extension for attaching files to Google Calendar events, Schema design-systems programming, and hundreds of new templates. ### Source excerpt A monthly round-up of the latest features, fixes, and finesse we've added to Figma and FigJam. ## Connecting to incident.io with Zapier DevFeed: [Connecting to incident.io with Zapier]() Original publisher: [Read original article]() Author: Charlie Kingston Published: 2022-08-11T00:00:00Z Content type: release Language: en Sources: [The incident.io Blog]() Topics: [incident](), [incident management](), [No-code](), [Slack](), [Google Calendar]() Tags: [google](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [no-code](), [outage](), [post-mortem](), [slack](), [slack-incident]() ### AI overview incident.io announces a Zapier integration for automating incident-management processes. Users can create incidents from Zap triggers, use trigger details to populate incident information, and automate post-incident tasks such as reminders, post-mortem nudges, incident-channel invitations, and Google Calendar retrospectives. ### Source excerpt Want to connect your incident management processes to existing systems? Our integration with Zapier can help! ## Shopify's Technical Interview Process: What to Expect and How to Prepare DevFeed: [Shopify's Technical Interview Process: What to Expect and How to Prepare]() Original publisher: [Read original article]() Author: Ashley Sawatsky Published: 2022-07-07T14:00:00Z Content type: tutorial Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Shopify](), [Google Calendar]() Tags: [communication](), [guide](), [how-to](), [interviewing](), [shopify](), [skills](), [support](), [technical]() ### AI overview A practical guide to Shopify's technical interview process, explaining what candidates can expect at each stage and offering preparation advice. It focuses on individual contributor roles and highlights the conversational Life Story interview, including the experiences and traits candidates may discuss. ### Source excerpt The interview process can be one of the most daunting aspects of finding a new gig--but it doesn't have to be. This guide pulls back the curtain on what to expect during the interview process for technical roles at Shopify and sets you up for success with tips for each stage. ## BarCampLondon2 Recap: Offline Web Applications, Amazon EC2, and OpenID DevFeed: [BarCampLondon2 Recap: Offline Web Applications, Amazon EC2, and OpenID]() Original publisher: [Read original article]() Author: Graham King Published: 2007-02-25T13:05:28Z Content type: article Language: en Sources: [Graham King]() Topics: [web applications](), [Amazon EC2](), [JavaScript](), [Rails](), [Amazon S3](), [Google Calendar](), [openid](), [Firefox]() Tags: [amazon-ec2](), [conference](), [firefox](), [javascript](), [openid](), [rails](), [recap](), [s3](), [society](), [software]() ### AI overview A recap of BarCampLondon2 highlights sessions on offline web applications, including a proxy-based approach for using Google Calendar without a network connection; running Rails applications on Amazon EC2 with persistent storage in Amazon S3; and an explanation of OpenID. ### Source excerpt "Unconvention-al Conversations: A BarCampLondon2 Recap."