ArcMex

Nice! I have this on my 2023 TBR. Cannot wait. I read Netflix is picking it up for an adaptation?

I have heard good things about this book. I have it on my Kindle and plan to read it next year.

Fiction

I discovered and read Blake Crouch this year

- Dark Matter

- Recursion

- Upgrade

- Pines

I also discovered and read

- Project Hail Mary by Andy Weir

- Gravity by Tess Gerritsen

- A Man by, At the End of the Matinee Keiichiro Hirano

It's between Recursion and Project Hail Mary for me. I am leaning more towards Recursion.

Non-fiction

I discovered and read the following this year

- Deep Work by Cal Newport

- The Millionaire Fastlane by M.J. DeMarco

- Zero to One by Peter Thiel

- How to Start a Business Without any Money by Rachel Bridge

- Creative Gene by Hideo Kojima

- Steve Jobs by Walter Isaacson

- The Psychology of Money by Morgan Housel

- Show Your Work, Steal Like an Artist by Austin Kleon

- Press Reset by Jason Schreier

I would say Deep Work and Steve Jobs had the biggest impact on me.

Programming

I am learning Elixir using Elixir In Action by Sasa Juric.

First, find a job.

Any job you are willing to do.

That should add some stability in your life as a start.

An incredible project. Your motivations resonate with me. Thanks for sharing.

Thanks, Jose. Really looking forward to it.

Regarding Apple Silicon, last I checked Asahi Linux had made some significant strides but with drivers YMMV. Might be worth looking into if you’re serious about running Linux on Apple Silicon. As for Intel, I’m not too sure. About as mature as it’s been for a while now, I reckon.

I’ve eyed the P series for years but ever since I got a MacBook Air, I have come to expect my machines to be silent.

Do you know of any use cases that WSL2 might be lacking for the average developer?

Has there been any instance of you preferring a dedicated Linux box to WSL2?

I would have loved to see you talk about the part of the book that addresses working with others, as that seems topical to the OP.

Overall, it is also my recommendation, in that when you develop a good habit of churning out quality work, it enhances your contributions to the team.

I’m interested.

My main topic of interest is how much has changed over time and perhaps what the next 20+ years hold. Such discussions can be eye opening when considering what direction to take, for example, when adopting frameworks and methodologies.

Looking forward to your content.

I agree.

Soliciting for business and sustaining good relationships, in particular, will enrich one’s experience overall.

I’ve learned many lessons - everything from improving my craft to knowing when to drop a problematic client or project.

I’m always looking to improve my set of skills, so thank you for the thread and thank you for the responses- I have managed to pick up some recommendations.

My personal recommendation would be Deep Work by Cal Newport as it is my most recent read, having completed it just the day before yesterday.

I applied what I learned and discovered that I was able to meet deadlines much easier than before. I’m also in the process of applying deep focus techniques to my work weeks to ensure I have a tangible build or product every Friday. Could be a document, a repo, a feature, etc. So far so good. This past week I delivered a Design Spec document in record time.

Thanks again and take care.

Thanks for sharing. This had made me really think about how I can tackle billing in future.

This was the first time reading about this, thanks for sharing. It's an alien concept to me so it was a fascinating read.

My concern was how will putting these little languages together work and it turns out that the author also had these questions.

Where do we draw the line on "enough DSLs" for example? And what happens to the gains from using several DSLs in tandem as opposed to a high-level language with libraries that accomplish the same thing?

Quick SSH sessions mostly.

>As can be seen, these patches are slowly building the in-kernel Rust code up so that real functionality can be implemented in Rust, but this process has some ground to cover yet. It's not clear whether more Rust code will be proposed for 6.2, or whether this is the full set. The pace of change may seem slow to developers who would like to start doing real work in Rust, but it does have the advantage of moving in steps that can be understood — and reviewed — by the kernel community. The Rust-for-Linux work has been underway for a few years already; getting up to full functionality may well take a while longer yet.

Me too, I agree.

Thanks for sharing this.

Daniel.

I can only wish you the best. 6 months ago, I was in your shoes. Today, I have my own startup building applications I am passionate about. I have never been happier. I’m grateful for everything that I’ve learned and endured so far.

I just wanted to tell you that I hope you stay positive even during the dark days and that you maintain your integrity. Truly, I wish you the very best.

Regards, Daniel :)

Very sad indeed.

Just a few days ago, I was thinking about what relocating could mean for me and my family and it frightened me to think about being a stranger in a strange land without a job.

Wishing them best of luck.

Like a dog?

Regarding learning a new paradigm and having to build an application with it, I think it’s possible within a reasonable time.

My approach, ironically was the incremental approach mentioned in the article. So the first step was for me to view it as one problem - build app using X. Then the steps might have looked like

1. Learn ABC

2. Apply ABC

3. Refine ABC

I always know enough to build something. Eventually, I know enough to refine it.

Now the author said this is slow and I agree but at the end of what would be a learn-first-build-later approach is an actual, built system. You can now solve the next problem, enhancements.

To any new developers, I should mention that a good foundation of fundamentals is key to this kind of approach and I admit, there are much better ways to learn and build.

Sorry but off topic.

At what point did containerization begin to make sense for your workflow?

Have you tried mirroring?

For context, see Chris Voss’s ‘Never Split the Difference’

Never Split the Difference: Negotiating As If Your Life Depended On It

https://www.amazon.com/Never-Split-Difference-Negotiating-De...

All this article has done is reinforce my desire to always consider the best paradigm for my use case.

Have you ever heard of Chirper?

>I don't think anyone really cares about what I have to say

Reaching 3 - 5 friends who care is enough for me.

just enough education to perform

Can’t even transact without it * wink *