euphemize

Awesome stuff, I really like this for the following reason:

While I do push data to github for various projects, I actually take part in 3-4 active, self-hosted redmine projects that would never be counted in the github graph. Same for a seldom-updated bitbucket project.

My time estimate included opening illustrator, layout out the code and printing it :)

If anyone wants the linux kernel on their wall : https://commits.io/builds/88548595a3c (or at least a chunk of it)

I find this service a bit expensive for something that can be made in 10 minutes with illustrator - maybe if I get fantastic glossy paper, but it doesn't seem to mention much about the paper specs.

For those having a hard time with the site color(s):

  (document.getElementById("content")).style.backgroundColor = "black";

This is interesting for GoPro (good client, huge promo), the fans (great new angles, different perspectives), but I like to see this as big upgrade for the NHL and the players too, as they rely more and more on cameras to enforce the rulebook, review plays, rewatch sequences, etc.. For example:

- Illegal & dangerous checks often come with a suspension, which is always dished out after video evidence is reviewed by the department of player safety - It's very common for goals to get reviewed in-game to check whether there was goalie interference, high stick, kicked in, etc. - All players watch countless hours of video during a week to improve their game and study their opponents (ex: shootout moves)

All in all, more power to the referees, more power to the coaches/players = better, safer, more entertaining hockey, IMO.

As others have mentioned, it depends on the sport. Something like hockey, where you need to go forward/backwards a lot, look out for 9 other players on a small ice surface and be constantly aware of your surroundings to not get leveled means tons of head movement -> not very pleasant to watch. Single player sports are better suited for this, or for specific replays of a few seconds.

They don't have the cameras on for normal games, it's just for the All-star game which is this weekend. It's notorious for being easy-going and low on hits.

Over the years in the startup world, I've realized there are just a few very fundamental things that I (personally) need to do to keep going. Especially in such an exciting / stressful / uncertain ecosystem, year after year. I suspect others have this too:

- Eat well - Sleep well - Sports (both individual and team)

If I do these things more often than not, odds are that I'll be productive, have good ideas, be able to execute on them and be generally happy. It takes discipline, but I could never go back to not doing these.

Thanks to the author for a really vibrant piece, I'm sure he'll be back on his feet.

For those who read till the end:

  The other test is to meet their significant other. What qualities did they choose in the person with whom has the most influence over them? We call these the “asshole acid test.

I like the idea, and would love to meet every candidate's SO, but I can't imagine how this would work out well, practically speaking. I'm also thinking in reverse - what if my SO's prospective employer requested to meet me - knowingly that the hiring chances will depend on how they read my personality...I'm not sure it's a great thing to put people through.

Cool, then Falcon is actually better off if it's suited for a more specific use-case like this.

Flask has a fantastic REST API extension (Flask-restless), so I'd go for a very targeted comparison between that and Falcon. Having more competition here can only be a good thing, I wish you the best of luck!

Came here to say this. In my humble opinion, the creator of Falcon should write at least 1 very clear paragraph to explain how this framework is better or just different from Flask. Flask is such an amazing piece of software, you'll need to make the case for me to use it much clearer than it is now. From its APIs to not having a templating engine included and strange things like hooks.to_oid, I don't see why I would use Falcon over Tornado or Bottle either.

It's true that people tend to force OOP onto python, especially when coming from other languages. But I think it's good to mention that in certain cases, keeping state by building a class is necessary, or at least easier than using a module-based approach.

  > The double checking costs a few CPU cycles but saves a lot of keystrokes.

Not sure I agree with this, idiomatic python should be explicit, even if it means more keystrokes.

Thoroughly agreed. As a developer who spent a lot of time studying humanities, arts and other disciplines requiring constant writing for grant submissions, essays, etc. a lot of skills required to be a good developer become invaluable for a dissertation and the other way around.

  >  A core skill in both disciplines is an ability to think clearly. The best software engineers are great writers because their prose is as logical and elegant as their code.

Personally, I found that combing through my text again and again and again to cut down on unnecessary words, combining similar ideas ideas and clarifying points made a huge difference, and was very much akin to optimizing software. It was generally something other students didn't really bother to do and their writing greatly suffered from it.

In our experience of ELB/SQS, AWS has done a good job on these services. A few things we noted:

- ELB takes about ~15 minutes to scale out completely when you hit traffic spikes.

- SQS is simple to use, rather cost-effective and quite reliable. It will add a bit of latency, but as the author notes, this can't replace Kinesis.

- The redrive policy on SQS is really nice to catch corner cases.

If I don't have webGL, it just shows a blank page. Would be useful to detect that and tell me to enable/upgrade - now it's just really confusing.

I'm very aware of what you mentioned but...all I "wanted" in this case is a visual separator in my terminal when I'm working with lots of output. I don't care whether each "* " refers to the same object, I just want a line :)

With that being said, if I want to merge two lists and apply an operation on each, I don't see what's the issue with:

    In [1]: a = [1,2,3]
    In [2]: b = [5,6,7]
    In [3]: c = a+b
    In [4]: c
    Out[4]: [1, 2, 3, 5, 6, 7]
    In [5]: d = [x*4 for x in c]
    Out[6]: [4, 8, 12, 20, 24, 28]

One of my favorites:

    >>> print "* "* 50

to quickly print a separator on my terminal :)

Previous discussion on python idioms from 300 days ago: https://news.ycombinator.com/item?id=7151433

I'm not sure if other languages have it, but I have to say that pycharm is excellent at suggesting chained comparisons to you. I didn't know this existed before I switched IDEs.

