<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: wannabe44</title><link>https://news.ycombinator.com/user?id=wannabe44</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 27 Jul 2026 02:22:22 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=wannabe44" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by wannabe44 in "Go Analysis Framework: modular static analysis by go team"]]></title><description><![CDATA[
<p>In practice you use Go with a linter, so this is not a problem in practice. I have never seen a missed error.<p>The problem is painstakingly and manually having to build the stack trace, and then unwrapping it few layers above if you ever need to check what error it was.</p>
]]></description><pubDate>Mon, 27 Jul 2026 02:19:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=49064508</link><dc:creator>wannabe44</dc:creator><comments>https://news.ycombinator.com/item?id=49064508</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49064508</guid></item><item><title><![CDATA[New comment by wannabe44 in "Go Analysis Framework: modular static analysis by go team"]]></title><description><![CDATA[
<p>Oh yeah totally agree. I don't understand why someone would want to write `slices.Contains(s, needle)` when you can write this beautiful poem like a Shakespeare in VSCode:<p><pre><code>    found := false
    for _, v := range s {
        if v == needle {
            found = true
            break
        }
    }
</code></pre>
Oh and I totally want to build a stack trace manually. It's like doing cardio to me.<p><pre><code>    if err != nil {
       return fmt.Errorf("my function name but in spaces: %w", err);
    }
</code></pre>
This is very elegant by the way, so that we need errors.Is now, which has to dynamically check if the error implements Unwrap() error or Unwrap() []error. Because having any language facilities for error handling is harmful.</p>
]]></description><pubDate>Sun, 26 Jul 2026 17:41:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=49060417</link><dc:creator>wannabe44</dc:creator><comments>https://news.ycombinator.com/item?id=49060417</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49060417</guid></item><item><title><![CDATA[New comment by wannabe44 in "Worse on Purpose – How Corporate Greed Killed Product Quality – Worse on Purpose"]]></title><description><![CDATA[
<p>Slop on purpose</p>
]]></description><pubDate>Thu, 23 Jul 2026 14:20:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=49022087</link><dc:creator>wannabe44</dc:creator><comments>https://news.ycombinator.com/item?id=49022087</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49022087</guid></item><item><title><![CDATA[New comment by wannabe44 in "Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes"]]></title><description><![CDATA[
<p>> All the enterprisey stuff makes it feel a lot more complex than it really is.<p>Kubernetes is not PaaS. It is a low level container orchestrator. But people start by thinking of it as a ready-made PaaS and then keep on trying to make it closer to that vision by continually slapping random plugins on it.<p>In corporate environments, incompetence is the norm. Every kubernetes deployment in such places ends up relying on rando docker images, helm charts and "operators" written by script kiddies and webshits which break every night and are hardly better than coding the same functionality yourself.<p>You need a strong instinct to say "No" and taste to keep the system complexity under reasonable limits. Sometimes this involves actually architecting your "platform" code around the barebones orchestration provided by kubernetes instead of slapping on latest webshit shown on CNCF dot org. That sort of judgement and taste is impossible to find in corporate environments in the age of resume driven development. That is how most people get Kubernetes scars.</p>
]]></description><pubDate>Thu, 16 Jul 2026 13:15:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=48934080</link><dc:creator>wannabe44</dc:creator><comments>https://news.ycombinator.com/item?id=48934080</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48934080</guid></item><item><title><![CDATA[New comment by wannabe44 in "Dear sir, you have built a compiler (2022)"]]></title><description><![CDATA[
<p>Often the reverse happens. People will think some half baked toy will solve the problem and it brings it's own set of challenges.<p><a href="https://www.joelonsoftware.com/2001/10/14/in-defense-of-not-invented-here-syndrome/" rel="nofollow">https://www.joelonsoftware.com/2001/10/14/in-defense-of-not-...</a></p>
]]></description><pubDate>Sat, 23 Nov 2024 14:57:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=42221236</link><dc:creator>wannabe44</dc:creator><comments>https://news.ycombinator.com/item?id=42221236</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42221236</guid></item><item><title><![CDATA[New comment by wannabe44 in "DEI for Dummies"]]></title><description><![CDATA[
<p>In India, DEI is nothing but an initiative getting more ~posh~ Affluent urban women into IT jobs.<p>Whereas someone like me, from humble background and acquired much better skills by my own effort and sacrifice, is denied the same opportunities.</p>
]]></description><pubDate>Fri, 21 Apr 2023 04:35:14 +0000</pubDate><link>https://news.ycombinator.com/item?id=35649836</link><dc:creator>wannabe44</dc:creator><comments>https://news.ycombinator.com/item?id=35649836</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=35649836</guid></item></channel></rss>