Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #22433

N

Noop

Company blog · noop.dev/blog · on HN as noop_joeprogrammingsystemsweb

Noop is the company blog at noop.dev, writing about programming, systems and web. Since 2024, 3 different Hacker News readers have linked it 27 times, most often “Build Apps Not Infrastructure”. No feed was found, so read it on the site itself.

No feed foundVisit the blog
27mentions?
3HN people?
2024–2024first – last linked?

Too few sampled comments (1) to say how often HN recommends it.?

Why HN links it

Noop's article "Twelve Expectations for Developer Platforms" is discussed in one HN comment that cites it on programming logic in YAML and suggests CEL as a better option than a bespoke language.

Summarised by Claude from a sample of 1 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

The author on HN?

noop_joe · 22 karma · member since 2024

Developer Advocate @noop.dev joe.kendall@noop.dev

From their public HN profile, which links to this site.

Most-linked posts?

  1. Build Apps Not Infrastructure
    2 people · 4 mentions · first linked 2024-03-20
  2. Dev/Prod Parity with HTTPS on Localhost
    2 people · 2 mentions · first linked 2024-03-27
  3. Docker Desktop Alternative
    2 people · 2 mentions · first linked 2024-05-16

What Hacker News says?

  1. Totally, I think there's a lot of retroactive justification for what's familiar whether it be microservice or monolith. They both have advantages and disadvantages -- we're at a point where deploying and running either is available on most clouds. That said, I think interesting possibilities exist where the two approaches are blended. I work for a cloud [1] that supports a concept of "services" grouped within an app…

    Comment linking /docs/sleepy-services/

    on “What's New in Ruby on Rails 8”
  2. Submitted Show HN: Noop Workshop, Develop with Local/Cloud Parity as a story · 6 points

    HN discussion
  3. I'm working on a developer platform [1] that makes the progression from local development to global deployment way smoother than alternatives. At some point AI may have a role in the platform. But for now we're focused on much more fundamental problems related to the process of developing and scaling software applications. BTW we're looking for developers to try it out! 1. https://noop.dev

    Comment linking /

    on “Ask HN: What non-AI products are you working on?”
  4. Submitted Docker Desktop Alternative as a story · 2 points

    HN discussion
  5. I'd love to connect with you and talk more about this! I'm working for a company building something that addresses the problems you describe [1], ditto for pricing model. email is in my bio :-) 1. https://noop.dev

    Comment linking /

    on “Tooling has improved for ambitious software developers”
  6. Submitted IaC Is Not Making Your Team Any Faster as a story · 2 points

    HN discussion
  7. Full disclosure I work at a company [1] attempting to address this very problem. Without dedicated devops the challenge is allocating developer time to do the integration work required to get the various ops tools playing nicely together. In my experience that work is non-trivial and eventually leads to some form of dedicated ops. That is also part of a dynamic -- lots of tools available for solving these problems e…

    Comment linking /

    on “Ask HN: Startup Devs -What's your biggest pain while managing cloud deployments?”
  8. Submitted Build Apps Not Infrastructure as a story · 2 points

    HN discussion
  9. IaC is undeniably a good pattern for dealing with complex systems. The bigger problem is that it's not a solution for delineating responsibilities between software engineers and infrastructure engineers. All the specifics about an environment that need to make their way from software->infra (and in some cases the other way) still need to be worked out, and that's often a bigger problem than getting code to a box tha…

    Comment linking /blog/build-apps-not-infrastructure/

    on “Infrastructure as code is not the answer (2022)”
  10. Submitted Like Docker Desktop but Also for the Cloud as a story · 1 points

    HN discussion
  11. If I understand correctly, the benefit of using this over something like Compose is the parity with production. In my experience Compose is great for local development, but doesn't hold up well for complex architectures in production. I work for a company [0] building something similar, but mostly agnostic to programming language. One thing I particularly like about the approach is the reduction of time debugging pi…

    Comment linking /

    on “General Availability of .NET Aspire: Simplifying .NET Cloud-Native Development”
  12. Submitted Dev/Prod Parity with HTTPS on Localhost as a story · 1 points

    HN discussion
  13. Have you considered using a provider that might help eliminate some of the operational burden of running your apps? At a very high level, when using the big 3 and hosting that's raw infra you're going to find ways to pay for _keeping things running smoothly_. At least the big three have happy paths to avoid some of the operational burden (hidden among many many foot guns). Full disclosure I work at noop.dev [1], a h…

    Comment linking /

    on “Ask HN: Those of you who don't use AWS/Azure/GCP, what do you use for hosting?”
  14. Submitted Test Cloud Deployments Locally as a story · 1 points

    HN discussion
  15. Disclosure I work for a company, Noop [1], which is the picture of the steak. As someone working on the marketing side of the endeavor, I see the shift the author describes. there are a handful of PaaS companies picking up where Heroku left off and in the enterprise world devops is evolving toward "platform engineering". Platform engineering suffers from being poorly defined, but there appears to be growing demand w…

    Comment linking /

    on “Kubernetes is not the point”
  16. Submitted HTTPS Traffic Routing for Localhost as a story · 1 points

    HN discussion
  17. Noop [0] is a cloud platform that runs entire application ecosystems (including edge routing) locally and deploys the same setups globally -- it's a departure from the plug and play paradigm of kubernetes, but it means a lot less integration work. Full disclosure, I work @Noop. 0. https://noop.dev

    Comment linking /

    on “Ask HN: Dev/Ops/DevOps tools you use and more people should”
  18. The company [0] I work for gave a talk on this [1]. We're going a bit beyond analyzing logs because we have more contextual information about running software so we can compare different application state over time and infer whether it appears the application is experiencing an "incident". 0. https://noop.dev 1. https://www.youtube.com/watch?v=PxZx71xfIl8

    Comment linking /

    on “Has anyone used AI to diagnose system logs?”
  19. We are building an application/infra platform, Noop [0], it's multi-repo, one key benefit is it facilitates the deployment of different system components with greater isolation. That said, I'm a big fan of mono-repo. Noop actually supports developing mono-repos in a really interesting way. Here's an example [1] Vue + Node backend in one app. It should be pretty straightforward to see how you might be able to extrapo…

    Comment linking /

    on “Ask HN: Startups – Are you on a monorepo or multi-repo set up?”
  20. Not exactly a starter kit, but something I think could be useful during early development: Noop Workshop [1]. Full disclosure I work @ noop. One of the primary benefits is you can quickly explore what Cloud components you need (locally) before purchasing them. We also built a bunch of templates in different languages that act as application boilerplate. If it works the way you want in Workshop you can launch right t…

    Comment linking /

    on “Ask HN: What's the best SaaS starter kit for indie makers?”
  21. It might not matter _that much_ depending on the complexity of the application you're modeling. There are lots of options. A few things to consider: - Is it a dedicated individual or group responsible for the IaC? What are they comfortable with? - Details about the running app will need to find their way into the infra somehow (env vars at least), if it's a separate group or individual, what will be the most obvious…

    Comment linking /blog/build-apps-not-infrastructure/

    on “Ask HN: What's better Terraform or AWS CDK?”
  22. For building docs sites I like Astro. There are at least a few tailwind+docs themes available if you want to get something started fast. By default all content is markdown, but you can integrate with other CMSs. I think I used something called Spinal as a reference theme [1] I use astro for the development of my company's developer docs [2] -- I would reach for it for internal sites also. 1. https://spinalcms.com/re…

    Comment linking /docs/

    on “Ask HN: Best tools for creating user and developer documentation for web apps?”
  23. We're a developer platform [0], for running apps at scale and locally. The platform is batteries included: global router, logs, metrics, managed resources (datbases, caches, block storage). Because we have all this data in a unified platform we can (already, without AI) correlate issues across different system components, reliably and without elaborate integration work. We're now taking that a step further and using…

    Comment linking /

    on “Ask HN: What is your company doing with AI?”
  24. I don't know of an internal feedback tool, that's not more general purpose. I think a lot of what you're describing is the-practice-of-software-development. There are Lots of possible solutions, what works best for _your_ team will be somewhat unique to them. The company I work for [0] provides application hosting which includes automatic preview URLs, that can also be associated with a Github PR. The PR will have a…

    Comment linking /

    on “Ask HN: Internal feedback tool for webapps, how to QA?”
  25. Right now the term platform engineering seems to be a reflection of a collective intuition that software engineering teams need to have common patterns to simplify operating software. I think it stems in large part from the complexity associated with running software in a deployed environment. Often, every system, from development to deployment is mired in process. Tools and concepts have emerged to deal with _piece…

    Comment linking /

    on “Ask HN: Is there a place where one can learn about platform engineering”
  26. One thing I learned building a similar system to Noop, the authors of this article, is that people don't want to program logic in Yaml. Those of us that do, only do so because we are forced to for things like GitHub Actions, not because we want to. Using CEL would be better than something bespoke if you are going to add this to a Yaml based DSL https://noop.dev/docs/logic-reference/

    Comment linking /docs/logic-reference/

    on “Twelve Expectations for Developer Platforms”

Search all of HN for noop.dev