Phreaker00

I've long ago realized that going to sleep with a prepared mind (occupied by the problem) would often result in a working solution when waking up in the morning.

Once read an article that research showed that studying before sleep would increase retention 30% compared to studying in the morning. So at night your brain is actively working and you can take advantage of that.

A link to the article on Jetpack's website: https://jetpack.com/2022/01/18/backdoor-found-in-themes-and-...

I see that you have a two-fold goal where the former (build a functional prototype) is a means to an end (first actual users).

Perhaps having a functional prototype isn't the best next step to getting to your ultimate goal. Start by defining as clear as possible the task to solve and then determine the easiest and quickest way to validate your solution. If the 'pain' for your prospective customers is big enough that they're willing to pay for a solution, they're willing to accept limitations with a product in development that solves their core problem.

As a freelance developer for various start-ups I've seen this mistake being made a lot of times: jumping from basic idea validation to product development. Unless you can get a prototype built for free, development is an expense you should put off as long as possible. This goes for situations where time is less valuable than money, which in your case it seems to be.

They do, although AFAIK they recommend using the API. I recently moved from one to another and it only took switching out the library and a few lines of code, since most of them work very similarly.

Easily worth the added benefits of the API

I'm with this person. Let the professionals do the heavy lifting in terms of email delivery. You just worry about setting things up correctly in terms of DKIM, SPF records etc. The services mentioned all have dashboards to see the amount of spam complaints, so you can keep an eye out on that.

There are also some best practices to keep in mind when sending system emails like this, like not using that same system for marketing emails since they're more likely to get flagged as spam.

First of I'd like to mention that I'm not a certified teacher, so my advice comes from experience rather than formal education. I have however taught programming before and during my professional life as a developer had many instances where I had to explain a programming concept to a non-programmer.

With that disclaimer out of the way my understanding of the problem for people to understand something so abstract as functions, arrays and iteration is because they have no frame of reference. It's like remembering a word from a very foreign language after a week. My trick to help people absorb these abtract ideas is to use metaphores with things they're familiar with. So a function can become a robot that takes commands (parameters) and outputs an answer (return statement). Since you have the understanding of both a medical professional and a programmer you're in a great position to connect the two worlds. Also leave out the technical jargon; explain it in regular language. Together with a simple hand-made drawing (most people are visual learners) it should help make it stick.

Registered an account here to reply on this, so I hope it helps.