19 hour Ago:
I started this Hackathon. I started with getting the basics of NextJS under my belt building on top of my ReactJS and Javascript Knowledge. In the process I have learned Typescript as well. I am not yet complete with NextJS I have about 3 chapters left to go. However, considering the fact hat the main tutorial has wholes in it that force programmers to have to debug (about 2/3 - 3/4 of the work) I have decided to move on because the point of a hackathon is not just learning in practice but mainly to have something DONE. And well 19 hours of my 24 have been burned up leaving me with a mere 5 hours to go unless I push into a 48 Hour extended run.
Thoughts:
I will use the next 5 hours to get as much of my prototype laid out. Once the 5 hours is up I will assess if I have reached my goal of DONE. If there is more to do based on my documentation I will either push past and finish or extend 24 hours to both finish NextJS in one sitting and then finish the prototype. I would like to do this all with no debugging or worrying about roadblocks but when exhaustion hits it’s kind of hard to think around the problem as opposed to pushing through the problem. But, since I am 11 hours fully rested, I will make working around blocks a goal to attempt to maximize my next 5 hours. Let’s Do this!
Part 2 - 5 Hours Left
1:20PM
Changing gears to build page one of my prototype.
2:20PM
An hour in and I have read through the SDK update I think I will move forward with that makes start-up feel less like a 3 -12 month learning curve and more like a hackathon prototype reality.
Now comes the time for me to make choices on the tech stack I will use to move from here to the starting line with.
https://youtu.be/0hp2T4XGEqk?si=b7hgJHnbAuyZya0M
Auth.js
What: Auth.js, Authentication for the Web. Open Source. Full Stack. Own Your Data.
Why: https://github.com/nextauthjs/next-auth
HIPAA?: Not the library but the providers such as: authO, azure-ad-b2c, okta, cognito (AWS), google
3:10PM
Hackathon Meal Time! Eating like Queen. My hackathons be the bomb! OKAY! Eating and Drink Well! Take a look at my Steak and Potatoes Chef prepared to perfection paired with a Mezcal cocktail.
4:43PM
Getting my tech stack together with what offers HIPAA integrations for a track record of being prepared for internal HIPAA & Soc2 Type 2 Compliance.
5:45PM
All I have made headway on is reading and reviewing documentation especially when it comes to making choices that are HIPAA and SOC2 Type 2 Compliant. While I said was going to work around roadblocks and not through as much as I can compliance being a mainstay for development was not work around able.
6:33PM
There it is, I hit the 24 hour mark and what do I have to show for it? Company documentation and a CTO level tech stack strategy. If I was just an engineer I might have gotten more done. But as CEO and CTO I can’t ignore critical steps in the workflow and deliverable. Or can I? I wish I could just skip to the tangibles but building trust is part of our KPIs so it needs to be done in tandem and I am the only CTO and Engineer rolled into one human.
Side note, I do have my 11 year old helping with other keys tasks that are time burners that don’t require my mind or attention. So, that helps! However compliance is something I and my cofounder have to speak to and I as CTO have to provide them with the information they need making my job not just about production coding but also about strategy and c-suite communications.
Accessing Done and Level of Benefit
24 hours in I have nothing to use from an investor/user perspective but I have necessary knowledge and information. The goal was to have a prototype done. I don’t! So I am not done with this hackathon. But I do realize all Tech CEOs should do hackathons twice a year to understand what goes into what they request.
This 24 Hour Chunk is over but I MUST continue on to 48 hours no more documentation or learning just blind faith that I made sound choices from sound research thus far.
Let’s Continue to Hackathon #2 Part 3: Getting to Done.