HN user
DIDs are rooted in ECDSA keys (secp256k1). Each user identity is a non-PQ cryptographic commitment. These ecosystems must start migrating very soon because if CRQCs arrive before they're done, they face a choice between user compromise and bricking accounts.
I'm hesitant to build anything load-bearing on AT Protocol given its PQ exposure: https://words.filippo.io/crqc-timeline/
I've been writing notes on Heroku alternatives (mostly Fly, Railway, Render) at https://croaky-webstack.deno.dev/ Maybe something useful in there for others.
+1 Netlify.
I've really liked it for https://blog.statusok.com and https://statusok.com
GitHub webhook deploy flow, one-click SSL, 301 redirects and other rewrite support, CDN seems pretty good.
My favorite growth resources are Brian's essays at http://www.coelevate.com/
I love Trello and have built a few things on their API but have to agree the API docs are painful, hard to navigate.
Also, what's up, homie? Hope you're well.
Sorry about that! Working on the ILIKE fix at https://github.com/thoughtbot/administrate/pull/166
Here's an RSS feed: https://github.com/thoughtbot/til/commits/master.atom
If you're a Rails developer, you probably have a config/initializers/backtrace_silencers.rb file in your app. Think of James the next time you see that file. He wrote the initial implementation:
http://jamesgolick.com/2007/12/1/noisy-backtraces-got-you-do...
DHH later ported the work to Rails:
https://github.com/rails/rails/commit/f42c77f927eb49b00e84d3...
I knew James mostly online and a little in person from various programming conferences. He was smart, funny, and kind. He made a difference. He will be missed.
Awesome! I'm a huge fan of Segment: http://playbook.thoughtbot.com/#instrumentation
We're using this code-level approach in basically every one of our Rails apps these days: http://robots.thoughtbot.com/segment-io-and-ruby
Most common integrations: Intercom, Mixpanel, HubSpot, AdWords, Twitter Ads, Google Analytics.
Good interview with Peter (Segment founder) from February this year: http://podcasts.thoughtbot.com/giantrobots/86
https://github.com/thoughtbot/laptop will install Homebrew, Tmux, Silver Searcher, Postgres, Redis, a few programming languages, and other items.
https://github.com/thoughtbot/dotfiles sets up a bunch of slick aliases and plugins for Vim and ZSH to make development productive.
Rubocop is great! Hound is built on top of it.
We've tried putting style violations in the build and found there are enough edge cases that it isn't exactly the interaction we've wanted. Sometimes, we want the human to say "no, my pair and I broke the guideline on purpose and we're okay with it in this case." We don't want a broken build in those cases.
Totally agree with you about getting feedback earlier than opening a PR, though. Linters integrated into text editors are a great way to go.
You can tune Hound (and Rubocop) to your liking:
https://houndci.com/configuration
the change is a false positive
I've been using Hound on about a dozen projects the last few months and haven't seen false positives. We built it atop Rubocop, which has been pretty well-vetted.
Software development has too many unwritten rules and social interactions for a bot
We've limited our guidelines to a subset that should almost always be "no argument, my bad, fixed in [SHA hash]." However, it comments instead of failing the build or mechanically changing the code because that the human should make the final decision about whether to make the change.
+1 I've been using it on a number of Rails apps. Really helps reduce the time spent in TDD cycles and stay focused.
Hello :)
I help maintain the http://github.com/thoughtbot/laptop script that Giles mentioned. Happy to take feedback in Github Issues.
Some other good ones:
Ah, didn't think of that. Valid critique. Edited the headline.
Very cool.
I've been in a Campfire room with the new maintainers for a few days. We've been coordinating the transition for a couple of weeks. Looking forward to knocking out a few more features and bugs in the next few days while they get used to the codebase.
Everyone's busy so we'll see how much time is needed and able to be spent by the new maintainers but we're happy to have found almost a dozen developers to lead maintenance across the two companies (Crowdtap and Iora Health) and we took the time to express a process and way of doing things to help make the project more efficient:
Hahaha. Yes, I was joking. Sorry about that, apparently not funny! :)
More on the acquisition from the thoughtbot blog: http://robots.thoughtbot.com/post/17212734809/airbrake-acqui...
More info on the acquisition from the thoughtbot blog: http://robots.thoughtbot.com/post/17212734809/airbrake-acqui...
thoughtbot runs a similar program and we do offer visas:
Prem Sichanugrist was a former apprentice of ours. He's from Thailand and is now a full-time thoughtbot employee.
Please apply if it interests you!
I've been thinking a lot about internships versus apprenticeship:
http://robots.thoughtbot.com/post/14216183124/internship-or-...
I'd say Hungry Academy is definitely an apprenticeship.
Haha, as the author of that commit, I'm embarrassed to see it here. Maybe it's a story, though.
I heard about Heroku Bartender from http://devopsweekly.com
It pushed me to finally use a Linode slice for which I had a $60 credit from http://appsumo.com and play with Ubuntu, which is outside my typical skill set.
I had fun installing Ruby, git, Postgres, and https://github.com/defunkt/cijoe on that slice. While stuff was installing, I added the favicon to Heroku Bartender.
There's a lot of cool software and tools out there. Open source, DevOps Weekly, etc are awesome for learning and playing.
We worked hard to make sure it wasn't making lots of HTTP requests. The way the client library works is it runs a background polling thread and syncs to the Copycopter service every 300 seconds (this number is configurable), caching all the edited copy locally in the Rails app.
Full-screen shell & text editor.
Definitely. Fridays after work (6pmish) at The Field in Central Square?
If your app only provides Facebook for authentication, do some Jakob Nielsen-style usability testing and you might be surprised how common this complaint is. That's been my experience on the most recent app I've worked on.
Startups love Facebook authentication more than users do.
What's up with their contributor agreement?
https://spreadsheets.google.com/a/joindiaspora.com/viewform?...
That seems pretty wacky. The patent section in particular seems random and unrelated.