First thing we need to do, before we even start writing a single line of code, is to plan. Plan our MVP. How it’s going to look? What features it will have? Wha a user can or cannot do? Will there will be somethings a user can do without sign in? How our API will look like? How our Database Architecture will look like? How the client and server will communicate?
Every operation need good intel, and good intel is hard to find. Or is it? OSINT (or Open Source Intelligence) is the operation of collecting and analyzing information about a target from various sources. A lot of times you’ll see the terms “public” or “open” sources but let’s be honest here, this is false and that’s why I wrote various sources. This is not to say that hacking to someone and steal his data is OSINT, because it’s not.
This is the start of a series of posts to build Twitter like website. But why did I even want to do that? Because I saw a gap in software engineering blog universe about bring software to production level. Nobody explain what we need to do it and didn’t do it with the reader, together, while keep it as simple and stupid as one can so even the most junior software engineer can understand why and how to get his next project to production.
I’m really excited for this! Don’t ask me why because I can’t explain it. This is not the first time I make a new design for this blog, it’s actually the fifth time! and yet, I feel this is the best one yet. It have everything I ever wanted in my blog. 1. New Design I can’t even start to describe to you how much I feel this design is perfect for this blog.
Creating Jekyll progressive web apps has never been easier! 1. Jekyll Starter Kit First thing first, for those of you who has yet to hear about the Jekyll Starter Kit generator, it’s a Yeoman generator for creating Jekyll projects or really Jekyll static websites. It’ll create for you the default Jekyll website template, with all the best practices from Google Web Starter Kit, all the things you need for your website to be a PWA (progressive web app), and some more cool stuff.
A tutorial for a real world docker use case. Recently I read a lot of articles about load balancing applications with Docker, Docker Compose, and Docker Swarm for my work. We have a couple of hundreds of instances and we need to manage them and do load balancing between them. There are a lot of articles about this topic, but sadly the use case they present is quit simple and because of that they really don’t help.