最新

I recently shared a real case where DataMatrix-based automation exposed counterfeit pharma products across borders.

The industry is kind of in a bad spot, and I dont think its due to AI or Vibe Coding, because thats still niche. I am talking about the general sense of the market.<p>We are producing too much software on the web, yet nothing seems to work well. There is no creativity on the web as sites just look the same and even if we make a creative site, its not possible to get any traffic when google hogs it via AI summary or people dont even ask google about stuff in other cases.<p>Its now increasingly hard to make any money on the internet, we used to have blogs and individual sites making some money for the author, but now thats also not possible. Even if we dont talk about money, the websites all look the same, ask similar amount of money, in a similar way. I mean how many subscription services we think a user can have? At least some mobile apps give lifetime deals but on the desktop web thats increasingly rare. Is every site just a copy of a copy of copy of another site now? This started a long back but with AI its gonna be taken to an extreme level but I am hoping in few years we may find a way to break the cycle.

GYESME is an early-stage, design-led project exploring alternative architectural approaches within the GNOME desktop ecosystem.<p>Rather than aiming to replace GNOME or ship a new desktop environment, the project treats GNOME as a platform and asks a narrower question: which behaviors and assumptions could be made optional or more cleanly abstracted without compromising a minimalist default experience?<p>The current focus is on research and documentation rather than implementation. Areas being examined include:<p>Architectural modularity versus extension-based customization,<p>Opt-in functionality for features that are disabled or removed upstream,<p>Preserving established Linux interaction patterns without expanding defaults,<p>Reducing unnecessary hard dependencies where practical, including systemd-specific assumptions,<p>The intent is not to “fix” GNOME or argue against upstream decisions, but to explore design tradeoffs around minimalism, flexibility, and long-term maintainability in modern Linux desktops.<p>At this stage, the project consists primarily of a concept site, documentation, and open design questions. Feedback on the framing, assumptions, and scope is very welcome.<p>Project site and repository: <a href="https:&#x2F;&#x2F;github.com&#x2F;runleveltwo&#x2F;GYESME" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;runleveltwo&#x2F;GYESME</a><p>Thanks for taking a look.

We’ve all seen the crazy “10 parallel agents” type setups, but I never saw it fitting my workflow.<p>What I usually do is I would have Claude Code build a plan, Codex find flaws in it, iterating until i get something that looks good. I’d give direction and make sure it follows my overall idea.<p>Implementation is working well on its own.<p>But this takes a lot of focus to get right for me, I can’t see myself doing it on the same project, multiple features.<p>Am I missing something?

I analyzed 10 years of Hacker News data (2016-2025) to track Show HN submission trends.<p>- Show HN posts went from ~900&#x2F;month (2016-2019) to 3,315 in Dec 2025 - Share of all stories: 2.4% (2016) → 12.8% (Dec 2025) - Notable spikes: COVID-19 (2020), AI boom (2023), and accelerating growth through 2024-2025<p>Data source: HackerBook (144k Show HN posts &#x2F; 3.4M total stories)