Subhas

medium.com/@rdsubhas · Personal blog · on HN since 2014

Subhas writes Medium posts on software engineering practice, covering Docker, Ruby in production, REST URLs, and JavaScript.

What HN saysHN links it for REST URL advice, which one commenter calls spot on, and for posts on over-engineering and Docker.
22HN people shared it
2linked it in comments
31stories submitted
727story points
2 years agolast shared
2014people per year2026

Most-shared posts

  1. 1
    Modern Software Over-Engineering Mistakes
    17 people · 675 points · first shared 2016 · 133 comments on HN
  2. 2
    Docker for Development: Common Problems and Solutions
    2 people · 6 points · first shared 2015 · discussion on HN
  3. 3
    Ruby in Production: Lessons Learned
    2 people · 5 points · first shared 2015 · discussion on HN
  4. 4
  5. 5
    Mad Max's take on Tech Evangelism
    1 people · 4 points · first shared 2015 · discussion on HN
  6. 6
    ES6: From Callbacks to promises to generators
    1 people · 3 points · first shared 2015 · discussion on HN
  7. 7
  8. 8
    PITIful RESTful URLs
    1 people · 3 points · first shared 2014 · discussion on HN
  9. 9
  10. 10
    Online Services: Fix your damn emails
    1 people · 1 points · first shared 2015 · discussion on HN
  11. 11
    A Better Android Release Pipeline
    1 people · 1 points · first shared 2015 · discussion on HN
  12. 12
    REST in Peace: Monolith vs MicroServices in Examples
    1 people · 1 points · first shared 2016 · discussion on HN

What HN people wrote when they linked it

rdsubhas · 2017-06-18
Spot on. RESTful URLs are not to be treated like SEO URLs. But unfortunately most people don't see the difference. One example in the article is especially harmful (/students/<id>/courses/physics for querying). The single best slideshare I've found on REST is Teach a Dog to REST. Old but gold. https://www.slideshare.net/landlessness/teach-a-dog-to-rest (And a shameful plug - https://medium.com/@rdsubhas/pitiful-restful-urls-5d576ffccb98)
allan_s · 2019-03-18
I would like to point out a possible problem with the generic advice "read books" "follow blogs etc." => technological bias As you are from Node/Express and Mongodb background the biggest risk is trying to become only better in these technologies. So you will only know how to make faster horses, how to train them for the best, but you will never learn car exists. More than best practices, what makes a great developer valuable (especially in a position like you where other people in your company are less experienced than you) is your ability to see wider not deeper. Try to challenge the status quo ? Why MongoDB? What kind of alternative do you have ? Same for Node + Express. Doing so will force you to see where your tool shine and where it reach its limit. Doing so will permit you to know when you need to dig deeper on "how to use better this tool", and when to step back and "wait a minute, no amount of best-practices/knowledge will balance the fact that MongoDB is just no the right tool here" So read a lot, but also from people that are not from your community (and to be honest HN is a good starter on getting different point of view) The other important things is about perspective, it's not because a googler/guy from netflix wrote about how they needed to split the code in microservices, or needed to implement $design-pattern-with-a-very-cool-name that it does apply to you. Especially looking to the size of your dev team, I think the worst things that could happen to…

Keyboard shortcuts

/Search
j kNext / previous blog
EnterOpen selected blog
vVisit the blog site
fFollow / unfollow
lSwitch grid / list view
dSwitch dark mode
g hHome
g pTop posts
g tTopics
g fFollowing
g lLiked
g yHistory
g qFAQ
EscBack / close