Waking up when the dog wanna eat. Going back to sleep, waking up when I had enough sleep, making a coffee and reading Hackernews, Guardian and Reddit until noon. Having a brunch outside. Enjoying life and not worrying at all. ;)
I always wanted to be a programmer, but coming from a poor family and from Eastern Europe, it was not really an option in my twenties. Of course you learn programming from books and blog posts. It worked. However, I never gave up my dream, so I just ended up in a master program when I was 40. Finished it part time and got my Computer Science Master when I was 45. Also, having real world experience helped a lot learning the theory, because you already know how to use it in practice. ;)
To be honest, when I was in my twenties, I just wanted to work and being "serious" grown-up. Being student when you are 40+ is much more fun and you really enjoy every second of it. Exams are amazing, home-works are challenging, a lot of fun!
You don't have to do everything right now. The most important is that always do what you would enjoy, do things what you really like. Life is long!
Running sqlite in memory as a test db speeds up your test runner as crazy. You can do this if you use an sql query builder library, because it can translate your queries to the specific database.
Overlay is useful sometimes, however not always the best UX.
The main route of the url (example.com/page/subpage) represents the background page of the overlay.
You have two options. 1. Using further subroutes to represent the stage of the overlay if your framework supports it (Ember does) (example.com/page/subpage/form/step1). 2. Using query parans to store the state of the overlay (without the actual data of course): … subpage?overlay=form&step=1
Also breadcrumbs should always mirror the routes. Frameworks, libraries can automatically do it for you.
Routes are the fundamental building blocks of a webpage, so the hierarchy will be represented by the routes in the url. Proper frontend framework, like Ember.js, built on top of routes and building a UX focused web app is much easier with them.
It is quite difficult to work on large Ruby or Python projects; interfaces are not determined, and figuring out what's happening is painful.
Still, so many devs love it, and they wanna keep working with Ruby and Python in this way.
I kind of feel that experienced devs move on, and give up projects without types.