makstaks

@armatav why should this post be flagged? The recommendation was very helpful to me and lets me compare two solutions.

If you are interested in ReactJS dev, here's a great course: https://www.udemy.com/course/react-the-complete-guide-incl-r...

Thank you for this library, I am looking forward to reviewing your work. I didn't want to use a framework (like hapi or express) to achieve something similar.

I'm not sure if I understand your question. What do you mean by "web scripting framework?". NodeJS is a server-side runtime. It just so happens to use Javascript as the programming language. Its strength is handling async event-driven requests, so given that AWS Lambda's strength is existing within an event-driven architecture, it's a natural pairing.

How does one do the third-pass? "re-create the work" it doesn't seem feasible because you would need some financial and human resources to do so.

When you say "learn", I am assuming you mean getting to the point where you can apply the knowledge. It sounds like the problem you are trying to solve is to decrease this "learning" time and not so much increase your retention of information.

I haven't done any kernel development, I'm assuming it's highly technical and you get can't skim through materials.

I think if you are able to painstakingly go through technical documentation, that is a special ability. My guess is it probably sets you apart from many devs.

Getting a big picture is a great idea as you build a mental map of important topic areas to cover and gives you some form of mental motivation or direction. Better if someone has already done this, so you can save your time.

For more technical subject matter though, those fine details make a big difference when trying to apply it. I don't know if there is a way to avoid doing that. Skimming things I find wastes a lot of time because when you try to actually build you get stuck because of some important detailed buried on page X paragraph Y.

Some other areas of development aren't as intense so you can get away with not knowing everything and be able to build something pretty impressive.

For dense technical information, my method is to take research-like notes, cross-referenced in my note-taking app and improve these notes over time. I save time by not re-learning and re-searching supporting materials.

This is a great idea. I'm not sure about the other major cloud providers, but AWS has the AWS CDK which allows you to use TypeScript, Python, Java, and .NET to create your cloud infrastructure via code. The ability to generate cloud diagrams from AWS CDK code would definitely would be awesome. Hopefully, your work gains transaction, then I can envision other devs writing adapter code for your project.

Not knowing much about your friend's service, it sounds like the value of his product is "heavy processing". Therefore, I also would have included scalability as part of a v1 deliverable and wouldn't consider it as an optimization task. Great that your friend identified that.

I'm rather confused by the misuse of the term "AI", to the point, I no longer know what is true. I thought true AI needs to pass some sort of test that demonstrates real intelligence? So, did the Singularity event happen already and I didn't notice?

I started using Localstack and wanted to make it work, but found myself using a sandboxed AWS account more and more over time because there was less friction.