#Flexbox30 Day 12 ✨
Here comes the fun part.This is the property that sets alignment along the main axis. In this example, the main axis lies horizontally - which means the flex-direction is set to row.
It's probably my most used parent property. You just choose the layout you like and BAM Flexbox automatically does it for you. And it's absolutely responsive. As your grow or shrink the window width, Flexbox will do the behind-the-scene calculation and ensure that layout is maintained. It's like one of those George Foreman grills, "you set it and forget it 🍗" -- this is not a sponsored post 😂
➡️ Follow @samanthaming to learn Flexbox in 30 days! 💖
These are some tips for people who are starting or wanting to enter this new world of possibilities 🙌
🔰Free Code Camp — http://freecodecamp.com (free)
🔰Udemy — https://www.udemy.com (a couple of courses are free)
🔰Khan Academy — https://www.khanacademy.org (free)
🔰CSS Tricks — https://css-tricks.com (free)
🔰Stack Overflow — http://stackoverflow.com (forum)
👇Let know in the comments what motivated you to learn programming 🧐 ...
Rate this setup 👇🤓🚀
Photo by: @satechi
The word productivity comes with a lot of baggage. For many years programmer productivity was measured in lines of code per day/week/month. There are several flaws in this method.
Let’s take a small game program called life and have two programmers of different skill levels write it in two languages: C and assembly. In C this is a 57-line program. The assembly language version is 97 lines. Let’s say that the C programmer takes sixty seconds per line (this is actually very fast) and the assembly programmer writes code even faster than the C programmer at the rate of one line every 40 seconds. It will take 65 minutes to create the assembly language version versus 57 minutes for the C version, so it took 15% more time, even though the assembly programmer writes 33% more lines of code per day.
Can we say that the assembly language programmer was more productive? If we measure by lines of code a day, she definitely was. If we measure by time spent to achieve results, no. Things get even less clear when you consider that the two programmers may be making different salaries because a programmer that writes fewer lines might also be paid less and therefore costless “per line”. Can we at least compare two programmers making the same salary, working in the same language? Let us consider this case: two programmers write the game of life in C. Captain Slow as we shall call him takes an entire day to write 97 lines of highly optimized code that takes 100 kilobytes of disk and loads in less than a second. Captain Showboat takes the same day, manages to find a way to use 970 lines of code where 97 would do just fine, to write a program that takes up one megabyte of disk and takes 10 seconds to load.
Now tell me: who is the more productive programmer?
More code does not automatically make a program better. Do we really want to incentivize people to write more lines than necessary? Bill Gates famously denigrated measuring productivity by lines of code by calling it a race “to build the world’s heaviest airplane” ...
Today I dived a bit more on Vue and the more I know it, the more I like it. However, for work purposes, I am going to learn React pretty soon from now. So I am curious: are there developers who use Vue AND React? If so, what are you guys opinion and experience in learn one after the other? Does it gets easier? 🧐 ...