curriculum VS notes

The landing page was built using HTML/CSS and some Javascript. How have I been learning this? A mix of AI (Claude, ChatGPT) and learning how to create a site by going through the foundational section of The Odin Project. I will also continue to go through this course and the React portion.

There were frustrations and compromises and victories, but little by little I can see my progress, and I still enjoy the act of overcoming these new challenges and learning more and more. Each day is another little lesson. I look forward to continuing with The Odin Project and the next challenges, but in the meantime I must return to looking for my alternance (apprenticeship) and maybe a small personal project before launching into the next part of the curriculum.

The Odin Project: With its hands-on approach, The Odin Project guids through everything from basic HTML and CSS to full-stack development.

The Odin Project (https://www.theodinproject.com/)

The Odin Project The Odin Project offers a full-stack curriculum for aspiring web developers. With its project-based approach, you'll gain practical experience while learning HTML, CSS, JavaScript, and more.

TheOdinProject

The Odin Project - Free, open-source platform with a curriculum focused on JavaScript and Ruby for web development.

I'll throw in a vote for teaching yourself or using free resources and communities. Even if you go down the bootcamp route it is going to take a lot of self motivation and work outside of the bootcamp / afterwards in order to become job ready. Or at least do this to start with to make sure you like it.

I did this myself a few years years ago over lockdown. I had a lot of down time and worked on teaching myself web development full time 5 days a week for about a year. I was then able to land a job at a FAANG company through an apprenticeship scheme that they offer in the UK (I'm not sure if these kinds of schemes are available in the US) where I stayed for a year and a half and I am now working for a startup in a position I found through connections I made at my previous job. At the time I did have other offers for non-apprenticeship roles at other companies so don't let the absence of apprenticeships put you off if they aren't on offer in the US. The job market was definitely better when I was applying for my first job so the process might be more drawn out now. The main resource I used for self teaching was The Odin Project (https://www.theodinproject.com/). I also did a batch at The Recurse Center (https://www.recurse.com/) which was a great experience in general, especially for getting some hands on time working on projects with other people. I would say be curious, reach out to people who are working on things you find interesting to ask them for a chat and just persevere with the applications as you will definitely get a lot of rejections.

One more thing (might be UK specific as well) but I would check to see if there are any government funded bootcamps you might be able to get a place on. I know multiple people in the UK who got the job center to pay for them to do a bootcamp while they were on universal credit and now work in the industry.

So I have been learning how to code and broadly development since 2020, during the Covid-19 lockdowns, beginning with the classic triple threat of HTML/CSS/JavaScript, adding into the mix a dash of Python and since returning to live in France 2022 have committed to The Odin Project web-development program and happily began my full time formal learning with Ada Tech School in 2023. Now the search for my 12-month-long apprenticeship (Alternance, en français) begins, as well as continuing my self-study and side-projects.

Thanks! I'm not 100% sure about this, still hearing feedback from people on both ends. Some reasons for the switch would be:

1. File versioning

2. Easier self-hosted syncing

3. Better data portability (although we already support exporting to .txt)

I would love to hear counterpoints. Currently, SQLite works pretty well, and our custom database is pretty simple (plus, our database code is also open source[1]).

[1] https://github.com/nuttyartist/notes/blob/master/src/dbmanag....

Plume is actually based on my open source note-taking app Notes[1]. You can already get it on Flathub, Snap Store etc. Notes uses just a simple plain text editor while Plume has a completely revamped block editor that I built from scratch. That parts of Notes used in Plume will remain open source (per the MPL license) but the rest of the code will be closed source. At least for the time being.

[1] https://github.com/nuttyartist/notes

Plume is built on top of my open source note-taking app Notes[1]. Since Plume is based on Notes, I'll of course comply with the MPL license and release all existing files that were changed (and must stay MPL licensed).

But I recently discussed my reasoning to go close-source with Plume[2]. I've been working night and day (every day) converting 4 cups of coffee into code for the last 4.5 months to create Plume. I don't want to risk not being rewarded sufficiently for it. But, I'm 99% sure that I'll either open source the core block editor or the entire app in the future.

[1] https://github.com/nuttyartist/notes

[2] https://news.ycombinator.com/item?id=38584960

2. Each note is just a simple plaintext in the underlying data (although currently stored in a database, but in a future update we'll convert the database to an arbitrary folder).

So you can create beautiful and advanced notes, easy. In a non-proprietary format (when that future update arrives). All while using a resource efficient and fast software that is cross-platform.

[1] https://www.get-plume.com/

[2] https://www.get-notes.com/

My Noets app[1] editor is built on top of the Markdown syntax of QOwnNotes.

My new app Plume[2] is built on top of Notes but features an advanced block editor and a new design.

[1] https://www.get-notes.com/

[2] https://www.get-plume.com/

Indeed, I want this feature badly myself to create wikis and such. There's an open issue[1]. We'll definitely implement that some day.

[1] https://github.com/nuttyartist/notes/issues/431

I mostly disagree. Like you said, Qt is the best native GUI toolkit available today. And that is a hard achievement. There are many tradeoffs (some you pointed out) but the open source community seems to find a way around those limitations. There are thousands of open source libraries you can plug-in into your Qt app to overcome many of its limitations (although some remain, like how can't we still not easily change caret/cursor color of QTextEdit??).

Unlike you, I like the direction where Qt is taking. I think QML and Qt Quick are great. I just implemented a feature in my note-taking app that turns Markdown text into Kanban board using QML and the experience has been great (https://github.com/nuttyartist/notes/pull/574). I'm planning to continue transition from QWidgets to QML/Qt Quick.

I do worry of the continuous friction with open source development and hate the online installers as well. I can recommend this useful tool https://github.com/miurahr/aqtinstall that allows you to easily download prebuilt Qt binaries. I hope they can revert their approach on that.

I beg to differ, QML is great. I'm implementing a feature that converts all tasks in Markdown editor to a Kanban view (written in QML) and it's been so easy to do. Work in progress GIF here: https://imgur.com/a/sZNHnp6

And it's even crazier that most of it compiles to C++. It's so fast to develop with it, and runs so fast.

BTW, source code here: https://github.com/nuttyartist/notes/pull/574