Join the Examfly Team

Hi, I’m looking for a Full Stack developer to join the Examfly team. 

Anyone interested in getting involved in an exciting early-stage startup? 

Reach out. Let’s catch up.

Needs experience in JavaScript, React, Node.js. 

See job description for more details. 

Must be based in Ireland.  

No recruiters please. 

Get in touch with me here

https://www.linkedin.com/in/jamiegood/

Thanks

Jamie

Next NDRC Startup Accelerator

It’s not too late to apply for the next NDRC Startup Accelerator at Dogpatch Labs

Closing date Sunday 3 December 2023

I went through the accelerator last year and it was an incredible learning experience. You really get to benefit from the vast experience at Dogpatch and tap into a whole range of networking and funding opportunities.

Investment and mentoring! yay!

The NDRC team are willing to take a chance! I suppose that’s what being in a startup is all about.

Interested to hear about the next cohort of startups.

How to Prevent Over-engineering a Startup

Over-engineering can cripple your startup. 

Here are 13 ways you can prevent this from happening.

If you are a technical solo founder or an all technical founding team you may need to read this.

Example Scenario:

Early stage startup. Tech solo founder or all technical founders. Pre PMF, little to no revenue yet. 

Got an idea to ‘change an industry’ and seeking to validate that through learning from user engagement & feedback. Fully prepared to pivot as you learn more.

1: The Golden Rule

Avoid premature tech optimisation. For example: Building to handle millions of users when your goal is 100s users. 

The software architecture that Netflix or AirBnB have in-place now was NOT their architecture when they started out.

2: The right software architecture depends on the context

Choosing the wrong software architecture will slow down your development velocity and increase your infra spend.

3:  Focus on what matters

Define your core business metrics.  EG AARRR or others. 

What metrics can ensure your business survives? Not just survive but thrive. The needles you must move. 

Focus your activity towards moving these needles.

4:  Figure out what the hard part is

Ensure the bulk of the teams effort is focused on the hard part. As a technical founder this may not be the tech. Often for you the tech will be the ‘fun part’. 

Make sure you prioritise.  Up skill and / or hire to fill the gaps.

5: Avoid Magpie Syndrome or Shiny Object Syndrome

What Tech stack should you choose? What you are most productive with is usually the right answer. 

Learning new tech comes at a cost of time. What is the best possible use of the time?

6: Marketing

If you think this is a dirty word you are in trouble. 

If you don’t have marketing skills on your team then you are all the marketers now.

Congrats.

 Same goes for sales.  Upskill and / or hire to fill the gaps.

7: Fight the urge to over complicate

Leverage boilerplate or template applications, no-code, PaaS options to avoid reinventing wheels. Free up your energy to focus on what really matters to your startup.  See number 3 above.

8: Avoid EGO driven development 

When you make tech decisions based on what tech you want to show on your CV.  This is EGO driven development. 

This isn’t about you. It’s a race to tap into an opportunity. 

9: If you build it…..

Developers love to build product. But building a product is a sub set of building a startup. How will you deal with managing what you need to do versus what you love to do?

10: Seek Advice

Most importantly. Seek advice from those who have been in the trenches. Such as a startup eco system. They can help you see your blind spots.

11: Embrace tech debt is a lever

Controversial. Paying off tech debt fully is for startups with validation, revenue, funding.

Take on tech debt and pay back when you can.

Better yet practise KISS, YAGNI, Clean Code to keep tech debt to a minimum

Have you earned ‘earned the right’ to deal with it?.  Leverage debt and pay it off when you can afford to.  If you get to that point. Congrats! 

90% of startups don’t make it.

12:  KIS. YAGNI

Keep it simple. You Aren’t Gonna Need It

Tip: Daily mantra to be repeated at every team standup.

13: Problem V Solution

Problem space versus solution space.

Depending on the startup stage you are at, the weight of importance slides between ‘problem space’ and ‘solution space’.

As devs we have a urge to skip the more ambiguous first (problem space) and instead jump straight into the second (solution space).

But the solution doesn’t matter if you are solving a problem no one cares about.

And how about you? How do you prevent over-engineering a startup? 

We are joining the NDRC Startup Accelerator

Happy to announce we at terrabyte are joining the NDRC national startup accelerator, Ireland’s national startup accelerator programme for globally ambitious tech entrepreneurs in Ireland.

Our developer showcasing platform thefullstack.network was chosen along with 6 other companies out of a total of 300 applicants.

The accelerator is run by Dogpatch Labs Startup Hub and comprises of investment plus mentoring and support. I’m particularly impressed to date by the focus on mentoring and am excited to see how we will evolve over the next few months.

https://www.irishtimes.com/business/2022/08/04/six-start-ups-chosen-for-latest-ndrc-acclerator/

Book Summary: The Mom Test

Drop everything, drop whatever you’re doing now and read The Mom Test


