I recorded vlogs to show how I built side projects
indielog.com
indielog.com
I mean, I am enjoying the custom webpack setup that I built for my work project... but just because I can do that stuff doesn't mean I should.
Nothing wrong with tossing a php script on some shared hosting.
I'll say though, after having done a few side projects with modern SaaS/stack -- e.g. Netlify, Heroku, nodejs -- it does start to look like to me that it's a time trade-off. When I embrace the JAM stack with static site gen (with Svelte/Sapper) and an API layer (nodejs on Heroku), what I'm doing is trade the time to get started (more time/effort) with less maintenance and deploy effort later. But if you have the passion to hack up something right this moment and can't deal with that drag to kick off the project, and you don't know if it's a product that'll work out and get traction anyway, by all means hack it up in PHP and jquery.
It made me realize that the "right way" is also a question of circumstance. The "right way" exist for one thing, avoiding some kinds of issues, but a side project is often quite simple, and most of theses issues won't happen, you most likely won't gains anything doing theses, so is it really the "right way" then?
It was hard to write that badly at first, hell my server side code is still mostly a single file, but most of my code took only a few hours to write, it's so easy right now to just erase a part of it and make it better. The frontend is using React, and at first it was a single big component, again the wrong way, but that component did something and it was working. Once I got some duplication in it, well I moved some stuff to another component. I could have done that earlier, I knew I would have duplication there, but I would have lost time making another component if I had abandoned the project (and I would most likely have if I had done everything "the right way").
So yeah, I'll keep doing it that way for now, doing it the bad way until I actually need the right way.
Rails 5 with webpacker and turbolinks strikes the perfect balance between classic and modern web dev imo.
Edit: For those of you looking for a way to get simple prototypes working without having to use opinionated frameworks like Laravel or going down the JS rabbit hole, try Flask (in combination with SQLAlchemy and Marshmellow if you also need a simple ORM). Full flexibility, can be learned in minutes and you have the whole freedom of Python to do what you want.
As for the VAT, I am leaning towards paddle instead of stripe, because they take care of everything tax related (for a bit bigger piece of pie of course). Any thoughts on this?
Good luck!
As for VAT, I’m focusing on the EU market at the moment. EU law is that all SaaS B2C sales have to pay VAT in the country where the client resides, luckily there’s a process called mini one stop shop which allows you to file your VAT taxes in one EU country (while still indicating the country of every sale) which will then take care of the redistribution of the VAT taxes (a similar procedure exists for non-EU businesses who have EU customers, searching for EU VAT on e-Services should help you get started). With Stripe that means creating a taxId for every country and matching that with the country of residence my users have to provide on checkout when I create their session in the backend. Sadly I haven’t found any good applications that then take care of everything so it’s probably going to have to be a mix of csv importing everything into accounting software and handing everything to an account. It’s a bit frustrating tbh because it looks like accounting will be the single biggest expense in the initial phase of the business. So if anybody knows of a good solution for EU-wide SaaS B2C sales with Stripe I would be happy if they shared them. Even Quaderno and the like are not really feasible if you’re product costs less than 5$/month since they base their pricing on the number of sales.
Btw, it might make sense to contact Quaderno (/others) and describe your pain point, they might be able to offer some solution.
Do you actually need Cognito and a Serverless API?
It's a drag because you put yourself requirement that make no sense with your project. The goal of theses tools are to make you go quicker, if they doesn't, it should be your first warning that they aren't for you right now.
Something like React is almost plug and play at this point. It builds into a static site that can be uploaded any more.
Even a non basic PHP app is more effort
But for me, to setup some full-sized project is still pretty daunting, and boilerplates and scaffolds are pretty messy and brittle.
When I'm setting up side projects, I would still use Basic Node.js + Parcel + Heroku as a starting point. It would only take minutes at most.
That, or I use heroku/a private k8s cluster on digitalocean when it's a tad more serious, that I just throw the docker container on and have it over with.
Like you, the last quick prototype I did was all html and js uploaded to a shared hosting (https://arcadejack.com). I would like to get back to building simple apps, but the barriers are higher than 20 yrs ago. For my current side project I'm using PHP and hired a developer online to help me with initial boilerplates.
This has also opened a new dangerous attack vector where hackers take over a small forgotten component used by many nodejs packages and inject malicious code into projects without anyone noticing.
It ended up being some arcane combination of config for... webpack, I think? Which is really weird because it seems to me "bundle all this in one file for web" is one of the countable-on-one's-fingers most-common use cases for a JS bundler, so should probably be available with a command line switch and no config file at all.
If I've found the right file (I was just trying to slap something together to try out a couple node modules in the browser... so much for that being quick & easy) then I ended up on an es5 target for TS, with "amd" module output. I've also got about a 12 SLOC webpack config file that specifies a single output "bundle.js".
The worst thing about troubleshooting shit like this is it's rarely clear what's broken. Is some part of the build choking on a bad ES-version + module combo (but just producing a broken build rather than, you know, fucking telling me that)? Is it a bundler config problem? Is Node at the wrong version(!)? So the troubleshooting process rapidly becomes combinatoric, which is an awful experience. You google some of these problems and see that everyone else is clearly going through the exact same "try one combination, see what happens, try the next" brute-force approach as you are. Meanwhile, again, the common use cases for these tools seem easily enumerable and quite tractable, so why they're driven indirectly by smashing together a bunch of implementation details until they work, rather than by explicitly stating which of a small number of common desired outcomes one wants and letting the build tools figure out how to make that happen in all but the most unusual cases, is baffling to me.
Serverless, everything-in-javascript, jamstack etc. are fads that are currently overhyped. (There are of course use-cases where they make sense. But for most project having a normal backend is clearly superior and much simpler.)
* Django https://www.djangoproject.com/ * Unpoly https://unpoly.com/ * Parcel https://parceljs.org/ * Heroku https://www.heroku.com/ * Tailwindcss https://tailwindcss.com/
Other than that, I use it in several of my own side projects.
Thanks for answering.
Thanks for suggesting the fix!!!
I never did something like this, putting myself in the public. It sounds scary. Indeed it was in the beginning, but it's an incredible journey so far!
IE: "My trip to Cabo" might include 1-2 stories out of 10 posted that day, but they are the user's favorite and tell a cohesive story.
Another analogy is Youtube's "Playlist" feature.
I think some will say that you'll lose a sense of discovery by not being on one of the largest video platforms, but you'll gain an opportunity to build something from scratch and see what you can cultivate. It really comes down to your goals/intent, and I think you did a great job of explaining your choice so far!
Also it's interesting to see most of our members never did vlog before. But they still love to share their updates on IndieLog. I think it's because people feel that there are like-minded people around. You can't get the feeling by posting a video on YT.
Congrats on getting to the 100-mark! What do you think was the best thing to come out of vlogging simultaneously?
The best thing so far is definitely making lots of friends around the world. We can see each other, hear each other. It's the feeling that none of those text-based forums can give.
For the purpose of indie log it might be sufficient to handroll a custom script that takes the snapshots and then use ffmpeg to convert them to a video.
I would love any constructive feedback if you want more content like this.
Here's today's vid - https://youtu.be/KI4Hv3uBjVY
(https://indielog.com/video/yo-indie-log-you-ready-53ab5efa)
It would need to support longer than 2 minute videos to do that. I'd like to see Indielog pick up momentum.
Thanks a lot!
I was recently on Indie Hacker's podcast and got a lot of followup emails from other engineers asking questions and it was cool talking with random developers.
Is there a way to post a link to a youtube video on IndieLog so I can double dip?
I added it to our backlogs: https://indielog.backlogs.co/post/allow-indietubers-to-share...
Actually for Backlogs, some features are already taken from IndieLog, like the upvote and commenting. I just implemented the roadmap boards and the changelog page.
Haha, I built the Backlogs on the side, so it is a slow process :)
The platform is still very young, 4 months old. I am trying to bring more features into it. Audio update is the next thing.
perhaps if GitHub gave us a way to do media attachments with particular commits, we could let people embed instructional/teaching moments in their code bases...
not suggesting GitHub is the only player out there, but may be big enough to give this a try as a side project for some of the internal folks.
If I had time for side projects I probably would use it. Bookmarked for when that time comes.
How many active users (uploading videos) are already? How you feel about speakers in other languages?
For speaking in another language, so far we don't have people do that. I am not an English speaker as well.
But if you think our platform is useful for you to simply document your own journey, feel free to say it in your own language :)
I really didn't expect this much attention. I will do an update on IndieLog in a bit.
For me, I will basically say anything from getting the idea, to doing some research, to implementing, then to demoing it. It's all about the journey!
I just fixed the 404 issue for the feedback tool. For the Github popup, I can see new users signed up via Github with no issue.
May I know what browser are you using? Is the popup blocked by the browser somehow? Thanks!
Actually as you can see, most of my videos do not have good lighting because I recorded them in the evening time after my little daughter went to bed. In the day time, I only got fragmented time slot so I can add things, whatever bug fixes or new features, little by little.
So blocking hours to do livestream would be hard for me as for now :(
This guy is a UX pro!
I dislike using social account because I might get suspended and lose the data and access to the website.
Not sure why it received so many downvotes