HN user

grk

1,184 karma

contact: gkolodziejczyk at google email service

Posts45
Comments139
View on HN
weblog.rubyonrails.org 4y ago

Rails 7.0 Alpha 1

grk
2pts0
ma.tt 5y ago

2021 Streaming Kit

grk
1pts0
weblog.rubyonrails.org 5y ago

Rails 6.1 RC1

grk
4pts0
discuss.rubyonrails.org 6y ago

Why is Rails boot so slow on macOS?

grk
1pts0
blog.alexmaccaw.com 7y ago

Zone of Genius

grk
1pts0
www.reddit.com 8y ago

Optimal CPU Tuning settings for i9 MBP to stop VRM throttling

grk
5pts0
maciejgalkiewicz.com 8y ago

What I’ve learned as a CEO from a year of self-set salaries

grk
1pts0
www.weforum.org 8y ago

The countries where people work the longest hours

grk
1pts0
qz.com 8y ago

Start-ups shouldn't try to be unicorns–they should be zebras

grk
1pts1
arstechnica.com 8y ago

Siri can’t talk to me: The challenge of teaching language to voice assistants

grk
8pts0
www.anandtech.com 8y ago

Intel Announces 8th Generation Core “Coffee Lake” Desktop Processors

grk
89pts42
blog.phusion.nl 9y ago

ActionCable Under Stress: Finding a DoS Vulnerability in Rails 5 WebSockets Apps

grk
1pts0
blog.ragnarson.com 9y ago

Blockchains: A brief introduction

grk
10pts0
blog.ragnarson.com 9y ago

Developing as a developer: a journey through learning

grk
73pts7
blog.heroku.com 10y ago

Introducing Heroku Private Spaces

grk
162pts45
www.ruby-lang.org 11y ago

Ruby 2.1.4 Released

grk
16pts0
github.com 12y ago

HTTP API Design Guide

grk
9pts0
coreos.com 12y ago

CoreOS Beta Release

grk
253pts37
shellycloud.com 12y ago

Managing assets with Rails Assets

grk
5pts0
shellycloud.com 12y ago

Hide your staging environment from Google (in Rails)

grk
5pts5
shellycloud.com 12y ago

Adding search and autocomplete to a Rails app with Elasticsearch

grk
14pts3
shellycloud.com 12y ago

Why GlusterFS should not be integrated with OpenStack

grk
33pts23
shellycloud.com 12y ago

Life of an HTTP Request

grk
66pts7
blog.shellycloud.com 13y ago

The pesky problem of freezing thin servers

grk
3pts0
blog.shellycloud.com 13y ago

How to find a marketing person?

grk
22pts11
blog.shellycloud.com 13y ago

ForwardMachine - dynamic port forwarding

grk
3pts0
blog.shellycloud.com 14y ago

Using Rails tagged logging for better bug reports

grk
22pts0
zachholman.com 14y ago

Word of Mouth

grk
5pts0
github.com 14y ago

Puma: A Ruby Web Server Built For Concurrency

grk
37pts25
leaflet.cloudmade.com 14y ago

Leaflet - a modern, lightweight JavaScript library for interactive maps

grk
1pts0

Not sure how it works with MySQL, but with postgres the most common pooling options use transactional mode, which doesn't support LISTEN/NOTIFY.

The problem with postgres-backed queues is they can't be used with connection pooling, so your workers are unnecessarily using up DB connections.

Should I set channels on the APs in some specific way?

We're using mostly apple hardware + ubiquiti APs, and to be honest I expected everything to "just work" with the defaults...

Does roaming devices between APs actually work? I reading through ubiquiti forums and it looks like they used to support it, but backed out of it.

My specific usecase is moving around the office while being on google hangouts on my phone.

We've been using the Github flow (or some variation of it) in teams of 2-10 people for a few years now. We work on feature branches, merge after code review using the github web UI. Here's a few things that help us:

- Make a rule that anything that's in master can be deployed by anyone at any time. This will enforce discipline for code review, but also for introducing changes that f.e. require migrations. You'll use feature flags more, split db schema changes into several deployments, make code work with both schema version, etc. All good practices that you'll need anyway when you reach larger scale and run into issues with different versions of code running concurrently during deployments.

- If you're using Github, check out the recently added options for controlling merging. Enable branch protection for master, so that only pull request that are green on CI and have been reviewed can be merged. Enable different dropdown options for the merge button (eg rebase and merge), these are useful for small changes.

- It takes some time to get used to those constraints. Make sure that everyone is on board, and do a regular review of the workflow just as you would review your code. It takes some time to get used to, but I think it's worth it in the long run.