260 karma · joined August 26, 2015
I never used the GUI. It seems really complex for what we decided to be our workflow. Git is a complex software that can solve complex contexts, but you can limit your daily workflow to a few commands.
Standardize everything, including the costs, seems like the end of creativity. However, creating a massive checklist that makes the user choose between services and, step by step, simulate final costs (which will include computation, task management, monitoring, customer support, etc.) is a titanic job that could change within the next generation.
You seem to do a lot of retrospectives right now. That is probably a necessary skill to be a good developer. You are questioning your solutions, looking at other developers' works, understanding that they are doing a better job. I can only say congratulations to you about that.
Do not focus too much on the technology or in what you know at the moment about the technology.
As a first step, you must answer if you want to be a better developer in a specific language or a better professional in one particular industry.
Technologies are too many nowadays, focus only on something you like, even if you know nothing about it at the moment.
The key is not what you have been until today. The only thing that matters is what you want to do.
How many rows do you usually manipulate at the same time?
I'll let you know.
> I am Mark Ben John Bill. from FBI unit,i have been instructed by the FBI Director Christopher A. Wray, to inform you that out of our thorough investigation lately , we found out that one of the abandoned valid Packages such as ATM Cards And Consignment Boxes by diplomatic agents who complained that the beneficiaries failed to pay for the anti terrorist clearance certificate to guide and show that the fund is no way related to fraud or drug money,with the information we have here , we found out that one of the funds belongs to you and it worth the sum of $10.5 million US Dollars.
So, IMO, Fuck you AWS, I'm rich now!
If I invest something in your company, and you are sick, should I know it?
I remember to close all my social networks when my daughter was two years old, about 12 years ago.
I will never know what I missed.
I know this is not an easy battle, but if they have more users than the US population, they are precisely the group that should not resign.
I'm alone, making likes in their projects, talking people this is happening, and when the moment comes, the fight with the system, they drop at the first sentence? What is this? Was it just a US fight? The decentralization got destroyed by a single man?
W3C members are visible here: https://www.w3.org/Consortium/Member/List
Those are the members that decided that WebAssembly is now an official web standard, not the testimonials.
I'm investigating more about the voting system here, https://www.w3.org/Consortium/Process/ERB.html.
Icons are perfect to define actions (fixing bugs, improving the layout, etc) however, the commit is important when you are doing releases, cherry-picks, maintaining patches, etc.
I'm not against changes and sure the icons look very cool on the front page of GitHub or in `git log`.
However, most of the maintainers, who actually do things with commits, they work looking at the content. Be useful in the future, to understand what was going on, is the main purpose of the commit message.
I agree that a bug, a rocket (and others) can be used to improve the subject of a commit, eventually, the problems are:
-by introducing icons, are we creating a perfect excuse to be lazy during the commit phase?
-Will the icons makes our history of change the poorest?
One of the most complex areas, having lots of users, that need to be fixed, is human beings. Spend all your time to know who you are, why you are like that, and change this world starting from the most promising thing it has on it: you.
In the meantime, try to carry out activities that you like (ride your bike, walk alone or with real people). Do it disconnected from any device or social network.
Do things that make you feel real and unique, without layout, template, guidelines, best practices. Ignore any negativism (fortunately you are introverted, it should help). Recognize in every moment that you have to learn a lot. Learn a lot and repeat.
- disaster recovery is the first thing you should have in mind, where is the second.
- the right strategy is to preserve the business, not going to the cloud.
I always had fun building my own environments. After the fun came the work and, economically speaking, managing and maintaining those environments has always been an advantage for me. If however, I consider the time it takes to understand and fix problems in VMWare, or SQL optimization, or configure Microsoft AD, Nginx, and others..., I don't know how much I would recommend building everything from scratch by renting some servers.
After a while, the same color pattern is emerging from customer communication.