Ask HN: How can you have fun doing corporate dev work in the age of AI tools?
The article discusses the impact of AI tools on corporate software development work. While these tools have made solo and small group projects more enjoyable, they have diminished the fun aspects of corporate development. The author expresses frustration over increased stress and reduced engagement due to constant context switching and higher expectations.
- ▪AI tools have made solo and small group building significantly more enjoyable.
- ▪Corporate software development work has become less fun due to constant context switching.
- ▪The author feels that the enjoyable aspects of their job have been replaced by stress and increased meetings.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Ycombinator |
| Canonical URL | https://news.ycombinator.com/item?id=48249258 |
| Publication time | Sat, 23 May 2026 17:03:19 +0000 |
| Retrieval time | 2026-05-23T17:07:27.532Z |
| Last seen | 2026-05-23T17:07:27.532Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | sshMuHm83zx9 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
My company, like many others, is heavily pushing agentic dev tools, putting up token usage leaderboards, etc.My problem is that corporate SWE work was already boring enough. You already had no say in the product or UX. This was compensated for by the ability to enter a fun "flow state" during implementation work, just working deeply on a problem for many hours and watching time slip by, having lots of schedule flexibility.Now, with AI tools, this seems totally gone. All that's left is constant context switching while you manage multiple agents and wait for them to complete at nondeterministic times. That, and increased expectations because "AI increases productivity", AKA more stress and more meetings.I have to say - AI tools have made solo and small group building 5x more fun...
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.