ahodgkinson

I do try to read 25 pages a day, and I consider 100 pages an almost unreasonable goal. The main key to success is that you focus on the process, rather than the result. This means you should build the habit to read (or whatever you goal is) rather than reaching some specific goal. (you also need to waste less time on the internet and social media).

I would suggest that you keep a list of the books you read over the long term. Inspired by a friend, I started this in 2011 and and almost immediately wished I had begin this practice as a teenager. The list just contains the title, author, and the date I finished the book.

The statistics have been surprising and the trend has been gratifying. In the fist four years I read just over 35 books per year, and in the past eight this has increased in an average over over 60 per year. I don't feel I read excessively, it's mostly in the evenings, on vacations, and while traveling.

Low code initially works quite well until you hit the limits of the low-code framework. If you just need a throw-away proof of concept, or a personal utility, or the like, low-code solutions can be quite efficient.

However, implementing anything significant that's expected to be extended and improved, particularly when there are users that request changes, improvements and new features, low-code "is like climbing a tree in order to reach the moon". You'll will very quickly run out of tree and further progress becomes almost impossible.

To a lesser extent the same thing also occurs with web development frameworks, but the limits are less constraining and there are often mechanisms that allow you integrate your own code, that implements whatever it is that the framework doesn't provide.

Low code, frameworks, and "build it totally from scratch", can all be a valid solutions, but the right choice often depends on a bunch of specific considerations (technology, user & quality expectations, organizational capabilities & constraints, etc.)

My recommendation is to keep an open mind about alternative technologies and approaches, and to pick solutions that are appropriate for the environment in which they will be developed, extended and operated. And that requires experience, which you normally don't have in the early phase of your career (e.g. good judgement comes from experience, and experience comes from bad judgement)