Finally it's here!! :-)
Probably the feature that I was missing more since I started using Telegram!!!
It deserves a mention here :-)
Journal entry from 20 August 1999, introducing his new blog about The Lord of the Rings.
Facebook AI has developed the first neural network that uses symbolic reasoning to solve advanced mathematics problems.
You may have heard about Bandersnatch, an interactive film released on Netflix as part of the Black Mirror series. I’ve heard about it when it was released, but didn’t get around to watch it until recently, and I was surprised at how deep and thorough the implementation is.
Analysis and numbers of the Bandersnatch interactive film.
A vegetable-picking robot that uses machine learning to identify and harvest a commonplace, but challenging, agricultural crop has been developed by engineers.
Learn from Docker experts to simplify and advance your app development and management with Docker. Stay up to date on Docker events and new version announcements!
Tens of thousands of Hongkongers took to the streets to protest what they saw as creeping tyranny from a powerful threat. But they did it in a very particular way. In Hong Kong, most people use a contactless smart card called an "Octopus card" to pay for everything from transit, to parking, and even retail purchases. It's pretty handy: Just wave your tentacular card over the sensor and make your way to the platform. But no one used their Octopus card to get around Hong Kong during the protests. The risk was that a government could view the central database of Octopus transactions to unmask these democratic ne'er-do-wells. Traveling downtown during the height of the protests? You could get put on a list, even if you just happened to be in the area.
So the savvy subversives turned to cash instead. Normally, the lines for the single-ticket machines that accept cash are populated only by a few confused tourists, while locals whiz through the turnstiles with their fintech wizardry. But on protest days, the queues teemed with young activists clutching old school paper notes. As one protestor told Quartz: "We're afraid of having our data tracked." Using cash to purchase single tickets meant that governments couldn't connect activists' activities with their Octopus accounts. It was instant anonymity. Sure, it was less convenient. And one-off physical tickets cost a little more than the Octopus equivalent. But the trade-off of avoiding persecution and jail time was well worth it.
What could protestors do in a cashless world...? If some of our eggheads had their way, the protestors would have had no choice.
We often have to write code using permissive programming languages like C and C++. They tend to generate hard-to-debug problems that can crash your applications. Thankfully, many compilers offer “sanitizers”. I discussed them in my post No more leaks with sanitize flags in gcc and clang. I strongly encourage the use of sanitizers as I think it is the modern way to write C and C++. When many people describe how impossibly difficult it is to build good software in C and C++, they often think about old-school bare metal C and C++ where the code do all sorts of mysterious things without any protection. Then they feel compelled to run their code in a debugger and to manually run through it. You should not write code this way! Get some tools! Sanitizers can catch undefined behaviour, memory leaks, buffer overflows, data races, and so forth.
Have you ever been in a situation where you are presenting to your manager or your manager's manager and you completely flub the opportunity by saying all the wrong things? Me too. It is from such encounters that I started to put together design patterns for handling these difficult situations. I like to think in systems and patterns, so applying this way of thinking to communication just makes sense. I have also found that these rules of thumb are useful to others, so I would like to share them here.
When you can spot the patterns, you can use some of the ideas presented here as guidelines to navigate these tricky, high-stress scenarios. This way you can feel confident and capable as a leader because you will know what to do: how to solve the problem and what steps to follow next.
Here are some of the most common challenging situations you may run into at work and how you can handle them.
- Someone asks you something you don't know
- There is a problem that is your fault or responsibility
- There is a decision that you don't agree with
- Your manager gives you negative feedback
Have you ever been in a situation where you are presenting to your manager or your manager's manager and you completely flub the opportunity by saying all the wrong things? Me too. It is from such encounters that I started to put together design patterns for handling these difficult situations. I like to think in systems and patterns, so applying this way of thinking to communication just makes sense. I have also found that these rules of thumb are useful to others, so I would like to share them here.
When you can spot the patterns, you can use some of the ideas presented here as guidelines to navigate these tricky, high-stress scenarios. This way you can feel confident and capable as a leader because you will know what to do: how to solve the problem and what steps to follow next.
Here are some of the most common challenging situations you may run into at work and how you can handle them.
- Someone asks you something you don't know
- There is a problem that is your fault or responsibility
- There is a decision that you don't agree with
- Your manager gives you negative feedback
I am a bit dissatisfied with the use of the Tragedy of the commons to represent issues with free and open source software development. It is not an abstract resource that can be depleted when overused. It is not magically maintained if left alone.
It is based on the work of people, and we should not erase those people.
Unfortunately (and it is by design), most of the licences and the vocabulary around it are focused on the software’s user. After all, they work by reducing the creator’s right to empower the user.
As examples of this vocabulary, we have the distinction between “free as in beer” and “free as in speech” to show that the “free” word in “free software” has more to do with freedom and people’s rights to use, study, modify and share a program, than its actual price. Although, in practice, the overwhelming majority of FOSS will not cost you anything.
The author tried to edit data in spreadsheet programs.
This post illustrate ho to use Vim to edit tabular data, although there are a few things that will make it more pleasant. It is assumed that editing files are in tab-separated value format (TSV).
"But what about CSV files?" Just. Don't.
Do: convert your CSV to TSV and back for editing.
Error handling is an integral part of programming, but in many popular languages, it comes as an afterthought.
The godfather of numerous programming dialects, C, never had a dedicated error or exception mechanism in the first place. It is up to the programmer to accurately report whether the function did what it was intended to do, or threw a tantrum—usually by relying on integers. In case of a segmentation fault—well, all bets are off.
This post goes through the experience of the author in the adaptation to the Golang error management workflow.
A list of things to pay attention to when making interviews.
The list enters some few items in details, while it only lists other items without explanation.
When I think about who I would like to work with as a programmer, I think so much more about non-technical skills than technical skills that make somebody a good co-worker. In fact, all of the skills that are in this post contribute to writing good code that improves technical projects. Most of them are really helpful for careers outside of programming too, but I'm going to focus on why they're useful for programmers specifically.
Most widely-used programming languages have at least one regular conference dedicated to discussing it. Heck, even Lisp has one. It’s a place to talk about the latest developments of the language, recent and upcoming standards, and so on.
However, C is a notable exception. Despite its role as the foundation of the entire software ecosystem, there aren’t any regular conferences about C. I have a couple of theories about why.
From Josh Mcguigan.
This is a tutorial on building your own shell using Rust, in the spirit of the build-your-own-x list. Creating a shell is a great way to understand how the shell, terminal emulator, and OS work together.
Alpine Linux-based Docker images are small, but they can still bloat up quickly. If you're concerned about image size, search for alternatives, like Minideb.
When the Docker revolution started, one argument among many in favor of using containers instead of virtual machines was their size. Container images were supposed to be small.
However, several anti-patterns quickly emerged in the early days of Docker. First, most people wanted to treat containers just like VMs, hence they wanted an SSH server in them, they wanted to run multiple processes in them and they wanted their regular Linux distributions.
This quickly ballooned the size of Docker images that could be pulled from the Docker Hub. Official Ubuntu and CentOS images used to be above 600 MB. Once dependencies and application code got added, it was not rare to see several GB Docker images around.
For the longest time I did not know what everything meant in htop.
I thought that load average 1.0 on my two core machine means that the CPU usage is at 50%. That's not quite right. And also, why does it say 1.0?
I decided to look everything up and document it here.
They also say that the best way to learn something is to try to teach it.