if 2 > 3 and 2 < 7

becomes

if 3 < 2 < 7

From the TempleOS: AfterEgypt video[1]:

"Now you're supposed to do an offering before you talk to God. [...] just get conversation, maybe being witty and charming - or praise - like 'praise god for sandcastles and snowmen and bubbles and popcorn'...hum, I'm gonna praise him for something new, which is isotopes! Like you have Carbon-14 and stuff like that. I think that's pretty cool. Didn't have to be that way, maybe...Ok here we go!"

Fascinating.

[1] https://www.youtube.com/watch?v=RzhRYGm_b9A

Great article, a lot of these points really hit home with me, as we've been using queues to process a lot of our data in the last few years. I think if you consider your queue being fine while having items backed up under normal conditions, you're going to have serious problems to deal with as soon as you hit 1) more input 2) you get a nasty bug in your system 3) often a combination of both.

As an aside, I really enjoy working with AWS' SQS queues, as they allow you to define a maximum number of reads + a redrive policy. So you can throw, for example, items in a "dead messages" queue if they were processed unsuccessfully 2 times. We use this to replay data, stick it almost immediately in our unit tests, and improve software incrementally this way.

Also pretty confused as to what this does. There's a few examples and sample code for initialization, but I have no idea what the use cases are, what type of "backends" I could build with this, how it's better/different than popular existing frameworks, etc.

Most tips here are very good, suggesting books ("Clean Code", etc.), team huddles and showing them the way. But you seem to be implying that they could be great coders - if they wanted to.

I can't help but feel like these programmers aren't very passionate about their code, and that's what you need to help them with. If they're naming variables wrong and hardcoding strings, but understand the asymptotic running times of what they're doing, I'd go on a hunch and say they're bored or unmotivated.

I say this because I recognize myself in some of these behaviors - when I want to get rid of something and don't care much about the project. "What's the fastest shortcut I could take to get me out of here?".

FWIW, many other python web frameworks use the very same pattern.

Used Tornado, django and flask quite a bit, web.py only once. As others have mentioned, it didn't work that well, and the community around it is smaller than other frameworks. Again today, Django seems a bit cumbersome, Tornado works well but has a very low bus factor.

Pretty sure flask is currently the front runner in "python microframeworks".

Much agreed with your points. In addition, this part:

"Your profile also gives our matchmakers a glimpse into what you’re like as a real person, but don’t worry - we don’t base too much of our matching on your photos that your friend took that one time at that party after a few glasses of red wine :)"

...really terrifies me. I need to trust that the people doing this selection understand the context of my pictures while not knowing me at all? If I'm serious about finding a match using this service, I will gladly spend a full hours filling out a form telling you more about myself, rather than giving you access to my FB account.

I figured you meant something more subtle than a big red flashing light, but here's the thing:

A) The difference between a clean hit and a dirty one is a matter of milliseconds. Players who dish out the hits can do very small things at the very last moment to try to hurt an opponent and I don't think any sort of warning system will help you with that. The time needed to react is way too long and you would need to be able to detect 'malice' in someone's intent, which is not exactly easy.

B) Pro sports players are known to hate additional equipment, gizmos, protection extras, etc. even if it means reducing their own safety. Hockey players get hit in the face with sticks and pucks going 100 mph all the time, but still prefer to not wear a visor because they find it "more comfortable". They don't care if they're completely toothless (they actually see this as an honor - many don't get work done until they retire), as long as they can play unobstructed. Same with braces and pads, players will never wear them (and players' associations will side with them) if it means gaining half an inch on the pitch.

Unfortunately, I don't think any amount of technology will help here. We need to change the way people think about contact sports (someone in this thread mentioned its likeness to wresting) and change the rules to protect the players better.

No NFL player would ever want to have an "alert in their helmet" if they're about to get hit. That sounds horrible and panic-inducing more than anything else. The NFL needs to follow other leagues, like the NHL, and simply ban dangerous hits to the head and blindsided hits altogether. There's a lot of resistance, but it's slowly making a difference.

Enforcing knee braces, putting weight limits for linemen and making an exception for marijuana will also never work IMO. Also, players have access to very strong pain killers via team doctors, they don't need marijuana for pain.

Downloaded the app, first screens look good. I would definitely use something like this, living near a huge park in a big city, and being very active. However:

- I don't have Facebook, how do I create an account?

- Do you really, really need accounts at all? And if you do, can't you at least just show me activities happening around me, and let me sign up later?

I'd love to give more feedback but I'm stuck outside your app.

I'm currently studying for multiple interviews at "established" tech companies, and I wonder where the interviewers like the author are. I've already finished a few, and between having to implement a linked list, analyze a matrix, describe hashmaps and regurgitate sorting algorithms, the questions have not had much to do with everyday coding.

I'd be really happy to discuss how to implement feature X in an app, or how to design the moving parts of Y for a particular infrastructure and talk about the tradeoffs each implies. But I guess I'll get back at implementing a queue using 2 stacks, because that's what technical interviews seem to be for.

I think ORMs like SQLAlchemy are really useful for many many use cases. I don't think most people who work with ORMs deal with the kind of complexity described by the author, let alone work on such a specific application for 30 months at a time. In that sense, ORMs are super powerful tools that cut down your work, shortens your code and do nifty optimizations once in a while

With that being said, this article totally resounds with me, having resorted to using direct SQL in almost all of my large-ish projects. Using an ORM always starts out nicely, and then eventually it gets messier and messier. Specifically, when your DB data has subtle interactions with a cache, I have found it harder to keep ORM code clean and readable.