Does salary mean TC or just base? How are discretionary bonuses handled?

When ever i see "never implement your own...", i know i want to implement it myself. People say that about hard things, and I only want to do hard things. Nobody wants people who can do easy things, people want people who can do hard things. The only way to learn how to do hard things, is to do hard things, so do the hardest things.

So go ahead, write your own date library, your own Unicode font rendering, compiler, OS, game engine or what ever else people tell you to never do because its hard.

"Here's what people said:" before the actual list was super annoying.

> Allow single‑stair buildings up to 6 stories

This seemed like a terrible suggestion, but it caused me to google it and now I see it's not that terrible.

I didn't fully understand all of these, and some are clearly specific to California. I also worry about some of these opening the floodgates for greedy developers (a lot of existing laws are due to some developer doing something ridiculous, collapsing, and leaving the municipality holding the bag).

Overall I like the direction, though.

> For anyone who's debating whether or not jj is worth learning

I don't have any productivity issues with git, like... at all. It's not like I spend an hour running git commands every day.

I can totally imagine that some people spend their day manipulating repos with git, and jj is better for them. But that's not my case, and git is already everywhere.

To me it sounds like telling me: "You HAVE TO move to bim, the better vim. It's very similar to vim, but different enough that you have to learn new stuff. But you will be infinitely more productive: when you start bim, you're already in edit mode, so you don't have to type i! And the auto-complete in Julia is objectively a lot better in bim!".

Sure, but typing "i" a few times more is really not a concern for me, and I don't use Julia. But if it's better for you, please enjoy bim!

For now, that's the entire collaboration component. It would make sense to build a portion of document rendering in that context which won't be found in the open source portions. A value-add to convince users to subscribe.

But the majority won't pay extra for an ipad and a keyboard, when they can pay less for an air with everything included...

> it's a widely-used term/practice in tech writing

But it's not. You have got the key phrase wrong!

It's Docs as Code.

There are whole websites devoted to it:

https://docsascode.org/

Not "like": As -- meaning, "create docs as you create code", meaning "using the same tools and methods."

There is a good strong evidence that your version is inferior: the dozens of comments in this thread by people baffled by the phrase, or pointing out its flawed construction.

It's the Docs As Code approach, _NOT_ "docs like code".

https://docascod.github.io/howto/#/

https://marketplace.visualstudio.com/items?itemName=rafaelmn...

https://www.synesthesia.co.uk/tag/docsascode/

Both the startups I worked at and the mega corps are all on github or moving there from bitbucket. They are in a bit of autpilot mode in terms of useful new features aside from actions but I can't think of any new bitbucket feature since I graduated and started working.