As early vim (vi imitation) user on Amiga, I can't imagine living without it.

What engineers usually struggle with as they grow into more senior roles is the transition from being primarily a technologist to being a leader. This is such a huge shift for a lot of engineers and requires soft skills and communication style adjustments. The more senior you are the more your focus shifts from coding to listening, networking, influencing, selling the technical vision, building trust relationships, understanding what other engineers need and want, to mentoring, to raising the quality of the team around you through influence to motivating others as well. Being able to influence the product direction, being able to express in business terms why something has to be done or should be a higher priority etc. Also, understanding the organization and becoming organizationally savvy is important.

All of these skills take time and practice to achieve, and good managers can guide their people through the journey.

So let's say you have a set U (possibly uncountable). To say let {u_i}, i in I (another set, possibly uncountable) is equivalent to asserting existence of function f:I -> U, such that f(i) = u_i. Note that this does not even require axiom of choice, since you are allowed to postulate that a function exists.

Of course if I is uncountable you can't list the elements of I, but that is not important in this case.

Everyone answers correctly the ball will roll of the table and fall to the ground. But then ask them" "What was the color of the ball? What was the size of the ball? What was the gender of the person pushing the ball, what clothes were they wearing?"

People with aphantasia are usually stunned by the follow up questions. People who don't have aphantasia really have seen the table, the material its made of, imagined a ball of certain size/type color (e.g. multicolor beach ball, or basketball or what ever), and they saw an actual person pushing the ball, they saw the ball rolling on the table an falling to the ground and can answer details about their vision.

Notwithstanding, I still find it very useful as a general guide when designing distributed systems.

You messages are stored in encrypted SQLite3 database. The Signal encryption key is in

    ~/Library/Application\ Support/Signal/config.json

Navigate to

    ~/Library/Application\ Support/Signal/sql/

    sqlcipher db.sqlite
    sqlite> PRAGMA key = "x''";
    sqlite> .schema

Of course there is a Python package to automate all of this here:

https://github.com/carderne/signal-export

This exports your message history as markdown and HTML files for your convenience and it will do incremental exports as well.

For iOS the same holds true, considering iOS has had a jail break most of its existence.

So, in retrospect your Signal messages are only as secure as computers of the people you talk to and of course your own device.

I would go a step further and assert that there is no such thing as secure communication.

[1] - https://www.amazon.com/Computer-Systems-Programmers-Perspect...

https://github.com/glinscott/nnue-pytorch/blob/master/docs/n...

It's pretty interesting read.