I actually had the experience of using meaningful identifiers in a previous company. At that time it was really handy in a lot of day to day stuff, but I'm now thinking we might not have used them long enough to have run into the problems described here.
Yeah, I've also been using screen for years without ever feeling the need to switch to tmux. Although remote ssh work is relatively rare for me (eg a couple times per month)
I still think for very small stuff it's easier to just write a shell script. For instance a docker entry point, where you set a few env vars, download some required files and start your main application.
And the public transport bikes you can hire for a couple of euro per 24hr are very popular. This way you can do the last part of your journey easily without taking you're own bike on the train. (This is actually cheaper as well, since the price of renting the bike is lower than the price of bringing your own bike on the train)
I’ve spend 10 minutes on this and still have no clue what it actually does. Seems to be focussed on beginners with very trivial and general tips on Git and terminal commands.
I totally agree, I have a few shortcuts in my GCE dashboard, but I seem to always forget which one is which. For instance logs, DNS and storage have super similar icons.
Blendle Data Scientist here (living said dream). I'd like to mention that users do have influence on what is done with their data. We currently provide two ways of determining what data is collected, one setting (which is switched on by default) makes us collect data for internal usage. Switching this off will make us stop sending analytics events from the frontend and we will stop aggregating your data into a profile used for personalization. Note that these profiles are currently being developed and are not yet in use anywhere and once they will there only use case will be making Blendle better for its users. The other setting is switched off by default and allows us to share some data with one specific publisher (which is very clearly mentioned).
Ok, if you are indeed asking the same questions that helps. I would add some information per item with some explanation or definition, so it is as clear as possible what is meant by the different terms.
So instead of the ambiguous text 'Software Engineer' we now have 10 ambiguous texts ranging from 'Analysis' to 'Data Science'. I don't really see how that solves a problem, since these underlying concepts are also quite hard to define consistently.