Tony Meijer
@tony-m-meijer.bsky.social
Data driven and context dependant. Project leader by day, building a SaaS by night.
Sometimes I wonder if maybe stories are just data with a soul...
Sometimes I wonder if maybe stories are just data with a soul...
Nothing in business is easy until you have done it at least five times. A lot is not easy even then.
#buildinpublic
#buildinpublic
May 23, 2025 at 9:58 AM
Nothing in business is easy until you have done it at least five times. A lot is not easy even then.
#buildinpublic
#buildinpublic
I ran into a wall with my latest idea, tried validating it on linkedin and basically crickets.
Asked @miracodes.bsky.social to take a look and she suggested asking perplexity to check what it thought my ideal customer profile where. Bad audience targeting it turned out.
#buildinpublic
Asked @miracodes.bsky.social to take a look and she suggested asking perplexity to check what it thought my ideal customer profile where. Bad audience targeting it turned out.
#buildinpublic
May 16, 2025 at 11:18 AM
I ran into a wall with my latest idea, tried validating it on linkedin and basically crickets.
Asked @miracodes.bsky.social to take a look and she suggested asking perplexity to check what it thought my ideal customer profile where. Bad audience targeting it turned out.
#buildinpublic
Asked @miracodes.bsky.social to take a look and she suggested asking perplexity to check what it thought my ideal customer profile where. Bad audience targeting it turned out.
#buildinpublic
Building a SaaS in 24 hours (or whatever) is like "I built this bridge from styrofoam and cardboard, of course it can handle a car".
You might want to do it for market testing, but not spending say a month extending it after the first 10 customers is troubling for me.
#buildinpublic
You might want to do it for market testing, but not spending say a month extending it after the first 10 customers is troubling for me.
#buildinpublic
May 5, 2025 at 8:06 AM
Building a SaaS in 24 hours (or whatever) is like "I built this bridge from styrofoam and cardboard, of course it can handle a car".
You might want to do it for market testing, but not spending say a month extending it after the first 10 customers is troubling for me.
#buildinpublic
You might want to do it for market testing, but not spending say a month extending it after the first 10 customers is troubling for me.
#buildinpublic
I created an api-generator. And then I extended it to handle the db connections. And then I extended it to handle login and monitoring. Now I'm extending it to generate html pages.
When does it stop being an api-generator and turn into a python version of wordpress?
#buildinpublic
When does it stop being an api-generator and turn into a python version of wordpress?
#buildinpublic
May 4, 2025 at 9:05 PM
I created an api-generator. And then I extended it to handle the db connections. And then I extended it to handle login and monitoring. Now I'm extending it to generate html pages.
When does it stop being an api-generator and turn into a python version of wordpress?
#buildinpublic
When does it stop being an api-generator and turn into a python version of wordpress?
#buildinpublic
A problem is that I really like bluesky for discussions but I think twitter is better for engagement ❤️
May 1, 2025 at 2:00 PM
A problem is that I really like bluesky for discussions but I think twitter is better for engagement ❤️
When calculating MRR, you need to do currency conversion.
It's a little bit of a hassle tbh, especially if you want to do it historically. I had expected there to be easily accessible api's or large tables to download, but none I could find. Guess I'l have to create my own table.
#buildinpublic
It's a little bit of a hassle tbh, especially if you want to do it historically. I had expected there to be easily accessible api's or large tables to download, but none I could find. Guess I'l have to create my own table.
#buildinpublic
April 25, 2025 at 4:43 PM
When calculating MRR, you need to do currency conversion.
It's a little bit of a hassle tbh, especially if you want to do it historically. I had expected there to be easily accessible api's or large tables to download, but none I could find. Guess I'l have to create my own table.
#buildinpublic
It's a little bit of a hassle tbh, especially if you want to do it historically. I had expected there to be easily accessible api's or large tables to download, but none I could find. Guess I'l have to create my own table.
#buildinpublic
In this post: bsky.app/profile/did:... I calculated it would take 127 deploys to start gaining time from my ci/cd pipeline.
I have run it 47 times since then, for an average of 5.2 times a day, i.e 16 days until I gain time from it.
#buildinpublic
I have run it 47 times since then, for an average of 5.2 times a day, i.e 16 days until I gain time from it.
#buildinpublic
It took me 5 hours 32 minutes to setup my ci/cd pipeline, or 332 minutes.
It takes me 2 minutes & 36 seconds to do it by hand (I clocked myself doing it 5 times). Assuming I will not mucking it up doing it manually (yeah, right), it will take 127 deploys to start winning time.
#buildinpublic
It takes me 2 minutes & 36 seconds to do it by hand (I clocked myself doing it 5 times). Assuming I will not mucking it up doing it manually (yeah, right), it will take 127 deploys to start winning time.
#buildinpublic
April 23, 2025 at 2:37 PM
In this post: bsky.app/profile/did:... I calculated it would take 127 deploys to start gaining time from my ci/cd pipeline.
I have run it 47 times since then, for an average of 5.2 times a day, i.e 16 days until I gain time from it.
#buildinpublic
I have run it 47 times since then, for an average of 5.2 times a day, i.e 16 days until I gain time from it.
#buildinpublic
Added portfolio and project pages to clearersense.com, including a demo page. Going to try to hook them up on friday, so that they actually can display something real.
#buildinpublic
#buildinpublic
ClearerSense
clearersense.com
April 23, 2025 at 2:29 PM
Added portfolio and project pages to clearersense.com, including a demo page. Going to try to hook them up on friday, so that they actually can display something real.
#buildinpublic
#buildinpublic
Interestingly enough, the first I would say 3-5 visitors on my saas where definitely bots looking for exploits (a lot of calls to wp-admin/setup-config and php info and stuff).
Now I have a good long list of requests to auto-block ip:s on 😅
#buildinpublic
Now I have a good long list of requests to auto-block ip:s on 😅
#buildinpublic
April 22, 2025 at 9:19 PM
Interestingly enough, the first I would say 3-5 visitors on my saas where definitely bots looking for exploits (a lot of calls to wp-admin/setup-config and php info and stuff).
Now I have a good long list of requests to auto-block ip:s on 😅
#buildinpublic
Now I have a good long list of requests to auto-block ip:s on 😅
#buildinpublic
Day 15 of the new saas.
Managed to get the html in order, Jinja2 is a bit of a struggle, at least for me. Nothing is hooked up yet, but if you want to take a look, here it is:
clearersense.com
#buildinpublic
Managed to get the html in order, Jinja2 is a bit of a struggle, at least for me. Nothing is hooked up yet, but if you want to take a look, here it is:
clearersense.com
#buildinpublic
ClearerSense
clearersense.com
April 22, 2025 at 8:55 PM
Day 15 of the new saas.
Managed to get the html in order, Jinja2 is a bit of a struggle, at least for me. Nothing is hooked up yet, but if you want to take a look, here it is:
clearersense.com
#buildinpublic
Managed to get the html in order, Jinja2 is a bit of a struggle, at least for me. Nothing is hooked up yet, but if you want to take a look, here it is:
clearersense.com
#buildinpublic
Yesterday did not go too well.
I started off good, but got hit with some very hard problems and lost a bit of faith in my idea tbh. The nights sleep helped, so much more motivated now. I think that I am a tad overworked also, so I will try to limit myself to 3-4 hours of coding.
#buildinpublic
I started off good, but got hit with some very hard problems and lost a bit of faith in my idea tbh. The nights sleep helped, so much more motivated now. I think that I am a tad overworked also, so I will try to limit myself to 3-4 hours of coding.
#buildinpublic
April 19, 2025 at 10:41 AM
Yesterday did not go too well.
I started off good, but got hit with some very hard problems and lost a bit of faith in my idea tbh. The nights sleep helped, so much more motivated now. I think that I am a tad overworked also, so I will try to limit myself to 3-4 hours of coding.
#buildinpublic
I started off good, but got hit with some very hard problems and lost a bit of faith in my idea tbh. The nights sleep helped, so much more motivated now. I think that I am a tad overworked also, so I will try to limit myself to 3-4 hours of coding.
#buildinpublic
So, today I have 8 hours of coding on clearersense today. I would ideally want to get login and perhaps some core functionality done.
I'l fill this with a thread on my progress, going to try to post something hourly.
Currently clearersense.com responds with a 404.
#buildinpublic
I'l fill this with a thread on my progress, going to try to post something hourly.
Currently clearersense.com responds with a 404.
#buildinpublic
clearersense.com
April 18, 2025 at 11:57 AM
So, today I have 8 hours of coding on clearersense today. I would ideally want to get login and perhaps some core functionality done.
I'l fill this with a thread on my progress, going to try to post something hourly.
Currently clearersense.com responds with a 404.
#buildinpublic
I'l fill this with a thread on my progress, going to try to post something hourly.
Currently clearersense.com responds with a 404.
#buildinpublic
Week 2 - SaaS build report
Last week was eventful, I managed to setup all infra (ci/cd, monitoring, nginx, docker) and get a landing page going.
This week will be getting core functionality in place.
Next week is launch if this goes well.
0% of running costs covered currently 😅.
#buildinpublic
Last week was eventful, I managed to setup all infra (ci/cd, monitoring, nginx, docker) and get a landing page going.
This week will be getting core functionality in place.
Next week is launch if this goes well.
0% of running costs covered currently 😅.
#buildinpublic
April 15, 2025 at 6:33 AM
Week 2 - SaaS build report
Last week was eventful, I managed to setup all infra (ci/cd, monitoring, nginx, docker) and get a landing page going.
This week will be getting core functionality in place.
Next week is launch if this goes well.
0% of running costs covered currently 😅.
#buildinpublic
Last week was eventful, I managed to setup all infra (ci/cd, monitoring, nginx, docker) and get a landing page going.
This week will be getting core functionality in place.
Next week is launch if this goes well.
0% of running costs covered currently 😅.
#buildinpublic
Not sure what to say here, but I have a waitlist to join for clearersense now (since like 3 minutes).
The idea is to act as a 3rd party verifier for people that publish their mrr/arr, like @marclou.bsky.social.
Waitlist here:
demo.clearersense.com
#buildinpublic
The idea is to act as a 3rd party verifier for people that publish their mrr/arr, like @marclou.bsky.social.
Waitlist here:
demo.clearersense.com
#buildinpublic
ClearerSense
demo.clearersense.com
April 12, 2025 at 8:57 PM
Not sure what to say here, but I have a waitlist to join for clearersense now (since like 3 minutes).
The idea is to act as a 3rd party verifier for people that publish their mrr/arr, like @marclou.bsky.social.
Waitlist here:
demo.clearersense.com
#buildinpublic
The idea is to act as a 3rd party verifier for people that publish their mrr/arr, like @marclou.bsky.social.
Waitlist here:
demo.clearersense.com
#buildinpublic
It took me 5 hours 32 minutes to setup my ci/cd pipeline, or 332 minutes.
It takes me 2 minutes & 36 seconds to do it by hand (I clocked myself doing it 5 times). Assuming I will not mucking it up doing it manually (yeah, right), it will take 127 deploys to start winning time.
#buildinpublic
It takes me 2 minutes & 36 seconds to do it by hand (I clocked myself doing it 5 times). Assuming I will not mucking it up doing it manually (yeah, right), it will take 127 deploys to start winning time.
#buildinpublic
April 12, 2025 at 11:10 AM
It took me 5 hours 32 minutes to setup my ci/cd pipeline, or 332 minutes.
It takes me 2 minutes & 36 seconds to do it by hand (I clocked myself doing it 5 times). Assuming I will not mucking it up doing it manually (yeah, right), it will take 127 deploys to start winning time.
#buildinpublic
It takes me 2 minutes & 36 seconds to do it by hand (I clocked myself doing it 5 times). Assuming I will not mucking it up doing it manually (yeah, right), it will take 127 deploys to start winning time.
#buildinpublic
Creating a docker build action in github is weirdly easy. So, now I can build and deploy docker containers to my ec2 instance. Next jobb will be to populate it with something and showcase it. Weird and wonderful that I am on day 3 and basically the ci/cd infra is done...
#buildinpublic
#buildinpublic
April 9, 2025 at 8:56 PM
Creating a docker build action in github is weirdly easy. So, now I can build and deploy docker containers to my ec2 instance. Next jobb will be to populate it with something and showcase it. Weird and wonderful that I am on day 3 and basically the ci/cd infra is done...
#buildinpublic
#buildinpublic
Nginx Proxy Manager was extremely easy to get going. The thing I once bought in (custom reverse proxy + setting up ssl + enforcing ssl + a bunch of other things) it solves out of the box. Tick on first hurdle fixed.
Next up, configure github to build on my ec2 instance.
#buildinpublic
Next up, configure github to build on my ec2 instance.
#buildinpublic
April 7, 2025 at 9:56 PM
Nginx Proxy Manager was extremely easy to get going. The thing I once bought in (custom reverse proxy + setting up ssl + enforcing ssl + a bunch of other things) it solves out of the box. Tick on first hurdle fixed.
Next up, configure github to build on my ec2 instance.
#buildinpublic
Next up, configure github to build on my ec2 instance.
#buildinpublic
Kicking off a new SaaS project — and building in public.
It’s a trust-building-marketing app for small businesses + indie brands using Stripe.
So, I have bought a domain, and tonight I'l start setting up nginx.
0% of running costs covered 😅
#buildinpublic
It’s a trust-building-marketing app for small businesses + indie brands using Stripe.
So, I have bought a domain, and tonight I'l start setting up nginx.
0% of running costs covered 😅
#buildinpublic
April 7, 2025 at 11:33 AM
Kicking off a new SaaS project — and building in public.
It’s a trust-building-marketing app for small businesses + indie brands using Stripe.
So, I have bought a domain, and tonight I'l start setting up nginx.
0% of running costs covered 😅
#buildinpublic
It’s a trust-building-marketing app for small businesses + indie brands using Stripe.
So, I have bought a domain, and tonight I'l start setting up nginx.
0% of running costs covered 😅
#buildinpublic
April 4, 2025 at 3:58 PM
The hardest problem in software development is understanding what people need.
March 31, 2025 at 3:48 PM
The hardest problem in software development is understanding what people need.
The closer I get to launch the more I think about the market I am serving. 😅
It should have been the other way around of course.
#buildinpublic
It should have been the other way around of course.
#buildinpublic
March 27, 2025 at 5:54 AM
The closer I get to launch the more I think about the market I am serving. 😅
It should have been the other way around of course.
#buildinpublic
It should have been the other way around of course.
#buildinpublic
Got 500 lines of code from a subcontractor for my saas, no unit-tests. I have started building them for it, roughly 35 lines in, two bugs found and fixed.
Things does not get quicker by omitting unit tests, your just changing the time of when you will suffer.
#buildinpublic
Things does not get quicker by omitting unit tests, your just changing the time of when you will suffer.
#buildinpublic
March 25, 2025 at 7:49 AM
Got 500 lines of code from a subcontractor for my saas, no unit-tests. I have started building them for it, roughly 35 lines in, two bugs found and fixed.
Things does not get quicker by omitting unit tests, your just changing the time of when you will suffer.
#buildinpublic
Things does not get quicker by omitting unit tests, your just changing the time of when you will suffer.
#buildinpublic
As far as I can tell, if Teslas stockprice goes beneath 101 USD then Elon Musk does not have sufficient collateral for the debt burden he holds on them (i.e forced selloff). This does not account for any other holdings (X/Starlink/SpaceX) he has.
Sources and reasoning in the comments.
Sources and reasoning in the comments.
March 19, 2025 at 9:57 AM
As far as I can tell, if Teslas stockprice goes beneath 101 USD then Elon Musk does not have sufficient collateral for the debt burden he holds on them (i.e forced selloff). This does not account for any other holdings (X/Starlink/SpaceX) he has.
Sources and reasoning in the comments.
Sources and reasoning in the comments.
A rule of thumb for the law of large numbers is that a sample of 30 is statistically significant.
Have you talked to 30 of your customers?
#buildinpublic
Have you talked to 30 of your customers?
#buildinpublic
March 10, 2025 at 7:51 AM
A rule of thumb for the law of large numbers is that a sample of 30 is statistically significant.
Have you talked to 30 of your customers?
#buildinpublic
Have you talked to 30 of your customers?
#buildinpublic
Planing pokers scales is odd.
I rather think we should just use this schema:
if time is < 3 days, estimate as honestly as possible. For every four tasks/dev, add a day as buffer.
If time is > 3 days but likely doable in the sprint, assume it will take the sprint.
else:
Break it down further.
I rather think we should just use this schema:
if time is < 3 days, estimate as honestly as possible. For every four tasks/dev, add a day as buffer.
If time is > 3 days but likely doable in the sprint, assume it will take the sprint.
else:
Break it down further.
March 1, 2025 at 10:14 AM
Planing pokers scales is odd.
I rather think we should just use this schema:
if time is < 3 days, estimate as honestly as possible. For every four tasks/dev, add a day as buffer.
If time is > 3 days but likely doable in the sprint, assume it will take the sprint.
else:
Break it down further.
I rather think we should just use this schema:
if time is < 3 days, estimate as honestly as possible. For every four tasks/dev, add a day as buffer.
If time is > 3 days but likely doable in the sprint, assume it will take the sprint.
else:
Break it down further.