154 karma · joined July 23, 2019
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
* 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
* 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
You can text updates on things you get done throughout the week, and then generate a (.PNG) text conversation with Elon Musk stating what you got done
Just a fun project, feel free to poke around!
[0] https://twitter.com/TechEmails/status/1575598387335901190
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?
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.
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
IMO don't use Medium as its tough for content exploration as a user.
I think the best option is to setup a static site generator using whatever tool works for you - ideally a tool that allows your users to search for blog posts, and filter posts by tags.
I would probably start with Wordpress to quickly get started, and explore other options as needs arise.
I received 7 inbound emails, some more personalized than others. 1 Twitter DM.
Surprisingly, I even received emails into the last week of February.
For context, I'd call myself an intermediate full stack JavaScript developer. I don't think I did anything special; here was my comment: https://news.ycombinator.com/item?id=30173273
Mix that with him being popular, well connected, and generally well respected, I can see why big names in tech would be eager to go on his podcast
Here though, I'm not so sure - maybe they try to sell intellectual content creators on a Gumroad alternative via Stripe Checkout? Seems like too small of an opportunity to be worth pursuing
Edit: honestly, could just be a recruiting play. IMO they have the brand "our founders are incredibly intellectually curious, and some of the smartest people work here", and this acquisition could help strengthen that brand. I think this could be the most plausible reason.
Remote: Yes
Willing to relocate: Possibly
Technologies: React, React Native, JavaScript, TypeScript, NodeJS, GraphQL, ExpressJS, PostgreSQL, TypeORM, AWS, HTML, CSS, Bootstrap, Storybook, Serverless
Résumé/CV: https://radihuq.com/resume
Email: radihuqHN@gmail.com
---
I have 2 years of experience working as a Full Stack Developer. I enjoy building web applications that have a business use-case. My ideal role will have me working across the full stack (from frontend, to backend, to devops).
* At my last job I helped build two cross-platform mobile applications from scratch using TypeScript, React, React Native, and react-native-web. We used GraphQL, TypeORM, PostgreSQL in the backend using Serverless architecture, and AWS to deploy.
* Currently I work at a startup overseeing the technology infrastructure for multiple medical clinics across Ontario, Canada.
* On the side I'm building https://engineeringblogs.io - this project scrapes & indexes thousands of articles from tech companies' engineering blogs, and provides a search engine interface for you to search across them.
I'm open to any opportunities that allow me to help build web applications.
The best way to reach me is by email (radihuqHN@gmail.com) or on Twitter (@radiunhuq).
Here's what I'd recommend:
* If you could build anything, what would you build? Have a clear vision and make sure it excites you. It could be an app, it could be a game, it could be the next GPT-3, it could be a calculator. Whatever the case, this is your north star & what you should work towards
* Forget about tutorials, focus on your building vision
* Seriously, don't overthink it - just start building
* Start small. Break it down into layers and tackle each step as you get there (eg. first I will create a webpage, then I will figure out how to share it with my friend, then I will make the webpage do something, then I will make it look pretty, etc.)
* When you get stuck, Google the problem. Don't think anyone's judging you, literally ALL 100 million developers before you Googled "javascript how to add another item to the end of an array"
* If you get stuck, have the mentality that GIVEN ENOUGH TIME you will find a solution to the problem
* Programming is a creative endeavour. If you don't know how to move forward, step away and take a break. You'll likely come back with 100 more ideas to try
* Focus on your vision. Work towards building it. I promise in a few weeks you'll be amazed at what you've managed to build
EDIT: they start talking about it at the 7:00 mark
This conversation is inevitable, but would it be happening sooner or later if Android users had access to Clubhouse?