<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: anonyMusk</title><link>https://news.ycombinator.com/user?id=anonyMusk</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 29 Apr 2026 21:43:03 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=anonyMusk" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[Ask HN: How to resist taking ownership at work?]]></title><description><![CDATA[
<p>Context: I am fresh graduate working for a decacorn startup with over an year of experience working. I am fueled by curiosity - working on different things, not being dependant on others, and taking ownership of abandoned tasks. However, I hate working with lazy people who are entrusted with responsibility but never deliver. In such situations, how do I stay curious and learn, while not taking ownership of work which is supposed to done by such lazy persons?<p>More Examples
- I was tasked with overlooking the tech implementation of a project since all other leads' bandwidth were reserved. But, I saw this as an opportunity to work across multiple teams, identify their blockers, communicate project timelines, all while working on my tasks. Everyone appreciated my work.
- Another mission critical project comes. I apparently cannot lead since the new (2 quarters old) senior hire needs to be trusted with more work. (this guy/girl) is the laziest person i have ever met. Uses AI. Don't even try to understand what they did. Whenever I sit to review their code, every other line needs to be pointed. The review changes are so vast, that ultimately all of them are thrown under bus to meet deadlines.
- Even while they lead, they are a lazy person. They don't plan stuff before hand. Now here comes the tricky part. Should I take ownership again? 
- My reservations are, this project is seen as them leading its completion. My contributions will be overlooked. But I also don't really appreciate sitting around waiting for disasters to happen.<p>If asked the same in interviews - A lot of you may have answered that sitting it out, escalating to managers should be my next step. But let's just be honest. These things don't work practically.<p>-I have indirectly told them multiple times, that they need to step up and understand before pushing garbage. No effect. They are two quarters old, no difference. Manager is well aware. Still the only reason to keep them is that the manager could justify his/her bad hire.<p>I now, it sounds like a rant, but I am genuinely concerned. If you are someone who loves building things with purpose, putting in extra stuff, going extra mile just for the love of it, how do you navigate working with someone who is such a vibe killer? Has anyone of you faced anything similar? Would really appreciate your thoughts.</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=45571620">https://news.ycombinator.com/item?id=45571620</a></p>
<p>Points: 3</p>
<p># Comments: 1</p>
]]></description><pubDate>Mon, 13 Oct 2025 18:16:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=45571620</link><dc:creator>anonyMusk</dc:creator><comments>https://news.ycombinator.com/item?id=45571620</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45571620</guid></item><item><title><![CDATA[Show HN: JurnAI – An AI agent for daily motivation]]></title><description><![CDATA[
<p>JurnAI - is a virtual friend like agent that connects with your notion workspace and generates personalized message based on your last night's journal / diary entry.<p>The flow is very simple. User will write about their day in the night in their notion journal. The next morning, the AI agents goes through the entry, generates a personalized message with a positive tone. this message is then sent to the user via their registered mail. The process repeats every single day.<p>The idea was to give a feeling, that someone is out there, looking for you and caring for you. This message in the morning is supposed to serve as a motivational reminder while starting the day.<p>Used a public notion integration for secure access to user's journal. Utilized a Google Gemini and Cron-Job for automating the process of feedback generation.<p>Receiving a decent response. Could have been better. I think people either don't journal that much or are vary of sharing access to their entries.</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44784582">https://news.ycombinator.com/item?id=44784582</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Mon, 04 Aug 2025 11:52:32 +0000</pubDate><link>https://www.jurnai.site</link><dc:creator>anonyMusk</dc:creator><comments>https://news.ycombinator.com/item?id=44784582</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44784582</guid></item><item><title><![CDATA[Show HN: A Virtual friend that checks up on you, every morning]]></title><description><![CDATA[
<p>I vibe coded Jurn AI - a notion integration that lets your diary / journal talk to you.<p>It works by generating feedback from user’s last night journal. This feedback is then sent over mail to the user every morning with the intention of motivating them.<p>The idea is to give a friend/family like feel, daily checking up on you based on how your day went by.<p>To vibe code, used following agents, each with its own dedicated folder to store their system prompts and progress.<p>Frontend engineer - knows how to build a nextJS website. Responsible for building the user onboarding ramp.<p>Backend engineer - works with python and fastAPI. Help built the entire server side.<p>Program Manager - knows the requirements and the deadline. Helps keep a track of pending pointers.<p>Product expert - Understands what we are building and why. Helps refine Content on the landing page - optimizing layout for max user conversion. Helps in simplifying decisions<p>Infra Engineer - To be honest, I wasn’t able to use much of agent’s help in this. Their knowledge was outdated when it came to resolving platform specific bugs.<p>What do you think about this project?</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44771343">https://news.ycombinator.com/item?id=44771343</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Sat, 02 Aug 2025 20:50:22 +0000</pubDate><link>https://www.jurnai.site</link><dc:creator>anonyMusk</dc:creator><comments>https://news.ycombinator.com/item?id=44771343</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44771343</guid></item></channel></rss>