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
Would love to have a discussion about your use case in our discord. We're constantly thinking about improving that part of our API as it's at the heart of many things.
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.
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?
> I am exploring something very similar, but for a different language.
Which language if I may ask? I'd like to branch out into other languages too in the future (preferably into something that's easier to parse than Japanese), but since I'm nowhere near done with Japanese at this point it's probably going to take many more years until I do so.
> I am curious if you considered making this a business (as in paid features/subscription based) and if not why not?
I do already have some Patron-only features. For example, normal users get access to two different voices for the audio files, while Patrons get access to four; Patrons get early access to work-in-progress new features, etc.
But inherently I'd like to keep the base product, and in consequence the major essential features, free. It's probably a horrible business decision, but I recognize that not everyone can actually pay, and I want those people to be able to use my site too. I was once poor too, so I know how it is.
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.
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.
I look into this, and upon submission I found that you must be an Australian residence. there a check box with the text 'I am a permanent Australian resident and do not require a visa permit to work', which is required from you to check.
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.
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