brennvin

> The problem is they can’t justify your cost if you go outside the planned work load

Cost? It's a freebie. I'm still doing my tasks, in addition to saving them tons of money with better tools.

> but it’s one you made up.

You just made a bunch of things up.

> Creating new work

I am not talking about creating additional work, I am talking about solving problems not on management's radar screen. Some problems are only visible from the floor.

> The right way to grow is to learn how to work with the company to get important work into the roadmap.

That is not always possible because valuable things sometimes have to be demonstrated to be understood. Not all things can be explained in the abstract, sometimes you have to build the thing first before people understand how useful it is.

I suppose it varies a lot from one organization and industry to another. My experience is that managers don't like it when people rock the boat, they prefer their subordinates to just quietly execute the tasks given to them. Growth-oriented people like myself are sometimes seen as a problem because they cause things to happen that are not in the road map.

In my field (fin tech) managers often do not have the background to be able to assess the value of spontaneous technical contributions. So they assume that if something was not planned and requested by management it did not need to be solved.

I assumed it was meant to evoke William of Occam.

Tokenizing everything in one go is usually the right approach. The typical case is the error-free case, so you won't actually tokenize more characters than necessary, but you will simplify the implementation and avoid jumping back and forth between parsing and tokenizing (thus improving locality).

Random tidbit: Wasavi sounds like Swedish for "what did we say".

Good idea! If we do away with f strings entirely the problem does not occur.

What if the compiler issued a warning if the f was missing and let you suppress the warning with an r?

"Codes" is correct when the intended meaning is access codes and the like, but not for source code, which is a non-countable noun.

I think the uptick is due to the increased number of participants who are not native speakers, mainly from Asia and eastern Europe I would presume--I'm not a native speaker either but the distinction between countables and non-countables is natural to me, coming from another Germanic language.

> Then why haven’t you?

I found another product opportunity that will be faster and cheaper to build. That I believe I could out-compete Figma were I rich does not mean I _am_ rich.

Thanks for the down vote.

I'm surprised Figma is worth that much. For a while I was considering bootstrapping a business in this space and I was never very impressed with what I saw of Figma. Does not look that hard to compete with or replicate.

I have never understood why (some) people want to write lexerless parsers. Lexing lets you approach two different concerns separately. What is not to like?

> Last indigenous people of Europe

There are still many Swedes, Finns, Germans, French etc around.

- A tracing garbage collector

- Tail call optimization

- Closures