3
4 Comments

Why I care about your code

Hello Fellow Indie Hackers 👋

It's awkward because I've been for over a decade in the industry and most of the things I come up with, ever, ended up in the trash.

I live a really simple life. I also care about a very limited set of things. I think it's important what we leave behind and how we influence the world around us.

I'm kind of the same person when it comes to working.

I care about quality software and good craftsmanship. This is why I created

https://jscodeaudit.com/

I believe that any company that has some kind of software, is entitled to have good software. And it's not that hard. I've worked with teams where it took a call to explain to them how to fix an exploit. It took an email and a link to explain SQL injections. I want to do this on a scale and help as many businesses as possible.

Does this make any sense to you?

Thanks,

  1. 2

    Love the idea, hopefully I can be candid.

    I really dislike long sales pages (but it might just be me).

    I also don't think saying your service is expensive is a good strategy.

    Personally I would talk about how code audits can speed up development.

    I also don't get who your audience or job to be done is.

    1. 1

      Thanks, of course, thank you for sharing openly what you think.
      Here's a little background info on what inspired this:

      Over the past year or so I had the chance to look at the software products of different companies.
      They either wanted to change development teams because they weren't satisfied with the work they did or they realized they ended up in a complete mess.
      Usually, they had no idea where to start or in which state their software is. Deadlines were already missed & money was already spent.
      I looked at the code & created a Google Doc listing all the issues & a rough plan of what & how needs to be fixed.

      I really dislike long sales pages (but it might just be me).

      Maybe the screenshots are making this seem long or there is too much text?

      I also don't think saying your service is expensive is a good strategy.

      Oh I understand, I see how this came through. What I wanted to say is that putting together a quality codebase is expensive and putting together a bad codebase is more expensive - because of the recurring technical debt, lack of standards, basically what I (tried to) explain with the pictures & text.
      So it's expensive, without me. Didn't wanted to say that my services are expensive. 😬

      Personally I would talk about how code audits can speed up development.

      This is good, I'll figure out which part should I replace with this.

      It could be a section after Why perform a code audit? or part of it? 🤔

      I also don't get who your audience or job to be done is.

      My audience is companies & individuals who have some kind of software and they:

      • know it's probably in bad shape but they don't how bad it is or where to start with refactoring, how to change it (this is for ppl who know to code and can tell if something looks bad)
      • don't know what kind of codebase they have (non-technical founders) and they're planning on switching development teams or selling the company.
  2. 2

    I’d consider adding more info about why YOU are the best person to review their code.

    1. 2

      That is a really good point, thank you.
      I think it's also aligned with the next thing I want to add to the site.
      That is a blog post/free pdf - haven't decided yet with the practices I use and you can use to improve the quality of your code.

Trending on Indie Hackers
After 10M+ Views, 13k+ Upvotes: The Reddit Strategy That Worked for Me! 42 comments Getting first 908 Paid Signups by Spending $353 ONLY. 24 comments I talked to 8 SaaS founders, these are the most common SaaS tools they use 20 comments What are your cold outreach conversion rates? Top 3 Metrics And Benchmarks To Track 19 comments Hero Section Copywriting Framework that Converts 3x 12 comments Join our AI video tool demo, get a cool video back! 12 comments