ArcMex

>It means we're proud enough to drop the word "beta".

Huge milestone. Congratulations! I will be trying out the flatpak on my Linux build and keeping an eye out for your progress. Well done!

Sad news. Wishing them the very best.

Congratulations on the book! I think we need more books like this. Recently on YT, I have been watching more and more videos on the subject. Most of them target beginners (which is fine) but few talk about what comes next. So your book is very welcome.

I believe it’s better if they are.

I once reported to a CTO whose bible was How To Influence People and Make Friends.

He ordered a migration of 4 million records to be done in a weekend because he had promised the CEO “everything would be fine by Monday” but I had told him that that plan would require 5 days to put everything in place, even a rollback.

The fact that he refused to hear me out when I pointed out the infrastructure capacity and the SQL scripts tested beforehand to arrive at my estimate made me wary of management that doesn’t understand even the basics of the technology we use.

So I think it goes a long way when CTOs are technical. They can give more realistic deadlines to reports while being able to be reasonably honest to their colleagues about estimates and progress.

Interesting argument. If you take a look at Sublime Text packages, you will see that some of them were last modified years ago but they are still downloaded and sometimes even trend according to the packages site metrics. You then have to ask, can I trust these packages? Or do I look elsewhere like VSCode on Neovim whose extensions and plugins are often regularly updated and maintained in comparison?

Wow, this comment is a sight for Soras

Ironically an anime that also released in 2011 called Steins;Gate has operations with crazy names. When it’s revealed what the criteria for the names are, it boiled down to “made up whatever sounded cool”

I don’t know, isn’t “Quiet Quitting” counterintuitive? Isn’t doing the bare minimum harmful to you getting a new job, let alone going out on your own?

Before I founded my own business, I gave my last day job everything I had. It just never worked out. But those lessons carried me forward in my own venture.

I don’t know if “just getting by” could have made me keenly aware of the opportunities that came by doing my best as much as possible.

I could be wrong though and would love to hear from others proving just that.

Same here. Writing/sketching is thinking. By the time, I’m actually typing code, I know exactly what to expect. Having that clarity is quite empowering and ascertains control.

I enjoyed this article. I echo many responses here and some of what’s in the article to reaffirm their importance in not just being good, but successful.

1. Clear communication

2. Thinking thoroughly about the problem and the solution

3. Easy to maintain code

4. Testing

5. Documentation

6. Research and learning

That already exists.

https://www.apple.com/shop/buy-mac/macbook-pro/13-inch

Did you mean an M2 Pro MacBook Pro?

Oh, I love your response. Thank you.

My workflow was as follows

- Remote into server and develop from there

- Git to different location, could even be same server

- Occasionally pull on local machine for redundant backup

This allowed me to

- Segregate builds for my testing and the business's UAT

- Allowed me to always have a stable build locally that I could look at from home

Before, I did develop on my local machine and push to a server. Some part of me still thinks that's the proper way to do it.

But I am always seeing what works best for the current situation and developing directly on my server served me well once upon a time.

Thank you for sharing this. I will give the 30-day trial a shot. I find VSCode just fits my needs on my boxes (Mac, Win, Linux) but I am always open to try stuff.

>sftp(1): add a "cp" command to allow the sftp client to perform server-side file copies.

Well, goes to show how little I know. Been using this for years but apparently not!

Commit small, commit often

I focus on the time required to accomplish something and it dictates where I want to be at a certain age, as opposed to picking an age and arbitrarily setting goals to hit by then.

Become a software engineer and solve problems in the areas you are interested in.

>Reduce the number of tools you use for the same purpose to 1 if you can

This was the focus of Q1 for me. I had 2-3 apps doing the same thing so I had to make a choice and choose the most suitable and stick to that.

It's funny that this advice goes beyond PKM. Even programming tools, pick and stick to one. You can always explore later. Go with your use case but I digress.

Thanks dSebastien

TickTick

Because I can catalogue and schedule all my tasks in one place. Before, I needed some combination of a calendar, to-do, notes and reminder apps. But now, I just use TickTick.

For comparison, I used Todoist prior but found the free tier more limiting than TickTick.

I agree. Don't stay at a job with bad management. It's not worth it.

Where are they now?

It's funny, ever since I dedicated the morning to normal duties and afternoons to growth and development, I deliver results faster. Could be that I only use 4 hours to do all my work so I plan better and action faster.

>This is the only sane way I have found to progress in a tech career. The daily and weekly learning really adds up too - in my experience this is the difference someone who has 10 years of experience and someone who has "2 years repeated 5 times"

I agree. Thankfully, my culture does not shun 2-3 year job spells on your resume. Typically, this is what I do. When I learn enough to do my boss's job, I leave. I am now at a point of running my own, small consultancy service. Only need a few more clients to finally quit my day job for good.

Being in tech has the advantage of me being knowledgeable enough to pursue tools and languages of interest that will benefit both my business and day job.

That is what I did. I learned web development and used those skills to do projects at work and for my clients on weekends.

Later on, I learned project management. Used those skills at my day job and made a consultancy killing as a PM for hire.

I feel privleged to have been in this position. So, yes, I do advocate for spending time increasing your value at work. But that time should also work for you outside of that day job.

I find learning and applying difficult. I usually prefer to learn all the fundamentals I need to solve my problem and then apply. So learning another language is relatively easy.

Also in my country, very expensive. Therefore, I order from Apple USA directly and import through courier. The exchange rate, courier fee and 15 day arrival 'delay' are much more tolerable than what I would pay for locally at the 'iStore'.

Will give this a shot and test with https://gorest.co.in/

I have got some good usage out of Thunder Client.

https://marketplace.visualstudio.com/items?itemName=rangav.v...

I typed in Taiwan and I have thoughts. Good thoughts.

>To me, the idea of Shu Ha Ri provides thinking tools, a language and a frame of reference to approach learning a new skill. When you are first learning something, variety of ideas isn’t usually the most helpful place to start. Once you get the basics down, then move on to experimenting and looking to integrate new thoughts or ideas. Your experiments will lead you to new paths and eventually you’ll move beyond the specific practices and evolve your own way of doing things.

That is a good summary.