![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
Just having clear and concise variable names often goes a long way. Avoid using abbreviations.
Breaking out the code into functions helps limit the number of variables within a scope, which makes it easier to name them.
Just having clear and concise variable names often goes a long way. Avoid using abbreviations.
Breaking out the code into functions helps limit the number of variables within a scope, which makes it easier to name them.
Refactoring for the sake of refactoring is rarely a good thing. It should be done with a clear purpose in mind.
Refactoring is often necessary to ensure new features can be continuously added with ease.
This is the truth. In my experience, the people who often writes comments are also writing the most incomprehensible code.
Comments are frequently getting outdated as well, so they’re not in great help understanding the code either.
I’m the opposite. If there’s 500 lines I will look closer for issues. If there’s only 10 lines it’s LGTM. I’m not going to reward such behavior.
Flask is a fun framework for making web apis.
Pika is a client for RabbitMQ, if you want to try message queue stuff.
Numpy and sklearn for numerical and machine learning stuff.
Matplotlib for making nice plots of your numerical stuff.
Pytorch for deep learning.
Pillow for image processing.
OpenCV for computer vision.
Pygame for 2D games (maybe a bit old, but I had lots it fun with it when I started learning programming years ago)
He has to finish section 7.2.2 of his book
Knuth has also decided that once he dies, a last version will be made which sets the version number exactly to pi.
Undefined is not part of JSON specification. It’s also not a thing in Java.
That’s good to hear. I haven’t touched Eclipse in maybe 15 years and back then it fueled me a burning hatred for IDEs. It felt like a huge confusing mess. But maybe it has become more streamlined lately.
Now I have grown out of my hatred and can’t imagine a day without (non Eclipse) IDEs.
Is anyone using Eclipse anymore? I’ve barely heard anything about it the past 10 years.
It’s not that funny.
Docker is like a virtual machine, but you only run one specific program in it. About exactly what the meme describes.
That’s fair enough. The common misconception is that waterfall is great for space missions, when in reality NASA is doing agile.
I agree that not everybody is NASA, so what works for them doesn’t necessarily work for everyone.
NASA also successfully flew a helicopter on Mars first try.
It’s barely waterfall planning either. Often there’s no planning, at least no coordinated one.
Currently at my current workplace we lack coordinated planning between teams. It seems like everybody is working in their own directions and it can take months until we get feedback from other teams. Mostly a product management problem.
The author is also hyping up waterfall too much. Agile was created because waterfall has its shortcomings (e.g. the team realizes too late that what they’re building isn’t what the customer wants).
But I also think it also represents how poorly implemented these ideas are. People say they do agile/kanban/scrum, but in reality they do some freak version of these.
I think this is a bit disingenuous. There’s no customer interaction in these panels.
So waterfall would be:
Customer says they want to go to Mars.
You spend years building a rocket capable of going to Mars, draining all the company budget in the process.
Customer then clarifies they actually meant they wanted to go to Mars, Pennsylvania, USA - not the planet!
Which doubles the maintenance work to keep docs in sync
When someone writes API docs, should they assume the reader knows nothing or can they assume the is already experienced?
It takes a lot of effort to write documentation towards newbies, at the cost of making it more difficult for already experienced to find the answer they need.
Difficult to punch coworkers in their face in zoom