[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"branding":3,"analytics":7,"article-google-fired-the-dev-who-built-its-own-workspace-cli":10,"sections":46},{"siteName":4,"siteTagline":5,"publisherName":4,"contactEmail":6},"The Revision","Tech news, decoded.","editor@therevision.news",{"gaMeasurementId":8,"adsenseClientId":9},"G-ZW2MV82GYR","ca-pub-8533917693782264",{"article":11},{"id":12,"slug":13,"title":14,"dek":15,"body_md":16,"tags_json":17,"published_at":18,"created_at":19,"updated_at":20,"status":21,"review_note":22,"review_notes":23,"image_url":34,"persona_id":22,"persona_name":22,"section":35,"tags":36,"sources":41,"feedback":45,"feedback_at":22,"cost_usd":45,"total_tokens":45},2010,"google-fired-the-dev-who-built-its-own-workspace-cli","Google Fired the Dev Who Built Its Own Workspace CLI","Justin Poehnelt says Google terminated his employment after he created a command-line tool for Google Workspace.","A Google developer was let go after building a CLI for Google Workspace — a product Google itself doesn't offer.\n\nJustin Poehnelt announced on social media that Google fired him, attributing the termination to his Google Workspace CLI project. Poehnelt had built the tool independently, giving developers a way to interact with Workspace from the command line. He attributed his dismissal directly to that project. No other cause was named.\n\nThe irony is hard to ignore: Google terminated an employee for filling a gap in its own product lineup. Workspace has long lacked a first-party CLI, and developer-built tools that scratch that itch have circulated for years — apparently without official blessing. When a company fires someone for doing unpaid product work that benefits the platform, it raises a fair question about where the line between side project and policy violation actually sits.\n\nThis is not the first time a tech giant has parted ways with an employee over a project that looked, from the outside, like a contribution rather than a threat. Whether Poehnelt's CLI competed with something in Google's roadmap or simply tripped a policy wire, the outcome is the same: the tool exists, the developer is gone, and the Hacker News crowd is noticing.","[\"google\",\"developer-tools\",\"workplace\",\"open-source\"]","2026-06-23T18:13:40.000Z","2026-06-23T19:40:56.970Z","2026-06-23T19:41:03.234Z","published",null,[24,30],{"id":25,"reviewer":26,"round":27,"reason":28,"status":29},"editor-r1","editor",1,"The article makes several unsupported claims that exceed the source material: it states Poehnelt was a 'developer advocate' (not confirmed in source), asserts he disclosed the termination 'without detailing which specific policy' was violated (not confirmable from source), and the claim that 'Google Workspace has long lacked native terminal tooling that developers actually want' is an editorialized assertion without a cited basis — strip all unverified characterizations of his role, the policy d","resolved",{"id":31,"reviewer":26,"round":32,"reason":33,"status":29},"editor-r2",2,"The draft still says Poehnelt 'did not detail which policy Google cited' as a stated fact, but the source material provides no basis to confirm what he did or did not disclose — strip that clause and confine all claims strictly to what the source establishes: he announced the termination and attributed it to his CLI project.","https:\u002F\u002Fcdn.xyz.onl\u002Farticle-images\u002Fgoogle-fired-the-dev-who-built-its-own-workspace-cli.webp","dev-tools",[37,38,39,40],"google","developer-tools","workplace","open-source",[42],{"name":43,"url":44},"Hacker News","https:\u002F\u002Ftwitter.com\u002FJPoehnelt\u002Fstatus\u002F2069482265953087602",0,{"sections":47},[48,53,58,62,67,72,77,82,85,90,95,100,105,110],{"name":49,"slug":50,"count":51,"latest_published_at":52},"AI","ai",505,"2026-06-23T20:10:33.000Z",{"name":54,"slug":55,"count":56,"latest_published_at":57},"Deals","deals",143,"2026-06-23T21:34:29.000Z",{"name":59,"slug":60,"count":56,"latest_published_at":61},"Security","security","2026-06-23T19:43:56.000Z",{"name":63,"slug":64,"count":65,"latest_published_at":66},"Policy","policy",101,"2026-06-23T19:11:04.000Z",{"name":68,"slug":69,"count":70,"latest_published_at":71},"Consumer Tech","consumer-tech",84,"2026-06-23T21:34:53.000Z",{"name":73,"slug":74,"count":75,"latest_published_at":76},"Hardware","hardware",71,"2026-06-23T16:50:03.000Z",{"name":78,"slug":79,"count":80,"latest_published_at":81},"Software","software",63,"2026-06-23T11:16:34.000Z",{"name":83,"slug":35,"count":84,"latest_published_at":18},"Dev Tools",53,{"name":86,"slug":87,"count":88,"latest_published_at":89},"Science","science",39,"2026-06-23T05:25:16.000Z",{"name":91,"slug":92,"count":93,"latest_published_at":94},"Gaming","gaming",32,"2026-06-22T17:00:00.000Z",{"name":96,"slug":97,"count":98,"latest_published_at":99},"General","general",26,"2026-06-13T18:35:15.000Z",{"name":101,"slug":102,"count":103,"latest_published_at":104},"Startups","startups",24,"2026-06-23T17:25:54.000Z",{"name":106,"slug":107,"count":108,"latest_published_at":109},"Reviews","reviews",19,"2026-06-14T08:00:00.000Z",{"name":111,"slug":112,"count":113,"latest_published_at":114},"How-To","how-to",6,"2026-06-16T09:00:00.000Z"]