We had been discussing product startup ideas and reached that most important question: 
How can you tell if your startup product is actually needed?


The answer: You’ve got to talk to people of course. But these conversations are rich in false positives and can send you down the wrong path.

The Mom Test by Rob Fitzpatrick offers are framework for how to handle these customer conversations. 

The Mom Test by Rob Fitzpatrick : How to talk to customers and learn if your business is a good idea when everyone is lying to you

Below are the The Mom Test Rules of Thumb helping me navigate these vital conversations.

Rules of thumb

  • Customer conversations are bad by default. It’s your job to fix them. 
  • Opinions are worthless. 
  • Anything involving the future is an overly-optimistic lie. 
  • People will lie to you if it’s what they think you want to hear
  • People know what their problems, but they don’t know how to solve those problems 
  • You shooting blind until you understand their goals. 
  • Some problems don’t actually matter. 
  • Watching people do a task will show you what the problems and inefficiencies really are, not what the customer things they are. 
  • If they haven’t looked for ways for solving it already, they are not going to look for (or buy) yours. 
  • People stop lying when you ask them about money 
  • While it’s rare for someone to tell you precisely what they’ll pay, they’ll often show you what it’s worth to them. 
  • People want to help you.  Give them an excuse to do so. 
  • Compliments are the fool’s gold of customer learning: shiny, distracting and worthless. 
  • Ideas and feature requests should be understood, but not obeyed. 
  • If you’ve mentioned your idea, people will try to protect your feelings.
  • Anyone will say your idea is great if you’re annoying enough about it. 
  • The more you’re talking, the worse you’re doing. 
  • you should be terrified of at least one questions you are asking in every conversation. 
  • There’s more reliable information in a “meh” than a “Wow!” You can’t build a business on a lukewarm response. 
  • Start broad and don’t zoom in until you’ve found a strong signal, both with your whole business and with every conversation. 
  • You always need a list of your 3 big questions. 
  • Learning about your customer and their problems works better as a quick and casual chat than a long, formal meeting. 
  • If it feels like they are doing you a favour by talking to you, it’s probably too formal. 
  • Give as little information as possible about your idea while still nudging the discussion in a useful direction. 
  • “Customers” who keep being friendly but aren’t ever going to buy are a particularly dangerous source of mixed signals. 
  • If you don’t know what happens next after a product or sales meeting, the meeting was pointless. 
  • The more they’re giving up, the more serious you can take what they are saying. 
  • It’s not a real lead until you’ve given them a concrete chance to reject you. 
  • In early stage sales, the real goal is learning. Revenue is a side-effect. 
  • If it’s not a formal meeting, you don’t need to make excuse about why you’re there or even mention that you are starting a business. Just ask about their life. 
  • If it’s a topic you both care about, find an excuse to talk about it. Your idea never needs to enter the equation and you’ll both enjoy the chat. 
  • Kevin Bacon’s 7 degrees of separation applies to customer conversations. You can find anyone you need to if you ask a couple of times.  
  • Keep having conversations until you stop hearing new stuff. 
  • If you aren’t finding consistent problems and goals, you don’t have a specific enough customer segment. 
  • Good customer segments are a who-where pair. If you don’t know where to go to find your customers, keep slicing your segment into smaller pieces until you do. 
  • If you don’t know what you are trying to learn, you shouldn’t bother having the conversation. 
  • Notes are useless if you don’t look them up. 
  • Go build your dang company already. 
  • It’s going to be okay.  

Book Review: The Cold Start Problem

Recently I finished listening to the book The Cold Start Problem.

This couldn’t have come at a better time for us as we continue to build to our pro developer network thefullstack

The Cold Start Problem details the principles and tactics that have helped massively successful products such as Uber, AirBnB and Dropbox to grow via network effects.

2 key takeaways for me are the importance of building ‘Atomic Networks’ and also measuring product network effects via the ‘Growth Accounting Equation’.

Meet The Full Stack

I am excited to share a new project I am involved with called The Full Stack and I would really appreciate your valuable input and feedback.

Meet The Full Stack – The professional network built for Software Engineers. https://thefullstack.network

The Full Stack is a platform designed for software engineering that I wished had existed throughout my career and to this very day. We’re hoping this platform helps engineers, managers and teams on their journey:

  • Showcase you and your projects on a professional network specifically for Software Engineering.
  • Connect with like minded engineers and build a more meaningful network (no spam!).
  • Don’t let your work get overlooked, instead let it connect you to opportunities from Teams and Engineering Managers looking for engineers just like you.
  • Unlike other networks liked LinkedIn, when “real” engineering hiring managers reach out to you on The Full Stack, you get paid into your wallet for reading and responding to opportunities, putting you in control.

The platform is built in Next.js, Tailwind, Spring, NodeJS, MongoDB running on Google Cloud Platform.

I’d really appreciate your feedback and thoughts. Reach out!

Check out https://thefullstack.network/.