Update: Rudimentary landing page and feed are in place. I'm typically more MVP-oriented but I'm still thinking about the best way to store/pull data in such a manner will allow for trie autocomplete, which needs a list to autocomplete with.
0
0
0
Alright y'all. I'm going to start building in public. For my first act, I'm building a user-generated archive for keyboard enthusiasts. To run this for free.99, I'll be using Next.js paired with Supabase. It's my first time using Next, Supabase, and Typescript so should be fun😮
1
0
1
I like to listen to this plane crash podcast when flying (called Black Box Down). It’s like a free 4D experience 😀
0
0
0
Just finished a coding assessment for a job. I literally learned Python so that I could take this assessment. Just wanted to share this spread with y'all. It's so satisfying to me🤧😮💨
1
1
14
Just completed a 3-part, 3-hour coding assessment for this company after being stuck on one part for over 2 hours
1
0
2
Maturing is realizing and accepting that no matter how cool the Lego set is, it doesn't fit your decor aesthetic
0
0
0
Day 156: This is what a dub looks like. Used AWS to deploy a Postgres instance, which is connected to a server instance, which has just successfully returned a query via Postman. #100DaysOfCode
0
3
9
Day 98: Y'all mind if I flex real quick? I finally got this problem that I've been struggling with for the past 3 days. After hours of tinkering, diagramming, testing, and most importantly, THINKING! #100DaysOfCode
0
8
8
Day 89: I'm off today but decided to spend some time reviewing a toy problem that I didn't understand. If anybody is interested in practicing being the interpreter, here it is. The exercise is to predict which line the interpreter will go to next. #100DaysOfCode
0
1
2
For the following 3 months, my every waking moment has been spoken for several times over. Wish me luck, y'all. I'm about to go in. #100DaysOfCode
2
0
1
Day 82: When you try to absorb the concept of keyword this, pseudo classical classes vs functional classes, prototype classes, and prototype chains in one sitting😳 #100DaysOfCode
1
1
3
Day 78: I AM OFFICIALLY DONE W PRECOURSE AND CAN MOVE FORWARD TO THE BOOTCAMP. (If I didn’t finish, I would not be let into bootcamp) OH YEAH BUDDY LETS GO #100DaysOfCode
0
1
5
Day 73: Here is an update on what the "app" looks like now. Struggling to find out why the hell the second column of each div is varied but in terms of functionality, it's all there. Unfortunately, I don't think I'll be perfecting this due to the time crunch. #100DaysOfCode
1
5
3
Day 71: RIP to my "human timestamp" which I accidentally formulated and implemented correctly on the first try only to immediately realize that the project doesn't want me to use it. Have to delete but I will immortalize by sharing it here #firstTry💪😔 #100DaysOfCode
1
3
15
Day 69: What the half-baked Twitter project looks like so far. The bootcamp uses Cypress, which throws directions at you in the form of failed tests. I still need to add the time stamps but think I'll be done with the "individual tweets" part after that. #100DaysOfCode
1
1
9
Day 68: About to try to build this half-baked fake Twitter program as the next project. So far, I’ve only learned JS so this is about to be interesting😂 #100DaysOfCode
3
3
15
Day 61: Turnaround time to embrace higher order functions and refactor 5 HOFs: 24 total hours -- eating, sleeping, thinking, taking breaks, having conversations, and coding included. T-minus 29 days to pre-course end date. T-minus 4 days to next soft deadline. #100DaysOfCode
0
0
3
Day 36: Today, I learned how to create a BINARY SEARCH in UNDER 20 MINUTES!! (I struggled with the concept of recursion for 2 hours a few weeks ago, but that doesn't count as part of today's efforts) #100DaysOfCode
0
1
6
Day 23: Just took the technical assessment for this bootcamp for the second time. The litmus test is the 9th question and I was definitely stuck for a good while, but I was able to debug all 45732894 issues within my code. Now, we pray to the bootcamp gawds. #100DaysOfCode
0
1
5
Day 16: Synced with coach again. He said my prior weaknesses have been tamped down and he is very impressed with my progress. So much so, starting next week, I'll be coaching him instead. 😎
Just kidding. Jokes aside, I'm rescheduling my technical assessment ASAP! #100DaysOfCode
Just kidding. Jokes aside, I'm rescheduling my technical assessment ASAP! #100DaysOfCode
0
0
6
Day 14: With bittersweet sadness, I present to you, my POV vs my friends' POV. As a dubs fan, I'm down horrendous. As a fan of myself, I'm up 1. My only hope is that next year, after we (obviously) repeat, I can attend the parade as an SWE. Cheers, #DubNation. #100DaysOfCode
0
3
9
Day 13: Just wrote a function and debugged it within 10 minutes to access this object in an array in a value of an object within an array and printing into a string, along with other stuff. Each day, my strength grows. #100DaysOfCode
0
1
5
Oh, it's open source, alright. The site name says python but there are other languages, including Java, Javascript, C, and C++. pythontutor.com/visualize.html…
1
0
1
Day 8: Just spent way too long figuring out this problem, and even then, I had to use additional resources. I had a hard time getting back into grind mode after a trip to SD for my cousin's graduation. Tomorrow, I will be learning objects! #100DaysOfCode
1
4
8
Day 5: I did not pass the technical assessment. I’m bummed but I’m not phased. I have faith in my habits, discipline, and capabilities. I’m out of town for my cousin’s graduation, but the grind doesn’t stop. Today’s work involves learning about sets. #100DaysOfCode
0
2
4