HN user

bacarter

108 karma
Posts22
Comments10
View on HN
explainextended.com 12y ago

Drawing fractals with PostgreSQL

bacarter
51pts5
janrain.com 12y ago

MyOpenid EOL

bacarter
2pts0
chrisdone.com 12y ago

Analysis of Emacs keys pressed

bacarter
4pts0
blog.23andme.com 13y ago

Citizen Scientists Look into Nearsightedness

bacarter
3pts0
www.xdd.org 13y ago

Fake US Identities

bacarter
1pts0
imrannazar.com 13y ago

Let's build a JPEG Decoder

bacarter
5pts1
explainextended.com 13y ago

Drawing a snowflake in PostgreSQL

bacarter
4pts0
www.postgresql.org 14y ago

Postgresql 9.2 brings covering indexes

bacarter
2pts0
www.cl.cam.ac.uk 14y ago

Towards Haskell in the Cloud

bacarter
2pts0
datamining.typepad.com 14y ago

Visualizing Lexical Novelty in Literature

bacarter
1pts0
postgresopen.org 14y ago

Postgres Open schedule published

bacarter
2pts0
pgeoghegan.blogspot.com 14y ago

Could Clang displace GCC generally? Part II: Performance of PostgreSQL binaries

bacarter
1pts0
research.microsoft.com 15y ago

Wearing the Hair Shirt - a Haskell Retrospective

bacarter
3pts0
mail.python.org 15y ago

CPython now in Mercurial

bacarter
2pts0
bitbucket.org 15y ago

Ian Bicking's port of doctest to JavaScript

bacarter
1pts0
mail.python.org 15y ago

Python 2.6.6 released

bacarter
3pts0
blog.persistent.info 15y ago

Page Fold animation with CSS 3D transforms

bacarter
2pts0
gizmodo.com 15y ago

Inside AT&T's National Disaster Recovery Batcave

bacarter
3pts0
dnsviz.net 16y ago

DNSViz - Visualize the status of a DNS Zone

bacarter
3pts0
www.mobilecrunch.com 16y ago

Mobspot Turns To Your Facebook Friends For Mobile App Recommendations

bacarter
1pts0
blog.comcast.com 16y ago

Comcast releases 'AFTR': Open Source IPv4 to IPv6 Routing

bacarter
19pts17
mobile.venturebeat.com 16y ago

Urban Airship raises $1.1M to provide infrastructure for mobile apps

bacarter
3pts0

ThreeFlow | Backend software engineer | Remote Only | USA | https://www.threeflow.com Hey! We’re an insurtech startup that has just announced our 45M Series B and is subsequently growing! In order to scale our engineering org, we're adding four backend engineers to help build out our APIs and integrations. We have done our best to create and evolve a supportive and inclusive culture that values perpetual learning. We also know there is always room for improvement which we actively work on.

ThreeFlow is and has been a fully remote company since the beginning, and has folks in Hawaii, Chicago, SF, NYC and beyond (in the US). Our company values are: Collaborate Enthusiastically, Work with respect, Constantly push boundaries, and Grow together.

Thanks!

Apply here: https://boards.greenhouse.io/threeflow/jobs/4325555003 or email me at brettcarter at threeflow dot com

ThreeFlow | Engineering Manager, Software Engineer, DevOps | Remote Only | USA | https://www.threeflow.com

Hey! We’re an insurtech startup that has just announced our 45M Series B and is subsequently growing! In order to scale an engineering org with intentionality and care, we're adding three engineering managers to join us to thoughtfully look after the expansion of our three product development teams.

I've thought a lot about how to position this role/job description so that people are successful from day one. I'm looking for folks who sincerely enjoy people management (hiring/mentoring/supporting the team) as well as perpetuating an inclusive working environment. If this sounds like you, please apply!

We have done our best to create and evolve a supportive and inclusive culture that values perpetual learning. We also know there is always room for improvement which we actively work on.

ThreeFlow is and has been a fully remote company since the beginning, and has folks in Hawaii, Chicago, SF, NYC and beyond (in the US). Our company values are: Collaborate Enthusiastically, Work with respect, Constantly push boundaries, and Grow together.

In addition to these Manager roles we’re also hiring for Front End, Back End, SDET and DevOps.

Thanks!

Apply Here: https://grnh.se/4fa713593us

This is a great article, raising many valid points around concurrent programming. I can't speak to Ruby, but Python supports, and has never presumed linear programming.

Python has had POSIX threads since at least 1.5.1. The standard library contains a set tools for concurrent programming (see the threading module, queue, etc) and many included libraries are thread-safe.

The GIL's behavior is complex, but even so it's still possible to write performant, multi-threaded code in Python, especially for IO bound tasks. See David's excellent write up: http://www.dabeaz.com/GIL/gilvis/index.html.

Everybody wants the GIL to be removed, and several attempts have been made, but the collateral damage seems just too great at the moment - C extensions, and tons of libraries, frameworks, and programs would need to be re-written at the cost of greater complexity, for questionable performance gains in the average case.

Backwards compatibility is a core philosophy of Python, one which I think makes it a great programming environment. This makes removal of the GIL more a philosophical problem than a technical one. Python 3 has made some progress in removing GIL contention, but it's certainly here to stay for the foreseeable future.

Perhaps Python will be left behind in the future due to these decisions, but given all the work being done, I find it hard to believe any argument claiming that the Python community isn't actively invested in concurrent programming.

Coffee! In Portland it's practically religion. There's at least a dozen microroasters and hundreds of coffee shops. My favorites: Spella (5th and Washington) Stumptown, and Barista (you choose the beans for your drink!)

It's important to encrypt your private key with a passphrase. Use ssh-agent to store the un-encrypted key in memory on login. On OSX 10.5 or greater, this is really easy: http://bit.ly/alDMhp. Make sure to add 'ForwardAgent Yes' to your ssh config, and then never have to type your ssh password again.

I used these for a commenting system as well, they're really quite amazing. There's basically three options when storing a tree in a relational database - adjacency lists which are slow to read, nested sets which are slow for writes, and materialized path, which is slow for moving around nodes. It's good to have a fourth option which is straightforward to implement and has excellent performance.