radihuq

I’m in a similar boat - made my first private server when I was 11 and loved tech since

Back in those days I didn’t know about VPSes so I’d host the private server on our family computer. Going to bed I’d keep the computer on and pray that the server stayed on for at least 3 hours before crashing. Worst feeling was waking up and checking the logs to see the server crashed 10 mins after you went to bed :’)

Check out this book called The 2 Hour Cocktail Party. I used it as structure to host a small get together last week and it was a lot fun!

I think as other comments allude to scheduling can be really hard so its a good idea to start sending out invitations 2-3 weeks in advance. Also don't be afraid to invite old friends - I reconnected with some friends I haven't talked to in 7+ years and it was great

I'm working on a project where I launch something every week this year. Here's my process:

* Create a notepad in your phone and throw any and all ideas in there whenever they come up

* Choose one to work on this weekend - whichever excites you the most

* When working on the project, be careful of scope creep. Accept your project will do one thing, and one thing only. Also accept your project will probably be crap - that's ok, you just need to something to start with so you can begin building on top of it next weekend

* Start with technology you're very comfortable with - whatever that may be. Then learn whatever else you need to learn as you work on the project

* Reuse code from past projects

* Force yourself to launch by the end of the weekend. This restraint will force you to be creative with your approach to building, and launching is always a great morale boost

feedback is really important because:

* it helps event planners improve their events

* gives event planners data points to attract more/higher quality sponsors

Imagine what your local dev meetup organizers could do if they had more funding (free arduinos? Fly out Woz? Hand out AWS credits?)

I designed the feedback form to be completeable in under 15 seconds, while giving good data to event planners. You don’t even need to provide your name. I don’t think it’s unreasonable for an event planner to ask 3 questions in order to provide some photos - photos you can use to build your personal brand, post on dating sites, cherish as memories, etc.

I think it’s a win-win situation for everyone

Haha good idea :) in the meantime feel free to follow along on Twitter (link in bio)

Haha yeah happy holidays, and thank you :)

Great insight into how it all happened! Thanks for sharing

> I have a sort spot for the folks at Twilio, because they were actually the ones who convinced us to do ads on Read the Docs originally, with a hacked together campaign way back in like 2015

This sounds really interesting! I find it fascinating that Twilio was willing to do such a personalized project with a relatively small company. Would you be willing to share the story?

Specific curiosities:

* Did you reach out to them, or did they reach out to you?

* Who were you working with there? (someone in a business unit, or someone in engineering?)

* Twilio is huge with (I imagine) big reputation risk. Why were they okay with being such early adopters?

* What was the process like working with them through this campaign?

out of curiosity, how big is the file?

EDIT: never mind, I see you answered this in another comment:

> The original film is around 10TB of mpeg2 1080p 25mbit/sec 25 frames per second.

> We later transcoded to h264, it now clocks in at about 2TB.

I like Supabase's SaaS model because I don't have to worry about infra work; I can just build.

Maybe eventually I'll have to explore other options, but for now my projects are still small enough where their feature set meet my needs. I think $25/mo is well worth it, knowing:

1. I can spin up a db & auth for a new project without having to spend hours on configuration & deployment

2. I can sleep well at night not worrying about one faulty line of code bringing down my entire app