Nate Berkopec writes about Ruby on Rails performance, scaling, and web speed, plus some self-publishing and career topics.
Commenters cite his posts on Turbolinks, Action Cable, and Rack middleware as useful technical references, and praise the Rails 5 Turbolinks work.
No.
Getting page views for well written and original content (especially tech topics) is not hard, in fact there is a severe dearth of good technical writing. How often you post, how many sharing options you provide should not be what you optimize for. Optimize for writing original, well informed content that shows domain expertise. Such content has no problem attracting an audience. But the problem with writing such content is that it's pretty time consuming.
Let me share my own anecdata. Three of my posts got significant attention when I posted them to my blog, around 30k pageviews and now I get a few thousand views every month from search engines and people sharing my posts on social networks. I don't spend any time promoting it, only post to a couple of subreddits initially, that's it, (and HN where my posts did not gain traction so far) .
Posts :
https://www.ploggingdev.com/2017/01/multiprocessing-and-multithreading-in-python-3/
https://www.ploggingdev.com/2016/12/performance-measurement-in-python-3/
https://www.ploggingdev.com/2016/12/analyzing-programming-language-statistics-of-100000-github-repositories/
Especially the first post linked above has gotten most of the attention and now ranks on Google for python multiprocessing and multithreading related keywords. My blog is clearly not very popular by HN standards, but it has given me a good understanding of what type of content has no issue attracting attention as explained above.
Edit : You might find the…
This is super cool!
I've only recently discovered that Markdown has footnotes, and I've gone to down adding footnotes everywhere.
I use Jekyll + markdown on my website, and I now have lots of fun adding footnotes to my writing.
I added a "footnote tutorial" for readers on https://josh.works/turing-backend-prep-01-intro#why-this-rubybackend-software-engineering-prep-series-exists, to help them learn how to navigate the footnotes.
I _love_ your library, and I love the problem that you're solving with it.
Along the way, I've looked at Gwern's sidenotes[0] and Nate Berkapec's "footnotes"/sidenotes [1].
I eventually want to do something more "in-line", like what you've down with Expounder, but I've been satiated with markdown footnotes for now.
[0]: https://www.gwern.net/Sidenotes#
[1]: https://www.nateberkopec.com/blog/2017/03/10/how-i-made-self-publishing-about-ruby-on-rails.html
I am of two minds.
First, if you want to earn money, choose the stack you know best already. Figuring out how to do business will probably be tricky enough. Talk to your prospects. Maybe start consulting first, and then convert recuring painpoint of your customers to a product. I have seen an advice to write a book/guide before you start with something that requires maintainance and few success stories about that [1] :-)
On the other hand, I often like to create various pet-projects in weird languages. I dabbled in clojure, kotlin, tried Vaadin, typescript, phoenix on elixir, but I see on myself that while learning a new tool can be hard, finishing a project is often harder :-)
Wish you luck!
[1] https://www.nateberkopec.com/blog/2017/03/10/how-i-made-self-publishing-about-ruby-on-rails.html
Whooops responded with old account. If you run `$ env RAILS_ENV=production rake middleware` you'll see that your final app that gets mounted is actually the "routes" of your app.
run CodeTriage::Application.routes
Essentially that RouteSet#call wraps every piece of code you've ever written for your app. I think that newrelic is reporting that is the entry point to your app code which makes sense that it takes the longest amount of time.
For a better view of request break down I would recommend checking out https://github.com/MiniProfiler/rack-mini-profiler. You'll not only see where request time is being spent, you'll see how it "stacks up". The flame graphs are pretty useful check out http://www.nateberkopec.com/2015/08/05/rack-mini-profiler-the-secret-weapon.html for more info.
The new TurboLinks is one of the best things about Rails 5, though. You can basically get UX comparable to an SPA with mostly server code.
As for coffeescript, you can just remove the gem and it'll use regular JS.
https://www.nateberkopec.com/2015/05/27/100-ms-to-glass-with-rails-and-turbolinks.html
For anyone that's interested, here's a guide on scaling Ruby servers to 1000RPM, written by the same author: http://www.nateberkopec.com/2015/07/29/scaling-ruby-apps-to-1000-rpm.html.