186 karma · joined July 4, 2014
But it can be really helpful to think through all the states that the application can be in, something I often neglect. Not sure if I will automatically think through the non-happy paths, but it might help.
With a more fleshed out syntax, I could very well see myself using this. But I don't see myself using the Javascript / prototype part, if I actually to that I could probably just create a prototype in Vue.js, which then also would describe all the states. I would focus on the spec part and make that more powerful.
To work at home is not for everyone, it can be lonely, you might not have an extra rooms to use as an office. So with their still the employer paying for your office and for all the infrastructure you need.
A government site, lightning fast, try the search! No bullshit design.
- When doing my first lessons on ruby you are asked to read several tutorials. I thought, well I already learned that, but in every article I managed to find something new.
- It uses a multitude of other learning sources, does not even try to cover too much themselves. So you get to learn in very different ways. Reading good articles, watching some talks, downloading a repo where you need to write the code to make the test run successfully. Overall I feel, I get the best content, not because they write the best content (who could do that for all the subjects?), but it points you to great content.
- Contrary to many online tools, it forces you to work on your own system, which is a good thing.
- It often forces you to define the problem you are solving yourself. Many online courses make it too easy, you just learn coding. You don't learn to structure the problem.
- It also tries to give you a solid programming knowledge before going into web development. I really appreciate that. It's so easy to learn some angular or vue.js, then you... just need to fetch some data, ah how do I store data, oh and authentication and authorization, oh and... and quickly you get lost. I think it's is very beneficial to first get some solid programming knowledge before diving into the whole server / db / frontend stack.
So I can highly recommend this approach. BTW: even the creators are thinking of driving the course more towards JS (https://github.com/TheOdinProject/curriculum/issues/5633)
edit: formatting
https://cloudcannon.com / https://forestry.io/ / https://www.siteleaf.com/
With all of them you can set up nice content type templates and get your client to put structured content.
edit: formatting
different color scheme / different spelling LookUp vs. LOOK UP / different font /different relative positioning
Basically all they share is the "caret up" symbol and the words Look Up. Both are very common and hardly unique. It can happen that people independently get similar ideas.
We actually once designed a logo after we had redesigned an app. And the logo drew from the app design. We found out a few months later, that there was a hungarian company that had the same name, same concept for logo (which was typography only), very similar font and almost identical color scheme. It can happen. In our case you could blame us for not researching it, but similarities hardly mean stealing, especially if there are no really unique attributes...
edit: corrected syntax, formatting