Definitely on my list of games I wish I could play again for the first time.
145 karma · joined February 15, 2012
Definitely on my list of games I wish I could play again for the first time.
(Confirmed with the pie chart in your first link.)
Interested in other recommendations too!
After about 4 days, I regained some ability to differentiate between salty/sour/sweet, but it’s been in and out for the last 2-3 days. I accidentally poured too much mustard on a sandwich at lunch today and could not have told you there was any mustard on it at all in a blind test.
- Collaborative editing was very solid, even with one of us using vim extensions and the other one not. (This has caused me some pain in Screen.so in particular.)
- The leader/follower model was slightly unintuitive at times. I vaguely recall Floobits allowing either participant to e.g. create new files, but in GitDuck the leader has to share them to the workspace for them to become editable. (I might also be misremembering this from the Floobits days, but it was slightly confusing.)
- Similar to ^ - when I was not leading, I couldn't summon the leader into a file I was editing, so I had to tell him when I was switching files. IIRC Floobits let you take yourself in/out of follow mode, even as the leader, so you would be automatically summoned when the other person switched files.
- Looking forward to terminal support - glad that's on your roadmap :)
- Our team is 50/50 between vim and VSCode right now, so we're looking forward to vim8/neovim support to really feel the power compared to Screen.so and Tuple.
Overall, had a surprisingly smooth experience for Day 2. Congrats on the launch and looking forward to future updates!I’ll give this a shot tomorrow with some friends and see how it goes!
I'll also call out places where I'm not happy with the implementation, looking for feedback, etc.
I agree that the terminology could be more clear, but it seems like they borrowed existing lingo from recruiters here.
I like your design choices here. Did you use an off-the-shelf theme, a toolkit like Bootstrap/Tailwind, or is it all custom?
If you would want to make a move to backend/full-stack, you might need to pick up skills like databases, queues, caching, building APIs, and DevOps. But good companies are willing to bet that you can pick up new skills on the job if you have some sort of foundation.
>The research is based on a survey of creators for thousands of Kickstarter projects between 2009 and May 2015.
From the paper:
>This suggests that the taken-for-granted assumption among scholars that entrepreneurship is best performed by teams should be reevaluated, with implications for theories of team performance and entrepreneurial strategy.
The claims in the paper are pretty limited and based on a questionably representative sample. Extrapolating to "solo founders are better" seems like a leap at this stage. The results seem interesting and worthy of further evaluation, though!
It can get a little slow for larger boards – we did multiple weeks of branding iteration in a single board with hundreds of images and sticky notes – but overall I'd highly recommend it.
Some interesting nuggets:
- Al Lowe basically invented beta testing at Sierra for Leisure Suit Larry. He wrote a program to capture user inputs that didn't work onto the floppy disk, which the beta testers then sent back to Sierra. They then updated the graphics, text, or parser to account for these confusing areas.
- Ken Williams was quite a visionary on several things, including the rise of IBM compatibles, MS-DOS, and the early internet / social networks.
- Lori Cole's vision for Quest for Glory, using a cardinal direction, a season, and an element as inspiration, was really fascinating to reflect on. (I have a soft spot for Quest for Glory IV's Eastern European mythology, which was very rare in the pre-Witcher days.)
- There was a failed merger between Sierra and Broderbund (Carmen Sandiego, Print Shop, Prince of Persia) in the early 90s that could well have changed the face of the industry.
Overall, was way better than the average internet rabbit hole!
OrderNova is building an order management SaaS platform for retail and wholesale bakeries. We help small businesses across the country deliver happy birthdays and drama-free weddings. We've been in the business for 10 years and decided to bake our learnings into a brand new Rails + Angular product.
We're seeking a Software Engineer to lead our development efforts. You will have a key role in determining OrderNova’s technical design, development, testing, and implementation, reporting directly to our owners. You will also build our engineering team from the ground up. We expect to add at least one junior engineer in 2018 as well.
The stack: Rails, Angular, RxJs/ngrx, Heroku
A little about our culture and company:
- We work to live, not live to work
- We're casual, friendly, and customer-oriented
- Although we've been in business for a while, this is a bootstrapped startup opportunity
We'd prefer Indianapolis local, but we're open to remote given the following qualifications:
- Previous remote experience
- Ability to overlap roughly with US Eastern time zone
- Willingness to travel to Indianapolis for onboarding and semi-annual team events
You must be authorized to work in the United States. We are unable to sponsor visas at this time.
If you are up to the challenge of developing a robust application in a fun environment and are serious about making the world a sweeter place, email join@ordernova.com with your resume and a couple sentences about what attracted you to us. Also include the word "sourdough" in your subject line to prove you are not a robot, or that you are at least a sophisticated robot!
Was a really interesting and well-done talk, IMO. I am not a type system geek, but thought it was fascinating to hear all of the tradeoffs that go into designing a system like this.
I really enjoyed Brad Feld's post[1] on choosing how to use each social network you sign up for. On LinkedIn, I've decided to be a public, promiscuous consumer. On Twitter, I am public, selective, and a mix of consumer/producer. Facebook is one that I probably need to cut even more than I do, since I don't have a strategy and get little value from it.
Social networks can be tools, and if they are not providing value, it may mean you need to use the tool differently or get rid of it if it doesn't solve a problem you have.
[1] http://www.feld.com/archives/2012/02/happy-birthday-im-unfri...
Popularity seems like an anti-goal unless you're selling something.
Maybe I missed something, though!
There are potential downsides such as increased politics or income inequality pressures, but it seems like a viable policy at least. I'm curious how someone like Google's Laszlo Bock would respond to this approach in comparison to their "pay unfairly"[1] mentality.
[1] http://www.businessinsider.com/google-policy-to-pay-unfairly...
For example, right now in a Google Doc if I want to connect it to a Trello list I need to add a bullet for each card in the list, make it a link to the card, and keep both things in sync. What if I could just drop in the whole list (or even a whole board in some cases) and have my project plan and my specific cards in the same context without jumping between different tools? That's a killer feature for me if they can pull it off.
Would be nice to have a link to whatever syntax highlighting library is used under the hood for this, but overall works pretty well as a test for me.