Lamy 2000 is so amazingly smooth. I really like having the piston fill, instead of cartridges and adapters. There's more ink, and it's more reliable with less fuss and mess.
Anyone have an example of taking a low functioning team to a high functioning one? Building trust, changing culture.
It's one thing to just say "here's the ideal".
And another to say if you're in a sub-optimal place, "just leave."
But how to change a poor habit place into a good habit place.
I don't think bad habits really go away, they get drowned out by the better habits. I think the same is true of teams. But, IMHE, improvement has been hard to come by.
I presume most people here at still ICs, so I don’t think there is anything you can really do except get into a leadership position and change it yourself.
The best thing I’ve done for psychological safety is by creating groups within the team that are willing to share feedback with each other. As long as there isn’t a bad manager involved or people who are incentivized to sabotage work, we do okay. But, ultimately, it’s unproductive and we all end up looking for new jobs in the end anyway.
I’ll admit I haven’t had every manager in the world but it feels like the manager ultimately decides the psychological safety of the team in the end. If they want it to be unsafe, you can’t do anything about it.
Being able to have a customer accept what the output looks like and then listening to when the page changes would be great for giving non-technical people control over passing tests.
For one, taskwiki, which if you use task means you have a great way to bang a checkbox in a vimwiki file and have that create a task.
MY company uses outlook so I sync the outlook calendar to khal using vdirsyncer. I then can use a (really janky) vimscript function of my own devising to add the calendar and some standard stuff to a "daily note". So I go <leader>ww and it creates a note for the day and adds my calendar and then I use that for all the basic notes for the day.
vimoutliner for when I absolutely want an actual outliner to do some planning. It's not always the right tool, but when it is, it's great, and it integrates perfectly with fzf. The other thing is that because notational-fzf is just doing a fuzzy find over text, I point it at all my sourcecode dirs for immediate jumping to particular files, functions etc in sourcecode.
This is how the system currently works. The best financed (so: most popular with business people) candidate gets heard the best and often times is pretty easily elected.
(edit like a timelord!)