<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: roymain</title><link>https://news.ycombinator.com/user?id=roymain</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Tue, 05 May 2026 08:21:57 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=roymain" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by roymain in "AI Self-preferencing in Algorithmic Hiring: Empirical Evidence and Insights"]]></title><description><![CDATA[
<p>What i have observed, which is the hard (unpredictable) part for candidates is, they can't tell which kind of hiring manager they'll get. Some reject resumes with metrics, others use software that won't let the resume through without them. Most (non-subject matter experts) would just look for whatever they think will get past the filter.<p>what i am researching right now is if you (hiring manager) got 2 resumes from the same candidate, one hand-written (metaphorically) and the other built by chat-GPT or AI, which one would you call ?</p>
]]></description><pubDate>Mon, 04 May 2026 07:00:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=48005519</link><dc:creator>roymain</dc:creator><comments>https://news.ycombinator.com/item?id=48005519</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48005519</guid></item><item><title><![CDATA[New comment by roymain in "Kimi K2.6 just beat Claude, GPT-5.5, and Gemini in a coding challenge"]]></title><description><![CDATA[
<p>The CV-to-six-months analogy is actually exactly right and it's also why benchmarks for hiring people stopped being useful. The signal that holds up is what you see when something breaks, which is hard to compress into a number.</p>
]]></description><pubDate>Sun, 03 May 2026 07:39:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=47994430</link><dc:creator>roymain</dc:creator><comments>https://news.ycombinator.com/item?id=47994430</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47994430</guid></item><item><title><![CDATA[New comment by roymain in "Ask HN: Is the Job Market Actually Bad?"]]></title><description><![CDATA[
<p>I have spoken to a couple of founders in the last few months and what I keep hearing isn't "we're not hiring" but "we're hiring fewer juniors and being pickier about the ones we take." The bar for what a screen actually tests for moved a lot in the last 18 months and most companies haven't caught up. Its like everyone has so much to absorb before they can decide who to pick. Most down-selected candidates have gone through 5-6 rounds of interview in their selection process.</p>
]]></description><pubDate>Sun, 03 May 2026 07:21:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=47994302</link><dc:creator>roymain</dc:creator><comments>https://news.ycombinator.com/item?id=47994302</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47994302</guid></item><item><title><![CDATA[New comment by roymain in "Ask HN: If coding gets faster, where should architecture happen?"]]></title><description><![CDATA[
<p>I believe you are overthinking. The "where" that you are pointing in your message doesn't really change. Architecture still happens in the head (figuratively) of whoever has to maintain the thing in 12 months, AI just makes it arrive faster so you have less room to defer those calls. Hope it helps.</p>
]]></description><pubDate>Fri, 01 May 2026 17:33:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=47977570</link><dc:creator>roymain</dc:creator><comments>https://news.ycombinator.com/item?id=47977570</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47977570</guid></item><item><title><![CDATA[New comment by roymain in "Ask HN: Is it still worth it to try to get a job in IT"]]></title><description><![CDATA[
<p>If you're genuinely fascinated by systems, yes is the answer. The point to understand is that the surface-level coding is what's getting cheaper, the systems work isn't.</p>
]]></description><pubDate>Fri, 01 May 2026 09:59:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=47972927</link><dc:creator>roymain</dc:creator><comments>https://news.ycombinator.com/item?id=47972927</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47972927</guid></item></channel></rss>