I cannot count how many times CSV "format" has caused problems for me..
In my country the decimal separator is comma, instead of punctuation.
This causes problems when importing and exporting with this "format".
Just few weeks ago I had fun times working with API returning CSV in unknown encoding. Hopefully they will never make changes (you cannot always trust headers). Ah and i do love when CSV is missing headers and someone adds data into middle.
Of course some of these issues can be avoided by doing the things "right". Sadly you cannot trust this in real life. People write ugly structures in JSON, but at least you can validate results..
I have same way of estimating tutorials and similar content. There are quite many people posting videos without real understanding what they are teaching..
I am an engineer/developer and practically work solo in many projects.
Last year I started using the Docker at work. Before docker, all services were installed manually on physical/VM server machines.
Getting my head around Docker took some time, but I feel that it was time well spent.
I started with composes, but moved to docker swarm (single node) for having configs/secrets. Currently I manage everything with the Portainer, that allows me to control all the swarms and services with relatively easy way.
After the working stack is created and tested on the development server, installing it Into one or multiple production servers is quite easy. Depending of the case ugrading services is relatively safe as you can rollback to previous images if you or someone else messed up.
The nicest thing for me, is that all dependencies are inside the image. No need to worry about conflicting versions or setting up same thing multiple times. Sadly you still need to be aware of any security related issues that might exist within the image and maintain them. But this same issue does exist outside of Docker as well.
However, if you don't understand or think what you are doing, it is still possible to screw yourself in many ways. But I feel that this is always possible in our field, no matter what tools you are using.
While the Docker is not a silver bullet, it has made my life a bit less stressful. And I think it is important to understand what you're setting up and how you are doing it. Personally I would not want to go back to my old workflow.
Ps.
Sadly the swarm is deemed by many to be dead. It is relatively easy to manage by a single person and I am not getting the same feeling from alternative solutions, such as Kubernetes.
Everything is subjective.
The users who are voting now are not same people as the users who bought first models.
I have OnePlus3 as my main phone and I am still quite happily using it. However, as the manufacturer has changed their target audience, my next phone is not going to be oneplus.
Sad thing, it is pretty hard to find a decent phone which does not have crap pre-installed.
This happens to me a lot. I need to have access to keyboard for being able to type some older password. Same thing with pin codes.. Funny how brain works.
Long time ago I remember reading about some service, that allows using single use credit cards. Last year I was looking for it, as many services cannot ne trusted with this information. But I could nothing like it. Maybe I was just dreaming...
Getting a legit card like that could be possible, but I don't think its worth of hassle and possible costs. Some companies practically throw these cards on you, but usually there is a catch.
I noticed this yesterday and now I am wondering what to do.
Especially when more and more videos are getting flagged.
ID is out of the question, credit card seems more plausible. However, i wonder what happens when you give the number. I don't want that it sticks after validation...
For years I have called my APIs "HTTP API" as they usually do not follow the abstract definition of the REST. And because I've seen so many APIs being called REST that barely follow any definition of a sane API.
The whole term is used by people as synonym for an API by management and by developers who never took closer look of the definition/paper.
I think that the situation is bit like in OOP, TDD and many other things that cause flame wars. When something good ideas come up, people tend to be religious about it. Instead of taking good ideas and utilize them for better solutions, we take things to extreme and fight about tiniest things.
Now this brings back some memories. I remember finding this when I was still a teenager and found it funny. I cannot really remember if I thought that this was legit, even it looks like a joke now. It could have been written by an adult, when looking from teenagers point of view. After all, adults had some stupid rules.
Since beginning of the year, I have installed two Win10 two times. As I expected some dark patterns, I made sure that these machines were not physically connected to any network. Even this worked, it still managed to piss me of by forcing security questions for admin user. Seems that only way to avoid this "feature", is to modify register. Even on pro-version.
There might have been some obscure way of avoiding connecting via installer (perhaps a link inside EULA text). But as long the internet is not available for the machine I believe that this workaround should be possible to use, until MS decides that internet is required for installation.
Edit:
After doing the install without Internet, I do remember that they were trying to get me to create MS account. However I have not created one. It is possible that they give up after some time or maybe I found some way of disabling this.
People tend to forget that everything seems easy when you know things.
I have been in situations where I had to compile some projects from other people and it has been painful every time. Especially as I might be in an environment where there are no IDEs that wrap things up for you.
Everyone has different experiences and requirements for their projects and not everything is same as it is for you. Don't take it personally and try to passively insult other people's intelligence.
While there are issues within Python side, I think it is quite unfair to use numpy as an example.
My reasoning is that the numpy project is meant for scientific and prototyping purposes, but many times people are using it as an shortcut and include the whole thing into their project.
That being said, the quality in these packages does vary depending on who developed them. But I think this is a problem that exists with all languages where publishing packages is relatively straightforward.
Probably there are things to learn from this article. However, I could not really find the red thread from this. This might be my fault, as I tend to scan the whole document with speed before investing my time on it.
The visuals were confusing as it was not always clear if they were part of an example story or explanation of the articles ideas.