HN user

Rygu

814 karma
Posts19
Comments177
View on HN
bearcave.com 4y ago

The D Language: A Successor to C++ (2012)

Rygu
2pts0
news.ycombinator.com 4y ago

Ask HN: What are you doing about climate change?

Rygu
4pts2
twitter.com 5y ago

“You should find a business-type / CEO”

Rygu
2pts1
blog.messagebird.com 5y ago

MessageBird (YC S16) announces an indefinite “Work Anywhere” policy

Rygu
3pts0
www.mollie.com 7y ago

Mollie raises €25M in Series A funding round to accelerate international growth

Rygu
8pts0
tether.to 8y ago

Tether (USDT) Account Snapshot Statement [pdf]

Rygu
63pts59
twitter.com 8y ago

How I explain Product Management to friends and family

Rygu
1pts0
getcaptain.co 9y ago

Show HN: Captain, a Docker menu bar app for Mac

Rygu
2pts2
stripe.com 9y ago

Stripe launches new European payment methods

Rygu
37pts22
www.youtube.com 9y ago

On the Spectrum of Abstraction

Rygu
1pts0
9to5mac.com 9y ago

Apple loses $22.1M case against patent firm Acacia

Rygu
3pts0
mta.openssl.org 10y ago

Forthcoming OpenSSL release announced

Rygu
77pts19
gist.github.com 10y ago

Extreme Go-Horse Process

Rygu
1pts0
www.dutchnews.nl 11y ago

Uber office in Amsterdam raided by local authorities

Rygu
7pts1
www.mollie.com 11y ago

Mollie: accept payments online (European Stripe)

Rygu
1pts0
dl.dropboxusercontent.com 12y ago

Dutch payment provider Mollie has integrated Bitcoin payment method

Rygu
1pts0
www.openwall.com 12y ago

CVE-2014-0130 Rails vulnerability exposes arbitrary files on server

Rygu
1pts0
techcrunch.com 14y ago

Rockstar (Apple, Microsoft, Sony and RIM) are itching to license their patents

Rygu
1pts0
www.ip-rockstar.com 14y ago

Rockstar Consortium receives green light from Department of Justice

Rygu
1pts0

Wow that's on-point, agree that in many past projects "inertia to larger changes" is exactly how I would describe so-called Clean Code.

It's that small changes like adding getters and setters give an easy-to-follow PR, a false sense of accomplishment for both the author and the reviewer, and ton of dopamine with that. While important changes, that actually deliver business value or repay technical debt, become increasingly difficult to do without replacing massive amounts of code and redoing the file structure.

Inertia is the biggest demotivator.

Yes that's the theory, yet currently any company with sufficient capital or geopolitical advantage can be an effective market leader, while at the same time operating inefficiently at a loss.

Retool positions itself as a tool for technical folks, and you’ll need to be comfortable with basic SQL and Javascript to get the most out of it.

An interesting reminder that PMs aren’t always in the driver’s seat. In fact, sometimes they’re not even in the car .

If you're building a technical tool for technical folks then you probably don't need product managers, until late game anyways. Though you'll probably already have a few product engineers and product designers, who fill in that role.

React v15.5.0 9 years ago

Although I don't agree with the overall sentiment of your message, I do understand your situation as a professional. In fact I believe by far the largest (less vocal) group of React users only use it at work, and never wilfully agreed to spend their spare time on GitHub because of FOMO, or fear of dependency upgrades (FODU).

And I believe there should be a better way to prepare your users for a major version upgrade (React 15 -> 16) than to update the current branch with all kinds of deprecation warnings. Even if a library - as popular as React - doesn't plan to provide lifetime support for any major because they like to to move fast, I understand that, it's simply not okay to ruin older branches this way, madly assuming everyone is surely going to upgrade to React 16 in the immediate future.

Ideally, I'd imagine there could be a separate optional package that adds these warnings dynamically. If that's not possible technically, then an optional build flag would be nice. Or two separate releases: react-15.5.0 and react-15.5.0-upgrade-support. Even better: go back to semver, and treat major upgrades as optional for the first 6 months. This allows other libraries like routers and style libs to catch up, so app devs can upgrade even more smoothly.

Maybe after all, DX is about when to provide helpful errors and warnings. And when not to?

It's always great to explore application connectivity for the next generation. Webhooks have done a lot for the web, but the lack of standardization is starting to show.

However external deployment of code somehow doesn't feel like an improvement to me. From a DevOps perspective having webtask code run on a closed third party environment is a big risk. It makes continuous integration, testing and error reporting more difficult or even impossible if the webtask service isn't well thought-out.

The way forward for webhooks in my opinion should be standardization of push and pull protocols, with concerns like cryptographic signatures, metadata headers, and failure recovery through event sourcing.

Google+ Redesigned 10 years ago

The goo.gl short URLs in (parentheses) are really annoying. They totally hide the content behind the links.

Creative processes actually CAN be well-organized and fun at the same time. Just look at hackathons, which teams get stuck halfway and which teams are productive and take the prize home?

If you only care about code and learning new APIs, that's your right. (I'd say do it at home.) If you want to ship something real with 20% company time? Get your project organized.

Amazon Prime Photos 11 years ago

Has anyone successfully backed up iPhone Live Photos on a photo storage service that's not iCloud?