* fear of writing original ideas, both natural language and code - agree
* the inability to measure things - who said this is something that is necessary at all stages? sometimes you just need it done. when you have 1000 people teams selling to enterprises, sure. If it is you and your buddies, no need to measure, necessarily.
* preference towards bias - Why? If it works, a good engineer won't go to the newest tech/framework. They will stay with their biased favorite.
* cognitive conservatism - Disagree. See previous comment
* inability to form assertion criteria - Not exactly sure what you mean, but if you mean to reason about code and state at various points, then I agree
> Maintaining Culture: As the team grows, it's vital to preserve the company culture and ensure new hires align with core values.
I honestly disagree. You should allow the culture to evolve, but make sure it doesnt evolve in a direction that is different than where your values are now.
As an analogy, if you have a child who is 3, their culture is "energy", "constant learning", and "being cute". When they are 13, they should evolve beyond #3. And, they probably should add "be social/fit in", and "do good work (on homework etc)"
If you try to keep the 13 year old on the "being cute" value, you'll miss out on a lot
Meeting in person >1 hour away is difficult for people in many life circumstances. And if there are constant meetings, it either strains families or makes the person who can't make it feel left out
Totally disagree. For introverts, "everything public in slack" means that I would rather not say something than have 50 people see my thoughts/rants/silly questions in public
Thanks. I appreciate the encouragement. It was definitely pretty slow at the end of the year.
It isn't about getting responses though. That is generally fine, from what I can tell.
It is more that I feel like every company wants to talk, and they want to test you, but really are not interested in hiring even if you seem like a good candidate.
E.g. they want to wait for other candidates, are slow in scheduling, have tons of required interviews where they ask similar things
Wonderful point. There's a Doctorow article I read somewhere that essentially put forth the following logic for digital distribution:
There will be a group of people who would not acquire the content unless it was digital. They may buy or pirate it. This is the group of interest. If more people who weren't going to get the content (b/c of lack of exposure, lack of interest, etc.) pay for it than don't pay for it, the digital venture is worthwhile (This ignores that some people who would have bought it non-digitally may pirate it, though that group is small; if you wish to support to movie by paying for it, you'll most likely do it regardless of medium)
For example:
100 people would have bought the movie if it was only physical.
100 other people will have never heard of the movie unless it is released digitally.
Of these 100, 75 people buy the movie, 25 pirate it.
By listing it digitally, the publisher gets 175 people's worth of profit, and 25 people's worth of "loss". Therefore, it is worth listing digitally.
Background checks will show where you've worked, unless you were getting paid illegally. Still, I agree with you. It isn't something to scream out loud.
Why would I write tests for Tic-Tac-Toe? It's insanely easy to exhaustively hand-test, or just look at the code to see its validity. If you expect tests on something that simple, then you're expecting people to waste 1/3 of their time testing code that is sure to work.