Steve Klabnik

There's many examples of exactly what you're asking for, such as Kenton Varda's Cloudlfare oauth provider [1] and Simon Willison's tools [2]. I see a new blog post like this with detailed explanations of what they did pretty frequently, like Steve Klabnik's recent post [3], which while it isn't as detailed has a lot of very concrete facts. There's even more blog posts from prominent devs like antirez who talk about other things they're doing with AI like rubber ducking [4], if you're curious about how some people who say "I used Sonnet last week and it was great" are working, because not everyone uses it to write code - I personally don't because I care a lot about code style.

[1]: https://github.com/cloudflare/workers-oauth-provider/

[2]: https://tools.simonwillison.net/

[3]: https://steveklabnik.com/writing/a-tale-of-two-claudes/

[4]: https://antirez.com/news/153

I am sure Steve would say this as well (because he has said it many times). Start by improving the documentation of helping to regress bugs. These two items while seemingly inconsequential are actually a huge help to the core team and all developers who actually use rails (especially awesome documentation).

Once you get a certain level of familiarity with the way Rails is built, find a small bug and follow the contribution guidelines.

There is no magic :) Take small steps and continue to make any contribution you can. Ask a ton fo questions and work through issues, you'll get there.

Here's a blog post that Steve actually wrote about contributions:

http://blog.steveklabnik.com/posts/2012-07-05-how-can-i-contribute-to-ruby-on-rails-

Congrats as well Steve! You should be really proud of this release with the rest of the core team.

What's the security posture of actix-web these days? The impression I got from the temporary deletion of the repo and maintainer switch about six months ago[1] was that actix-web was sort of a research platform rather than a production-ready server. It prioritized performance and ease of development in order to try (successful!) ideas the author had for writing really fast servers, and therefore made uses of unsafe code that many Rust developers thought unsuitable for production.

I don't mean to start drama -- I just feel like if the project is still prioritizing speed and experimentation over safety, that's worth including in comparisons like this, and if it's not anymore (or if I misunderstood the story in the first place), that would be good to know too.

[1] https://steveklabnik.com/writing/a-sad-day-for-rust

Look, I'm not a REST cheerleader by any stretch of the imagination but in REST terms the OP just doesn't know his ass from his elbow here. Consider:

> POST /orders/42/pay

> POST /orders/42/ship

You don't put verbs in your URLs. This is really REST 101. I highly recommend Nobody understands REST or HTTP [1]. The above is exactly why you don't put verbs in URLs. Consider instead:

POST /payment { orderId=42, etc }

POST /shipment { orderId=42, etc }

is a much sounder RESTful API design.

And in case anyone feels the need to suggest SOAP, I highly recommend the satiricial (but disturbingly accurate) The S stands for Simple [2].

[1]: http://blog.steveklabnik.com/posts/2011-07-03-nobody-understands-rest-or-http

[2]: http://wanderingbarque.com/nonintersecting/2006/11/15/the-s-stands-for-simple/

After reading Steve Klabnik's "Nobody Understands REST or HTTP" ( http://blog.steveklabnik.com/posts/2011-07-03-nobody-understands-rest-or-http ), I thought it would be helpful if honoring the client's Accept: header in GET requests were easier.

Recently I watched Richard Jones' survey of the various Python micro web-frameworks ( http://www.youtube.com/watch?v=AYjPIMe0BhA ), and I was really taken by the design of itty.py.

I thought it would be great to extend their idea of the @get decorator for use with Accept:. It turned out to be merely a ~50 line change! Fun! Kudos to the developer of itty.py for writing code which is hack friendly.

I just hit publish on a post about this! The common guidance is to get started light and to start with the issues. Even the GSoC student at the repo I'm starting to get involved in started by reading as many issues as possible before diving in.

Here are two links to help you:

http://words.steveklabnik.com/how-to-be-an-open-source-gardener - Steve wrote a great post about how he gets started with a new project

http://peteh.me/an-easy-way-to-get-started-with-open-source-in-2017 - Here's my post about how I'm starting to get involved in open source without being great at coding