With these two variables, the default minibuffer completion can now automatically open and update the list without you having to .

completion-eager-display completion-eager-update

Or at least that's how I view it. Whenever I think about using SQLite, I make sure I read these documents to see if I am fine with the limitations.

https://sqlite.org/whentouse.html

https://sqlite.org/quirks.html

There was a period of time in my life that I spent lots of time checking Imgur for meme and cute animal pics daily. I can just type "im" in browser address and press "enter" to consume whenever I want.

I "fixed" this addiction by removing Imgur from browser history so it would not auto-complete Imgur's URL. Since then, whenever I have urges to consume, this friction stop me from doing so. It has worked very well over the past few years.

For me, I find the hardest part of securing systems are usually to decide what is good enough for the current situation.

For example, ask your team to break down the tasks and provide a schedule for each task, and try to help them follow the schedule. If a task is taking way too long, ask them to break down it again. Remember to ask them to explain why they plan it like that.

Make sure you and your team have enough communication so you all know what need to do and what NOT to do. If your teammate is doing thing that is not in the scope, discuss with them and make the decision whether to support them or ask them to follow your request.

Rinse and repeat.

It is hard for me to not be judgmental about stuff I disagree, and I can tell this attitude is causing more trouble than I would like in many different area of my life.

The main advantage of IntelliJ or any other IDE by JetBrains over Emacs, is that the out of box experience IDE provided, especially from a new programmer's perspective. All they need to do to click a button, check few checkbox, then IDE will resolve it for you and tell you what happened.

But to make Emacs do any complex behaviors, you usually have to write additional codes or configurations to glue different features together. Not to mention you need to read documents and debug it when there is an error. In JetBrains IDEs those are integrated already. A context-aware error detection and code inspection is available the second you open the IDE first time. That is something default Emacs can never do.

The main advantage on Emacs over IDEs, is that you can ask Emacs to do whatever you want as long as you know how to implement it. Practically speaking, you most likely will accumulate many little functions over time that is specific designed for your workflows. That kind of customizability is something IDEs cannot provide. I do not consider myself an Emacs power user, but I still benefit form it.

Emacs is also have better text editing features in general. You can use the same features no matter what text file you are editing. That's why people want to use Emacs for everything.

In short, they are different tools, use it where it is suitable for you.

For me, I whine about how bad the editor is when I use IDE, then I complain about how bad the integration my Emacs has between multiple tools (mainly my inability to make it work).

Hope this give you some ideas.

I'm suffering from work burnout and are planning to quit my current job to pursue a more balanced, self-sustainable way working for myself. Seeing your post help me understand I'm not alone.

I am having hard time figuring these out. So I rarely use environment variables.

I want to point out that Hong Kong people tried every way they can before this protest. They are aware the consequence.

However, when you want to do more advance configuration (e.g. write your own feature), you will need to learn more about Emacs lisp and Emacs’s API.

1. You quit right away. 2. You force yourself go to work and eventually burn out then quit.

Unless you are in a position that can influence the company, it doesn't worth your time to change it.

If you need the job now, invest more time and resource on yourself so you can move on to other place easier later.

Comments URL: https://news.ycombinator.com/item?id=18853508

Points: 10

# Comments: 0

1. They often express their opinions on topics like security and privacy. Like how things impact their users, where they stand, and how they plan to do. As a user I am happy to see a company actively talk about hard topics like these.

2. While they are not the most stable software service I ever use, but they always provide timely update. They also write postmortem to explain what happened technically, what did they do, and their future plans. As a developer, I am appreciated when a software company spent extra effort to acknowledge and explain issues of their service.

3. Their business model is simple. I pay money, they provide service.

1. You should not fail at anything.

2. You should not feel unfamiliar at anything.

3. It is your faults that you could not provide best answer for your clients.

But I think you will agree these ideas are unrealistic.

You will find out things that you know nothing about, and that is fine. Maybe next time when you are in the situation where you have to deal with uncertainty, just admit that you will not have the best answer, but you will have a good enough answer that is based on your experience and knowledge.

Book suggestions:

1. Feeling Good: The New Mood Therapy

2. How to Stop Worrying and Start Living

Both books teach me how to recognize those unrealistic standards I set for myself. I think they can help you too.