<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: mjsarfatti</title><link>https://news.ycombinator.com/user?id=mjsarfatti</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 09 Sep 2026 12:35:12 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=mjsarfatti" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by mjsarfatti in "I-have-ADHD: A skill to stop coding agents from burying the answer"]]></title><description><![CDATA[
<p>Because it’s wrong, and you are right. It should be in your global AND per-project md’s… Perhaps in a custom output style too.</p>
]]></description><pubDate>Wed, 09 Sep 2026 07:05:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=49622385</link><dc:creator>mjsarfatti</dc:creator><comments>https://news.ycombinator.com/item?id=49622385</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49622385</guid></item><item><title><![CDATA[New comment by mjsarfatti in "I-have-ADHD: A skill to stop coding agents from burying the answer"]]></title><description><![CDATA[
<p>Weak is even giving it too much credit imho, a yapping skill telling Claude to not yap can’t but fail.<p>I placed those instructions in setting > personal instructions, in my global CLAUDE.md, and in each project’s CLAUDE.md. I also use the concise output style in CC. If I choose a high thinking model it will start deviating in long sessions, then I just remind it in my next message:<p>“Remember ASD-STE100 style.<p>[rest of my message]”<p>BLUF sticks a lot easier than STE to be honest… but Claude knows what STE is, and using the “ASD-STE100 style” locution avoids the compliance issue (it’s true that strict ASD-STE100 compliance isn’t really possible, nor desired)</p>
]]></description><pubDate>Wed, 09 Sep 2026 07:02:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=49622351</link><dc:creator>mjsarfatti</dc:creator><comments>https://news.ycombinator.com/item?id=49622351</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49622351</guid></item><item><title><![CDATA[New comment by mjsarfatti in "I-have-ADHD: A skill to stop coding agents from burying the answer"]]></title><description><![CDATA[
<p>You don’t need a skill. Just tell it to BLUF (bottom line up front) and ASD-STE100.<p>And stop using Opus 9 Pro Max XHigh 10.0 for everything. If you choose a hyper-thinking model for asking the weather you can’t but expect yapping.</p>
]]></description><pubDate>Tue, 08 Sep 2026 19:28:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=49615605</link><dc:creator>mjsarfatti</dc:creator><comments>https://news.ycombinator.com/item?id=49615605</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49615605</guid></item><item><title><![CDATA[New comment by mjsarfatti in "Ask HN: Freelancer? Seeking freelancer? (September 2018)"]]></title><description><![CDATA[
<p>SEEKING FREELANCER | Frontend-with-some-backend | Brussels, Belgium | REMOTE<p>I'm looking for a frontend developer to build a React PWA, with enough knowledge to build a PHP/October CMS (Laravel) backend as well. 
Healthcare sector, so you will be doing something for a good cause!<p>Job to be carried out between October 1st and Novembre 30th.<p>Must have:
- 1-2 years of professional experience with React
- 1-2 years of professional experience with a PHP CMS
- Feeling comfortable building a PWA with backend from A to Z
- Proactive attitude
- Attention to details (for real, not the fake claim everybody puts in their cover letters)
The workload I estimate is 20-40 hours per week for 6-8 weeks (it will depend on your experience with the tools/tech).<p>Will pay central european rates.<p>To apply send an email to manuele@mjsarfatti.com with THE FOLLOWING:<p>- Subject: Job Application
- Link to your portfolio
- Link to ONE relevant project (it doesn't have to check all the boxes, it should be somehow relevant though)
- A paragraph about the project explaining ONE difficulty/challenge you encountered and how you solved it, or anything cool about the project that you enjoyed particularly
- (optional) your CV<p>Any other type of email or application will be ignored!</p>
]]></description><pubDate>Sat, 08 Sep 2018 13:13:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=17940685</link><dc:creator>mjsarfatti</dc:creator><comments>https://news.ycombinator.com/item?id=17940685</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=17940685</guid></item></channel></rss>