Every Developer NEEDS To Know 12-Factor App Principles

[@lalithmahadev5027]

12 factor app in 12 minutes.Precise and Concise.Noice!!!

[@amirghandehari3003]

I think what is really good for people like me is a project review.Currently I'm working alone, not in a team. And as a junior full stack developer, I feel I need to get familiar with PRs and what rules apply to an application When written by a team or in a company. I also Feel like github itself doesn't recognized as it should be. I would love to have a review about such things from an experienced developer. Like how much important is CI/CD and github actions or how deep should I become in algorithms and data structures or is it better to learn a new technology. After all I learned lots of things from this channel. Thank you for your content.

[@2121jwill]

I've been doing web development since the late 90s and this is the first time I've heard of 12-factor. It has some overlap with other "manifestos" I've run into over the years. I think it's important to think of this as a gold standard - if you can implement 6 of these then great! If you can only do 2 then great! The most important thing is to keep improving. Great video!

[@hlubradio2318]

Thanks. During my software engineering courses in college we never heard of these but yet, my apps were well crafted if that's the correct word. Thanks for giving me a reference to rely on.

[@bluesteel1]

Nice job reading the 12factor doc

[@cs31296]

amazing explanation, it'd be great if you could make a video of an app that uses all these principles in AWS with CICD, Containerization

[@laser7861]

We followed many of these principles, but did not refer to them by name. A couple of these are interesting: 1) stateless - most of my time was spent building stateful apps with session data stored in memory. I usually saw stateless as an architectural choice rather than a best practice. 2) Dev/Prod disparity: We try to keep as many things similar as possible, but licenses and costs don't permit that for some things (e.g. monitoring tools). I wonder if there is empirical evidence of "it costs more", and if so what is the data?

[@PatrickMwachugu]

Awesome review.. Learning alot from this channel.. You should consider forming a group where we can discuss in depth various software development related topics..

[@astronautMM]

awesome and short. Thanks a ton

[@colbr6733]

In my experience, these are good principles but also depend on the organisational structure involved. Especially in large projects where your deliverable has to meet a specified requirement. Using these principles to check what is appropriate within your team is a good starting point. Often this can bring about a review of what is needed, as needs change and managing costs should also be a factor.

[@vaibhavdikha]

Saved a lot of time thanks !

Thanks for this!

[@markeggers8356]

My only issue is logging. That should be configurable per environment (attached service) much like a database or SMTP provider is.

[@aryanrahman3212]

Really good explanation but didn't quite get the reason behind the last point.

[@AP-ib7rf]

thanks!

[@hlubradio2318]

I have never heard of them

[@mertfromhell]

i hate being sober

[@salahammar1521]

Ooh

[@Snooze_Addict]

Is it even worth it to learn how to code anymore? Ai will cause even more layoffs. 😢

[@davebudah]

Layoffs have been happening for decades, don't lose heart

[@jtr-code]

Definitely still worth it! The important thing is to learn to utilize AI as a developer

[@Spaz667]

It is absolutely worth it. AI coding has become much more reliable than previous years however, it’s only as good as the prompts that are given. I’ve attempted to utilize it for troubleshooting a bug in an application and the rabbit hole it put me in was hilarious. Thankfully I ended up figuring it out myself but I can only imagine the poor dev that would follow AI blindly.

[@H4KnSL4K]

You've got this auto-micro-skips thing set up that is really annoying. I don't normally notice this on your videos, but it's anti-helpful. Check your settings?