I finally shipped a Chinese learning app I wanted for myself for ages at https://wenmoji.com/. Just never had enough time to sit down and code it end to end. Still need some improvements of course, but will slowly chip away on it. I use it daily/weekly myself now.
Highlights are that it completely free, no login required and works offline (once you "downloaded"/cached some files the first time around).
Have used it for a smaller project for a bit now and I really like it as well. Concise code and I can still map it to actual SQL in my brain.
What has been a bit non-intuitive for me though is the expression builder since the latest major version of kysely. When writing queries with `OR` conditions it always takes me a while to wrap my head around it again. It is also challening to make this easily readable with lots of dynamic `OR` conditions and I usually end up with a wrapper function which returns the array for the statements passed into the `or(` block. Could be improved in my opinion, otherwise a great tool
I kind of agree. Even now there are tons of third-parties dealing with the authentication for you, you will still have to write code to actually integrate with them and hook this up to whatever your user data is. I have written a few authentication layers now, and while I feel there are added benefits with third-parties, the amount of code I have to write is similar and strongly customised to the vendor offering the authentication solution.
Then there is also the problem you are facing and that is tooling not being language-agnostic across the board and you will have to re-implement similar patterns when changing the backend language or framework.
- The REWORK podcast (https://37signals.com/podcast/): Probably don't need lots of introduction here. Read the books in the past, but its great to actually hear Jason Fried and David Heinemeier Hansson to actually talk about those things.
Foxo is changing the way healthcare connects. We deliver powerful communication for healthcare teams, administrators, and organisations. Much more than secure messaging, the platform features clinical system integrations, patient centric workflows, and collaboration tools designed to reduce administration, enhance operational efficiencies and improve patient outcomes.
We are looking for a mid-level to Senior Backend Engineer (Node.js, SQL) with experience throughout the stack, be it frontend (frontend Javascript, we use Vue.js), infrastructure management (AWS, Azure, sysadmin) and just general fluency with common Web standards (HTTP, Websockets, WebRTC, etc).
You would join a small team and be able to use your skills across a multitude of areas to impact the healthcare/healthtech industry.
Foxo is changing the way healthcare connects. We deliver powerful communication for healthcare teams, administrators, and organisations. Much more than secure messaging, the platform features clinical system integrations, patient centric workflows, and collaboration tools designed to reduce administration, enhance operational efficiencies and improve patient outcomes.
We are looking for a mid-level to Senior Backend Engineer (Node.js, SQL) with experience throughout the stack, be it frontend (frontend Javascript, we use Vue.js), infrastructure management (AWS, Azure, sysadmin) and just general fluency with common Web standards (HTTP, Websockets, WebRTC, etc).
You would join a small team and be able to use your skills across a multitude of areas to impact the healthcare/healthtech industry.
Mandarin Chinese. I taught myself the basics (and a bit beyond) quite a while ago, but I am unhappy with either always having to start from scratch with every new tool I try or learn irrelevant things I am not interested in. Before I have seen your site I thought this to be quite a niche use-case, maybe it still is.
Really just want to scratch my own itch, but if I can also add value for others and make this a well-rounded product, even better.
Nice. I am exploring something very similar, but for a different language. I am curious if you considered making this a business (as in paid features/subscription based) and if not why not?
Foxo is changing the way healthcare connects. We deliver powerful communication for healthcare teams, administrators, and organisations. Much more than secure messaging, the platform features clinical system integrations, patient centric workflows, and collaboration tools designed to reduce administration, enhance operational efficiencies and improve patient outcomes.
We are looking for a mid-level to Senior Backend Engineer (Node.js, SQL) with experience throughout the stack, be it frontend (frontend Javascript, we use Vue.js), infrastructure management (AWS, Azure, sysadmin) and just general fluency with common Web standards (HTTP, Websockets, WebRTC, etc).
You would join a small team and be able to use your skills across a multitude of areas to impact the healthcare/healthtech industry.
Instead of focusing on a "cool" product, try to focus on companies/products which are solving meaningful or interesting problems (subjective to what you find meaningful and interesting of course) and then apply there. In my experience that is the best route of being happy and productive there.
Career progression is great, but there is an upper ceiling as long you want to still code. Only renumeration can still go up on some point.
8 years old. 30 minute screen time per day. Enforced via Google Family Link and Switch Parental controls. He has to finish all his daily errands before he is allowed to play (mostly like unpacking his school bags, do his homework/reading, etc).
We allow him extra time if he helps at home with things, either watching our little one or doing laundry or others which come up.
He is mostly playing Minecraft, Roblox or watches Youtube videos about those games or Lego on Youtube Kids. He barely watches any TV anymore, a movie every other week or some TV show every now and then.
If you intend to learn about stock trading for personal finance reasons you can follow a lot of blogs or podcasts in the FIRE (Financial Independence Retire Early) community. Some examples are the stock series of JL Collins (https://jlcollinsnh.com/stock-series/) and the Mad Fientist (https://www.madfientist.com/, the blog is a bit tax focused, but it goes well with the Podcast).
If you want to learn about active trading then you need vastly different resources and not really my expertise.
Just wanted to mention that there are basically two philosophies here and based on either what knowledge you want to gain or how much risk you want to take as an investor you will need to choose what to learn.
There are some breaking features from added in 3.7 which were not in the language in 3.7. Meaning code written for the newer Python 3 version might not work with the older Python 3 version. Most of those additions are relatively easy to fix though.
Code from an older Python 3 version should always work in the newer Python 3 version though (at least for 3.5 -> 3.7).
I am a Software Engineer at Wattcost (https://www.wattcost.com/), which creates a device and platform to read your energy consumption (even with older meters) and act on it. Eventually the platform is supposed to help you save energy in your home, which indirectly helps "fighting" climate change.
That being said, I do not believe that any single person or single company has the power to change things drastically into any direction. It has to be a joint effort of anyone or any organization on that planet. I am not seeing this actually happening (and often even see the opposite), so personally my outlook is rather grim as well.
First time around it was a very small one-man operation (just me). I think my main problem at that time was that I lost track of what I wanted to build because I fell in love with the underlying technologies too much. Typical case of when something new came around which seemed a better fit, I switched over. I guess I was still not experienced as I should have been at that time. In the end I was not sure what I was actually creating and lost motivation.
The second time there were different issues (and I was not alone). Product-wise we focused on the wrong thing. We tried to mostly build something which was already provided from our competitors (just improve it) and did not focus on something more original first which could have given us an edge. Financially we invested into the wrong things early on, even we did not need them yet (like marketing tooling). In the end we were simply out of fuel (money).
Third time is a charm and I am currently involved in a few businesses (most of them not even started yet) beside a full-time job. It looks like my current problem is that I want to do many things at the same time, so will have to reduce what to focus on soon.
The talk died down because it became a standard way of doing things now. It isn't something special anymore and the tooling has evolved to make it more seamless.
I am or actually was in a similar situation as you. I grew tired of developing software just for the sake to earn money (selling things, improving conversion rates, booking systems, etc.).
Eventually I ended up only applying for jobs which would enable me to work on something which actually could or will make a difference or I cared about. Was hired in the end (even found very few positions available in those spaces). You have to decide for yourself what things you care about to support and then find businesses or companies in that area which currently hire someone with your skill set. I admit there is a bit of luck involved, but should be possible if you are living not in the middle of nowhere or find remote positions.
Keep also in mind that this does not necessarily mean good pay (but should be decent at least) or a good company culture in the end. But I think this is the same risk you would take with any job.
I find it actually slowed down in recent years. Things finally seem to settle around the React ecosystem (yes yes, Vue has more stars). I also think there are way more projects which help you get started now without having to know all the tooling around it right of the beginning.
Regardless if you are working on a project and you have to deliver then simply stick with what you know. It does not matter what is the latest shiny thing out there and in most cases it won't matter in a few more years into the project as well.
If you want to learn something (new) in the frontend space though and also build something useful, the best approach I found is to only adapt one or two new things and have most of it build on what you know (using the 80/20 rule).
Highlights are that it completely free, no login required and works offline (once you "downloaded"/cached some files the first time around).