> I've personally seen a building with a fractional street number, in Kingston, Ontario, Canada.
There's at least one fractional street number here in Victoria, BC along Fan Tan Alley: https://www.flickr.com/photos/goddess_spiral/3377009251/
767 karma · joined February 5, 2010
Contact:
https://angel.co/cyranix (AngelList)
http://cyranix.github.io (profile, currently outdated)
Location:
Seattle, WA
Currently:
CTO at Hazel Analytics (Seattle, wA)
Selected history:
Developer at Socrata (Seattle, WA)
Developer at Moveline (Las Vegas, NV)
Developer at MyEdu (Austin, TX)
Rice University (Houston, TX), B.A. in linguisticsThere's at least one fractional street number here in Victoria, BC along Fan Tan Alley: https://www.flickr.com/photos/goddess_spiral/3377009251/
I know there are some entrepreneurial efforts being made at my alma mater, but overall it feels like a huge missed opportunity. The business school is strongly walled off from the undergrad population, the excellent CS department tends toward the academic side (with rare exceptions like COMP 410/415 [1]), and personally I never saw much of an attempt on the part of the local tech scene to get students integrated. There is the Rice Alliance [2] but it isn't quite the same as an organic grassroots-y scene.
[1] http://www.bandgap.cs.rice.edu/classes/comp410/ [2] http://alliance.rice.edu/
Remote: Preferred
Willing to relocate: Yes
Technologies: JavaScript (jQuery, Node, Angular, learning React); PostgreSQL; MongoDB; Java; PHP; plus experimentation or quick hacks in many others
Résumé: http://cyranix.github.io
Email: andrew.m.harrison+hn@gmail.com
I am most interested in organizations with opportunities in a social-good space such as education, health, the environment, or justice.
{ use, pipe, get, eq } = R
propEq = use(pipe).over(get, eq)As a newbie coming into Elixir without either Ruby or Erlang background, I didn't find anything in the syntax to be a real pain point (although understanding optional parenthesis usage in CoffeeScript did help).
Can you provide a little more clarity on what the Photon Kit listed in the store consists of? The short description says "several sensors" and the description in the modal is even more vague with "a couple of extra surprises".
This makes a lot of sense given the blog post a few days ago from `sama [0] — the evolution of YC from incubator to "meta-company" or network facilitator could only be helped by having more late-stage expertise on hand, so nodes don't drop out of the network.
[0] http://www.amazon.com/Odd-Bits-Cook-Rest-Animal/dp/158008334...
My not-at-all-certain observations are that 1) DotA's jungle is more complex and perhaps a bit larger and 2) DotA's terrain behavior is more advanced [tree removal, cliffs overlooking the river]. These factors would probably make it more difficult in DotA to place wards in the jungle in a way that is highly likely to yield solid intel — you can get a fairly good amount of safe coverage with a defensive ward on the cliff near river, as well as along the river exit once you've advanced past the river. To the best of my knowledge, you're just not going to learn as much from jungle wards in DotA, because of the sight lines and the difficulty of enemy jungle invasion (and perhaps because of the random invisibility rune spawns, though I don't know how much of a factor that is). Contrast all of that with LoL: accessing the enemy jungle is comparatively easy, and key ward placements on the enemy side (especially tri-brush, blue buff brush, and river junction at wraith camp) are almost certain to be high-information investments.
Additionally, in LoL you have to teleport to a friendly creep, structure, or ward; the secondary nature of a ward as a rally point is something that increases the stakes of ward superiority. In DotA (if I'm not mistaken) the teleport limitation is not the same, so the pressure is not the same. I'm sure there are also itemization and ability factors that I have no knowledge of whatsoever. If I'm horribly wrong on this, I welcome a more experienced perspective!
EDIT: `chc has more specific intel on the wards themselves. The team-wide limit on observer wards is a distinct difference!
An example that indicates the difference between last year's world championship games and this year's is the ward system. Wards are items that a player can place near their current location, invisible to the enemy team, to gain vision into the fog of war, which is vital for decreasing risk in map-wide coordinated team strategies. Under the old system, pro teams often bogged down during the mid- and late-game phases as they vied for map vision superiority, and the only viable strategy was to purchase as many of the superior ward type (pink, with green being inferior) as possible and equip at least one player with a long-term ability to see invisible elements. Under the new system, both green and pink wards are valuable — the former are invisible to enemies and time-limited, the latter are visible to enemies but can detect invisible elements and are not time-limited — and all players have access to a periodic ability to place an extra ward or shut down enemy wards. As a result, the action in this year's matches has been much more consistent, as teams can still angle for vision control without losing momentum.
Just today, I saw some rough notes (http://boards.pbe.leagueoflegends.com/en/c/champions-gamepla...) on changes being tested in public beta. The scope of changes is massive! Starting stats, behavior of towers, and the range of temporary buffs are all on the table for a major revamp. It would be really easy for Riot to resist improving their game under the excuse of "this is the way we've always done it", but they continue to push and innovate from within. A great example of keeping a startup mentality alive within an established company!
=====
On another note more closely related to the posted article: for anyone that doesn't already watch pro-level League of Legends and is interested based on this article, you can follow the remainder of the current world championship matches through http://na.lolesports.com — the next best-of-five between two Samsung-sponsored teams should be very exciting. Past matches are available via http://na.lolesports.com/vods/league/worlds and I would highly recommend the Fnatic vs. OMG game from the group stages (direct link: https://www.youtube.com/watch?v=O345c46mFqY).
As a personal reflection I suppose it's a decent piece of writing, but I wouldn't call it a strong argument — at least not of HN caliber. The author focuses only on social dynamics and personal psychology, avoiding any pragmatic points such as focused practice to improve efficiency or the economics of ingredient availability and value of kitchen labor.
Also, as a man who cooks with other men and women, all of whom respect the importance of good food and the people who make it... I feel badly for someone whose view of the world includes this massive overgeneralization:
> People cook — particularly women, but not only women —
> because they think people are going to notice them,
> and love them, but almost no one thinks about who made
> what they're eating or how it got on the table. They're
> just hungry, and they eat, and they sometimes say thank
> you, and then they forget about it.2. Most of the time, I plan a week at a time, but that might only be three or four dinners, as I plan on leftovers and usually eat out once a week. I keep a running list of meal ideas next to the week's plan on a whiteboard in my kitchen.
3. I try to stick with seasonal vegetables and that often guides my meal choices. I cook for/with vegetarians, vegans, and people with various allergies these days, which sometimes changes my plans; I get more latitude when cooking for myself. Green curry (with paste made from scratch) is the dish I'm most often asked to cook for groups; pulled pork and braised leg of lamb are also quite popular. I try to rotate through various protein sources during each week (including meatless), and while meat is often a star of my meals, they're mostly vegetables by at least a 2:1 ratio. Oh, and there's usually one meal per week that's stir-fry to use up lingering veggies.
4. No specifically named diet. I began to cut back on breads and sweets a couple of months ago to help shed a few errant pounds (I'm moderately fit at 135 lbs now), but other than that I generally eat what I want. I never drink soft drinks, rarely drink alcohol, and choose snacking carbs wisely.
5. I feel like most productivity hacks are geared towards squeezing every bit of efficiency out of one's time. While there are some useful common-sense ideas — establishing mise en place, caring for your equipment, etc. — I usually encourage people to tackle efficiency from the other angle. Instead of fretting about doing a lot in a little time, slow down a bit and carve out plenty of time to make a meal well. Meat needs time to get tender, bread needs time to proof, etc. The main thing I encourage new cooks to do is invest in spices, because having a solid core set of them makes a huge difference in the quality of results and new cooks are sometimes hesitant to try recipes that call for spices they don't have on hand.
tl;dr: full-stack JS (Express + Angular), MongoDB, Golang, web + mobile, remote, high impact on real customers
== The position ==
* Solid full-stack experience, preferably with JavaScript both
server-side and client-side
* Passion for clean, correct, and maintainable solutions as well as modern
development practices
* Bonus points for experience working with remote teams, devops skills, and an
eye for design
* Strongly self-motivated but eager to collaborate on tough problems
* Don't care if the moving industry isn't sexy
* Would rather make money than make the front page of TechCrunch
(though we do that too)
* Supporting web and mobile offerings for customers plus an internal web
app for our operations team
* Primarily working in a MEAN stack (MongoDB/Express/Angular/Node) with
a bit of Golang
* Evaluating new tools and technologies for real use cases, not just to play
with shiny new toys
* Shipping every day with continuous testing and deployment
* Small, tight-knit, self-managing, and highly communicative team (half
of us are remote)
* Deeply involved in understanding the business and creating long-term strategy
* We love Maker Day [4], board games, and hanging out together in
downtown Las Vegas
Moveline is transforming an industry older than the internal combustion engine: we build software that dramatically improves the customer experience, end-to-end, around moving. We're helping real people every day and excited to tackle more of the problem space.
* Techstars NYC 2012 graduate [1]
* 2014 TBAN Las Vegas Tech Transplant of the Year
* Located in the heart of Tony Hsieh's Downtown Project [2]
* Well-funded by world-class investors and advisers [3]
MENTION HACKER NEWS WHEN APPLYING! - We have hired from HN before and consistently see the best candidates coming from these threads.
[1] http://www.techstars.com/companies/stats/
[2] http://downtownproject.com/
[4] http://www.fastcompany.com/3029158/agendas/why-your-office-n...
Well-formed HTML is the exception rather than the rule and page navigation is often "interesting". Sometimes the school's system will use software from companies like Sungard or PeopleSoft, but there's customization within that... and of course, there's no incentive for the schools to aggregate this information in a common format (hence MyEdu's initiative), so there are plenty of homegrown systems. In short, there's no one-size-fits-all solution.
* NOTE: If you do attempt this, I insist that you teach throttling techniques from the very start. Some schools will IP block you if you hit them too hard; other schools have crummy infrastructure and will be crushed by your traffic. Scrape responsibly!
* If the credentials have already been written into shared history (e.g. merged into origin/master), regenerate the credentials ASAP. If the credentials are in local revisions only, use interactive rebase to edit the commit(s) in question.
* Introduce tooling to create better separation between dev and production credentials. Most automated tests should be able to run using bogus credentials. Pre-commit hooks can attempt to scan for accidental credential inclusion. Use a config system that loads credentials based on environment.