aespinoza

Would you be willing to write an article comparing the results ? Or share the code you used to test? I am super interested in the results of this experiment.

I downloaded it, but I was not even able to get past `Account Set Up`. :(

Under that definition, I wonder if anybody is `creative`. We would need to assess how many of what we call `original ideas` are not rehashes of other ideas.

Greatness comes at a very high cost. But to me greatness is not about money, or economic success. Greatness is a very subjective term.

For me greatness is about mastering my craft. Creating great things. It still comes at a very high cost, because practice is not free, and it takes away time from life, especially family time.

Now, Why? Look at life this way: Humans only care about the experience of life. Experience can be focused on family, money, personal achievements, material things, etc.

What you refer to a `great` experience is not really a `great` experience for another person. So `greatness`, IMHO, refers to the experience you wanna have. My great experience is becoming a master in my craft. That is my image of greatness. To Transcend. I trade time focused on my work, for time doing other things.

Now, there could be a person that has a vision of `greatness` that refers to being the greatest dad ever. That is still greatness. So basically, what I am trying to say is that everyone looks for their version greatness, and that not necessarily matches what you define as greatness.

IMHO mono-repo vs multi-repo should be decided based on the sources of change for each component in a product. For example, the cloud components of a product usually change at the same pace and for the same reasons, it makes sense to have them in a mono-repo. Even in a microservices approach. Even in the cloud certain components can change at a different pace and for different reasons. For example if you have grpc api that talks to your mobile app and a webapi exposed to your customers.

I believe that components that move at a different pace and change for different reason should not be in the same repo. It is difficult to setup CI/CD for different ways of deployment and specially if they not changing at the same time.

Now, regarding security, it is important to keep different components of a product in different repos, this will give you the flexibility to manage a more restricted set of credentials and reduce the number of people that have access to it.

In the end it involved 3 things: 1) Sources of Change, 2) CI/CD Processes and 3) Security. You can definitely mix and match.

I haven't seen any research that has pointed to me to one or the other. I can however give you my own experience.

I have mixed feelings about this. I moved from multiple monitors to one big monitor. I do not see a considerable difference between one or the other.

Obviously this is all subjective so I cannot give you any numbers to back this up. I am however not going back to multiple monitors.

This book made me fall in love with Lisp: Land of Lisp - https://nostarch.com/lisp.htm

I found it super helpful understanding everything there is about Lisp, and you can move from there.

Donald Knuth (https://en.wikipedia.org/wiki/Donald_Knuth)

Leslie Lamport (https://en.wikipedia.org/wiki/Leslie_Lamport)

Ian Goodfellow (https://en.wikipedia.org/wiki/Ian_Goodfellow)

Just to name a few....

In the case of technical books, I have found that pricing is not that different from digital to physical books.

This is a good example: https://www.amazon.com/dp/1449373321/ref=cm_sw_r_tw_dp_x_qQ8...

It is $29.99 for Kindle and Physical is $34.91.

Not sure if this is what you are referring to, but this page contains a list of offensive techniques which could be used to create attack vectors:

https://attack.mitre.org/

I can access it fine: https://www.isitdownrightnow.com/tinycorelinux.net.html

Basically what put me off was the way the keys are arranged in a semi circle. It was uncomfortable to code. I am not sure if it is because I have big hands or just the design didn't work for me.

Most of the good ergonomic keyboards are around the same price. Look at this one which it is good, but I personally didn't like: https://kinesis-ergo.com/shop/advantage2/

You could try Microsoft's ergonomic keyboards, they are cheaper, but I personally didn't like them either: https://www.microsoft.com/accessories/en-us/products/keyboar...

I love Ergodox (https://ergodox-ez.com/). There is a new keyboard by the same company which looks cool, but I haven't tried it yet: The Moonlander (https://www.zsa.io/moonlander/)

I second this. Will Larson's book is definitely one of the best if not the best book I have read on the subject.

There are other good books which can add to it like "The Manager's Path" by Camille Fournier.(https://www.amazon.com/gp/product/B06XP3GJ7F/)

I am right there with you. The whole idea of "master" is not really based on the idea of slavery focused master.

Master represents the final version of a component or software which ends up in production. It is the same meaning as an audio master (https://en.wikipedia.org/wiki/Mastering_(audio))

If the word master is considered evil, then what would happen to a Master Degree ? or Dojo Master ? Words have different meanings in different context, let's focus on changing language that changes the way you think.

If what you are looking for is a DB-like application, I recommend: https://eventstore.com/

Not sure if you can set retention periods, but it is definitely worth to take a look into that, and definitely a good starting point.

And this is why Ext.Net is so expensive. Sencha is the one who decided to hike the price.

I was a big supporter of what the Ext.net engineers do, and in a way I still do. Their tech is very professional and stable.

I stopped using them right after the price hike. IMHO, it is overpriced. Since I can get most of the same stuff done with other frameworks and mostly for free.

Nevertheless, their work on https://bridge.net/ is awesome.

Is there any official outlet where this is published ? I didn't find anything. I learned this because of people who knew him.