full-stack-open VS littlelink-server

For full sack you'd be better of with https://fullstackopen.com/en/ than with Brad's course.

You can start learning by doing, follow https://fullstackopen.com/en/, give 3-4 months on this and start tackling problems from Neetcode.io. Make sure to mark your projects public on GitHub and highlight it on your resume. Lastly, connect with people on LinkedIn, short down the organisation you’re interested in and send connect request to their employees and ask for referrals. Good luck.

Initially, I debated between Kotlin, Flutter and React Native. Having some experience with React from an excellent course, as well as building an internal tool for my job in React, it seemed like a great idea to try React Native. This came quite naturally, as Native is very similar to React, with setting up a screen being as easy as wrapping some content in a component. Other components also baked into react native such as , and make prototyping a breeze. The CSS-like styling is also simple to use, making UI design and testing easy enough. For building and deployment, Expo was a dream - fast reloads for previewing, the ability to flip between web and android via hardware or an emulator, and even handling building of APKs through EAS - perfect for this small project. Expo also has it's own set of well-documented packages available for use, making things like using Android's file system for a built in SQLite database easy. Homepage Simple - two buttons and a navigation container dealt with by react-navigation. Combo List The first portion of this was setting up the SQLite database. This is split into two parts: the user and built in databases. The user portion just generates a .db file, and contains all of the CRUD operations as separate functions. Different buttons are linked to these so you can create combinations, read and output them as a list, update their names and delete them. This is also where import/export is handled - which simply uses the expo filesystem to push out and pull in .db files, replacing whatever was there before. The built-in database is much simpler - it uses filesystem to download the built-in DB from the app's assets folder, then uses a basic SQL query to print them out. Workout Setup This is where the user sets up their Workout - in case you hadn't guessed. This is simply a set of buttons, toggles and text boxes - each parameter set here is then pushed over to the Workout screen. Workout Most of the logic goes on here. A couple of timers tick down, with the round timer being switched with the rest timer as it hits 0, and vice versa. The combination visual works by putting the selected database combinations into an array, then using a random number to select an index in the array. The rest is quite simple - a pause/play which will stop/start the timer ticks, a skip feature which allows the user to instantly set the current round/rest timer to 0, an extend rest function which allows the user to add 10 seconds to the current rest timer, and a cancel workout button which returns the user to the set up page. Future Aside from the additional features already mentioned, I don't think this app needs to be overcomplicated - it does exactly what I needed it to and I can't see it becoming obsolete anytime soon. However, the code is all open source - if anyone has ideas, I'll continue maintaining the repo, looking at PRs, etc. Depending on how large the user base grows, hypothetically, it would also be cool to have a hub for uploading combo databases. This could even separate by sport - boxing, karate, TKD - anything that involves drilling could make use of the system. If users were able to head somewhere and grab, say, a largely populated advanced boxing database, that would be very cool. Another interesting idea for me is logging - having the app log how many workouts you've done, display statistics, maybe even some sort of achievement / badge system. Gamifying anything always turns out to be a great motivator in my case, and I'm sure it wouldn't be a feature that goes unappreciated! All said, please feel free to poke around the codebase and make the app work for you however you'd like to :) The GitHub does have a few releases attached where you can download and run the APK on your own Android device! https://github.com/JJB9922/MuayThaideas/releases Acknowledgements Thanks to @menilek for giving the push to attach a blog to this project :) Do follow if you're interested in blogs from an experienced full-stack engineer!

I completed the Fullstackopen MOOC from the University of Helsinki up to part 7. Now, I've created a little portfolio to showcase my learned skills. Firstly, what's your opinion on that?

If you’re still struggling with that then try fullstackopen. Really good and easy to follow. You build lots of projects like Odin but it’s more guided.

Take a look at the exercises of the full stack open course from Helsinki University (e.g. recommendation). If you get stuck, there are multiple github repos with the solutions, so reading code from others until you reach your own solution can be a good exercise.

There's cs61a:

https://cs61a.org/

(I'm doing the Denero version: https://cs61a.org/denero.html) If you pass the command-line flag: `--local` you can run the tests without triggering the submission system.

accompanying book:

https://www.composingprograms.com/

The moocs from University of Helsinki are really good. Here's the current Python one:

https://programming-23.mooc.fi/

And there's their web dev course, called Full Stack Open:

https://fullstackopen.com/en/

If learning web dev, you can't go wrong with The Odin Project:

https://www.theodinproject.com/

You can use Littlelink-Server to create this

Hi, I wanted to share my little Homelab with you. Been following r/homelab for a week since I was not that aware of the awesomeness one can find in reddit :) Really appreciate the great community! The overall theme of my setup is power efficiency and low cost components since im still studying. I am really glad I went this route with current electricity prices, especially in Germany. A rack isn’t an option unfortunately, because our flat only has around 35qm² (376ft²) and we don’t have a usable basement or cabinet. So I decided to grab a Kallax shelf from our local Ikea to use it as my homelab shelf :) From bottom to top: “BigIron” - MoBo + CPU (built-in cpu): Biostar J4105NHU with Intel Celeron J4105 - RAM: 8GB DDR4 - PSU: Inter-tech Argus 250W Flex-ATX (soon Fan-Swap with a Noctua fan, the original fan is horrific) - HDD: 4x 4TB WD RED - Case: Inter-tech IPC SC-4100 - OS: TrueNas Core Dell Latitude 6410 - Had it laying around so I decided to remove to the monitor (headless mode ;) ) and install proxmox to run my docker containers and 1-2 linux vm’s Synology DS216+II - My first entry into the NAS and homelab world. Because I ran out of storage I decided to build BigIron as DIY. After the migration is complete, the Synology-NAS will be my local backup. Ikea Tradfri Gateway - We have some smart-lights in our flat, its just the gateway to address these. TP-Link TL-SG105E - I ran out of ethernet ports on my router, so I bought this from amazon. It’s cheap and doing the job. Fritzbox 7490 - The router our ISP provided. Nothing special, but will do for now. The services im currently running: - Littlelink (Link to Repo) as a little self-promotion for future employers - Pi-Hole - Heimdall - Portainer - nginx Proxy Manager - Bitwarden - Uptime Kuma - Photo Prism Future Plans: - Switch cloud-backup provider to Hetzner (currently just a Google Drive 2TB plan, oof) - enforce security of services that are exposed to the internet through nginx proxy manager. - Replace the Latitude through a SFF-PC like a NUC or smth. We entirely switched to Apple M1 Macs, but a somewhat decent Windows VM would be nice to have, just in case. - Cable management, a lot of it. xD If you want to know more, just ask me anything!

Also if you need docker or server-side rendering https://github.com/techno-tim/littlelink-server