165 karma · joined June 5, 2016
I know tamarind trees aren't native to the Western hemisphere, but that hasn't ever stopped us before.
This really comes out in corporate mission statements. Even if you're Xerox, your mission statement is something like "Improve the rate of business communications by creating the world's most excellent copy machines."
If you don't have an idea for a startup, you're missing the key ingredient. The team literally cannot exist without that visionary person who knows exactly what they're after.
I should point out that they lost nothing by this.
An employer who sends nasty emails and withholds pay is ruining the possibility of a valuable future re-hire, causing needless guilt, turning his own employees against him, building himself a poor reputation, and begging for a lawsuit. It's a heavy price to pay for his own pettiness.
- TypeScript annotations everywhere
- Unit tests (via AVA)
- Several bugfixes for line comments, block comments, and more
It's more useful than ever.
One of my first jobs was as a dishwasher at a pasta shop. A few of my friends worked there and helped me land the job. One of them, Kevin, was a particularly good dishwasher--fast, efficient, conscientious. The managers were vocally appreciative of his work and used him as an example.
One day, I was talking to one of the other friends, Macey, and I mentioned that I thought Kevin was probably up for a promotion. The career path at this pasta shop was dishwasher > cook > waiter > manager, and at a place like that you could move up pretty quickly because turnover was so high. Macey said with some confidence that Kevin would never get promoted. He was just too fast at washing dishes. He'd made himself indispensable, especially on high-traffic evenings, and the management would never gum up the works by moving him to another position.
Macey was wrong. Kevin was promoted to cook within a few weeks.
I guess there are managers who won't promote their most productive employee. And there are managers who will.
I'm building a prototype of one of our actual landing pages in each framework to get a bird's-eye view of what works and what doesn't. So far I've been really impressed with Vue, but my team has a couple of objections from the outset:
1) Most mid-level developers haven't heard of or used Vue, so the pool of candidates we can hire as our company grows will be smaller if we switch from a common denominator like AngularJS to something relatively unknown like Vue. I personally love to learn new tech, but not everyone does and a "Vue developer" job posting may not get a lot of hits.
Then again, if (e.g.) 15% of devs want to use Vue and only 10% of companies use it, that's a clear advantage over 75% of devs wanting to use Angular and 80% of companies using it. I wouldn't be surprised if the numbers worked out like that.
2) Vue is kind of a one-man band, whereas Angular and React are backed by large cap companies. This is the weaker argument IMO, since there's no law stating that Google and Facebook can't run up on hard times and decide to drop support for their open source projects. And after seeing how sloppy Angular's documentation is, I've lost a lot of confidence in the "bigger is better" argument. However, in a rational universe, it may be fair to say that Vue would die more easily than Angular would.
My view on the situation is that it's better to use the right tool for the job and have less developers/support than to use the wrong tool for the job and have more developers/support. But I'm more technically-minded than business-minded, so I understand that I might need to be open to business concerns outside of my normal decision-making criteria.
I'm keeping detailed notes as I compare frameworks, so I may do a write-up when I'm done if anyone's interested. (Although the "battle of the frameworks" genre has been done to death...)
I haven't played Legacy, because on principle I won't buy a game that can only be played a set number of times.
In conclusion, get off my lawn, I guess.
My favorite games are either very simple or designed to absorb complexity into familiar devices, like decks of cards and well-designed boards. And they thrive on a deceptively simple mechanic, a few difficult decisions, and a sense of urgency. Pandemic, Dominion, Ticket to Ride, 7 Wonders and Quadropolis come to mind. Each of these is clever, not just because it adds another "thing to keep track of," but because it asks you to do something that seems easy and is not.
I am speaking out of ignorance a little, though, since I haven't played many eurogames (and probably don't have the patience for any game that takes longer than 90 minutes).
CSS Grid and flexbox are a nice improvement over what I had to work with in, say, 2010.