Initially, boilerplates were free and were called scaffolding; things like create-react-app were trendy back then.However, we have seen major successes in the boilerplate market, and it’s tempting to enter it.Because of these, I decided to go deeper into understanding why startup founders should use SaaS boilerplates.Here are my top reasons:- Speed - Cost-effectiveness - Standardization and...
Some of the jobs are featured from different job boards, and for the jobs that are not available, we will do well to remove them soon.
Thanks for checking out;
Honestly, I'm short of words to express how grateful I am for your feedback and encouraging others.
I'm glad you found the content useful.
It's Solomon Eseme, the author of the piece.
It's Solomon Eseme, the author of the piece
It's Solomon Eseme, the author of the piece.
When you say the first two paragraph. I'm hoping you mean:
"This is the most comprehensive guide on Docker online.
In this docker tutorial, you will learn docker from scratch to an advanced level starting from the concept of containerization to Docker Compose in Docker."
1. "This is the most comprehensive guide on Docker online.
This is how I start all my Definitive guides and it gives you a sense that I will try to make the guide understandable and easy to read by using the word "comprehensive"
2. "In this docker tutorial, you will learn docker from scratch to an advanced level starting from the concept of containerization to Docker Compose in Docker."
This is me letting you know that article is a journey from "Beginner" to "Advanced" meaning, it's long and you can skip to any point. That's why I separate them into chapters.
Thanks for your feedback.
It's just optional to add it or not.
https://docs.docker.com/compose/compose-file/03-compose-file...
By the way, this is an easy fix and thanks for pointing it out.
I'm Solomon Eseme, the author of the piece.
I don't think it's entirely through that the article is misleading.
The article intention it to take readers through a journey from beginners to advanced level, using storytelling to explain technical concepts like containerization and Docker.
If you get to chapter 4, Look the brief where you see the image, You will see all the listed topics that will be covered in the Advanced Part of the article and It will be too long to include them there.
I even indicated with "Let me know in the comments section. I will share it with you."
Then I moved to discussing "Docker Compose" the next topic will continue in the advanced guide.
Docker documentation is great. But it's not every beginner or even advanced developers that understands Documentation at first introduction to a technology.
Thanks for your feedback anyways. I'm still learning and will improve as I write more.
Thanks for your feedback. It's Solomon Eseme, the author of the piece.
Honestly, I don't see any wrong with the statement "Nevertheless, Docker runs flawlessly on all major operating systems such as Mac, Windows, and Linux with Mac being the easiest."
Docker runs perfectly in Windows, Mac, and Linux
Maybe I could have been more clear here "...Mac being the easiest."
The installation of Docker is more easy than other OS, that's what I wanted to communicate there.
I have personally installed Docker in all 3 OS and I discovered Mac to be the easiest. If you think otherwise. Then I respect your opinion.
When it comes to using Docker, of course, every developer should enjoy using it in Linux since it all command and the Terminal is Number one tool for developers.
Thanks for your feedback.
Some of the things you listed as things I didn't touch on the article is true. I didn't cover those.
But this article is for beginners and I also indicate that there's an advanced content coming up on it.
For example, when I mentioned Volumes in Chapter 4, I added this "We haven’t discussed Docker Volumes in this guide but you can visit the Docker Content Hub for more advanced topics like Volumes."
To let readers know that there's an advanced topic that covers other concepts.
I even indicated it at the beginning of chapter 4 "Let me know in the comments section. I will share it with you."
Talking about common pitfalls for exposing ports. I didn't go in depth into PORTS because that knowledge will be too overwhelming at that point. At least, you should know how to dockerize an application before trying to secure it.
I have an Advanced Docker content coming up that covers Docker Security, that's where your feedback will be very help which I appreciate by the way.
Lastly, I never encourage storing secrets openly and committing it to git. That is a bad practice in software engineering.
In development, we all store our secrets in an .env file (if you use JavaScript) that is the standard but when deploying or on production, you move your secret to somewhere safe.
So that's the same concept for the article, while building your dockerized app in development I created the common.env file to hold the secrets in my development. During production, It will be secured according to standards and best practices.
I may not have indicated it like this doesn't mean I'm encourage the wrong thing. Beside for a developer to consider learning and using Docker, the developer must have been developing and deploying apps for a while and should know the best practices with SECRETS.
Next time, I will consider indicating it, Thanks to your feedback.
I'm Solomon Eseme, the author of the piece.
Seems like I need to improve more on my storytelling skills hahaha
The concept of "Definitive Guide" on my blog is not to write "How to" guides or general overview articles.
It's to use personal experience and storytelling to write articles that are personalized and interesting to read while tackling difficult concepts like Containerization and Docker.
I could understand for the length. But if it's interest and you're getting value, length won't really matter, will it?
I may have gone off point at some point but of course, I'm always learning and improving and your feedback has been helpful.
However, I don't think asking people to avoid the piece is a good idea. If you notice a few mistake based on your level of knowledge on Docker doesn't mean others do.
They need grassroot beginners content to get them started.
My name is Solomon Eseme and I'm the author of the "Docker: The Definitive Guide in 2023"
First, I want to personally thank you "Idoubtit" for reading through the piece and sharing your personal review.
I will only try to share my views here and hope it helps clarify things a little.
Firstly, the intention of target audience of the book is for beginners to Docker and as your progress in the chapters, you can see some other concepts that intermediate can benefit from.
Secondly, I also understand that the book is long and a lengthy book sometimes could contain unwanted parts or noise but this is because of my style of writing. I want to tell a story when I'm writing a "Definitive Guide". I don't want it to be like an "How to" guide or "Overview of" kind of article.
Thirdly, when you say "copying from Docker commercial" that's not entirely true because you could see that I give proper credit to every source and I didn't go in-depth into some topics because at that stage in the reader's mind, It will be confusing since the target is beginners there's no need talking about Docker Swarm or Networks at that point.
Next, the comparison part is simple and straightforward, my intention wasn't to show comparison but to inform the reader that there are other containerization implementation out there and these are their market share. Coming from the point where I said that Docker is the most popular, the Market share diagram helps compliment that.
Of course, I understand that the article can be improved, It could be made better and also, I could be better in writing and passing points across.
I also, I understand that the title "Docker: The Definitive Guide in 2023" could be misleading. But if you look at the chapter 4. I indicated that there is an Advanced Copy of this book.
I even said "Let me know in the comments section. I will share it with you."
I'm currently working on the Advanced part that will include everything I have listed in the chapter 4.
I hope this helps clarify somethings. I'm still learning, I'm still improving and I really appreciate you for giving these feedbacks.