10 ms·
Technology is usually just a means to an end. Unless IP is what you are selling, boring is great. I’ve seen SO many teams burn SO much energy on complicated sta
by whalesalad 7y ago
Technology is usually just a means to an end. Unless IP is what you are selling, boring is great. I’ve seen SO many teams burn SO much energy on complicated stacks just to drink kool-aid. It’s mind bogglingly frustrating, especially as a contractor. At the end of the day it’s great for me: I get brought into shit shows to clean up the mess. But deep down, I want projects to succeed and clean/sound systems architecture is how you do that. Doesn’t matter if it’s PHP, Python or Java.
It hurts to see people continue to make mistakes over and over, so I’m working on a new website and series of engineering posts to help share my approach to a lot of these problems.
Any product I start building usually begins in Rails. React is great. Vue is great. It’s not necessary, good ol’ request/response is just fine. You don’t need a service mesh. You don’t need Kafka. You add that stuff later when it’s required... if it’s required. Rails can’t be beat for startups. I wouldn’t waste any time on a single page app, it’s a completely pointless endeavor unless you have proven traction, users, revenue etc... and can afford to do it correctly.
- theonething 7y agoMy first thought was "I wish the startup I'm working for would read this". My second, "eh, wouldn't change anything." > so I’m working on a new website and series of engineering posts to help share my approach to a lot of these problems. Do you have a mailing list or something to get on to get updated on this?
- whalesalad 7y agoI will hunt down this comment and reply to you in your profile once it’s out!
- mattbillenstein 7y agoIf you do write something up, I'd like to read it - solid analysis re systems architecture et al.
- whalesalad 7y agoGot your email in my notes. Will shoot you a message once I have something out.
- kabacha 7y agoWhy is HN so against people who _enjoy_ engineering? Why should I run some run-of-the-mill stack that has enourgmous legacy cruft and just not "fun". Not every business wants to be sillicon-valley optimized money farm - some people want to do some enjoyable work.
- corndoge 7y agoThat's fine, but that's not engineering. Bridge designers do not try to build bridges out of materials discovered in the laboratory last month.
- PeterStuer 7y agoResearch engineers do. GP said he is not aiming to build a profitable above all else company. Maximizing fun in a hobby seems legit.
- johannes1234321 7y agoFor a hobby and for learning it is absolutely fine. The critique is on businesses running that way fmeither since some developers want to drink the cool-aid on the job or since the company wants to be "attractive" riding the hype train. (How else could they attract the best developers? ;) )
- bsder 7y agoExactly. Look at Eiffel's Folly, for example.
- saiya-jin 7y ago... and bridge designers don't design 'to have fun', but to have structurally sound, cheap and reliable infrastructure tool to cross rivers. Or imagine hiring a construction company for your dream house, realizing only after all is built that they were experimenting and 'having fun' with new unproven materials, construction, wiring etc. OP's approach is mighty fine for his own endeavors, but if I had such a worker hired, there would be a serious talk about priorities. If no agreement is found even 100x engineer would be let go.
- chopete 7y ago>> It hurts to see people continue to make mistakes over and over, Its because https://vimeo.com/76499047 https://vimeo.com/76499047
- chrischattin 7y agoYes! So much this. Every startup I've worked with regretted choosing a trendy tech stack early on. Speed of development is BY FAR the most important thing and the SPA/Javascript framework de jour trend of the past few years is an antithetical to rapid iteration. As a consultant, I'll happily bill hours to untangle that mess, but it's very frustrating to see startups with lots of potential spinning their wheels with unnecessary bloat on the front end.
- stupidcar 7y agoTotally disagree re. SPA frameworks. Having mastered one of the popular ones, I've found I can now turn out fairly complex apps that I never could have contemplated building solo a few years ago.
- Volrath89 7y agoCompletely agree. My default stack is now react + an api in the backend. The way you can reuse components is a great time saver (even for simple apps). I also like redux-thunk to separate all my API calls from the components. Makes everything very lean and readable. I feel way more productive today than in the old jQuery, knockout messes
- r_singh 7y agoSame here! What's your choice of stack for the api? PS - I need to build an api for an app with a React front-end. My choice of language is Python (because I'm super familiar and because of the great ORMs Python has).
- orhanhh 7y agoDjango-rest-framework is super productive once you learn it. It has a bit of a learning curve, but it’s worth it if you are writing a lot of APIs, especially if you’re doing a lot of CRUD. It’s my go to tool when I need to get stuff done. Combined with react and typescript, developing full stack is really smooth.
- dx034 7y agoThe only problem I see with rails is that it's hard to find devs these days (at least in Europe). Even if they could learn Rails for that project, many I've spoken to wouldn't want to take a job where Rails is required. I just witnessed a project switching from rails to React (for the frontend) because they just couldn't get enough good people willing to use Rails.
- strzibny 7y agoI heard this before, but when we tried to find a React dev for the front-end part we couldn't find any either. There are more JS devs for sure, but you also compete with literally everybody for talent.
- zhdc1 7y agoI kind of get the impression that there is a glut of developers who know/are learning React and a glut of companies that are having trouble finding someone willing or able to use React (at least where I'm located).
- tomclive 7y agoThat's interesting. This year, for the first time, I've been working with Rails. It wasn't my choice but I've really enjoyed it. A lot just makes sense and it's been so quick to get things from idea to code.
- dx034 7y agoI don't think devs hesitate because Rails (or Ruby in general) isn't good, they hesitate because they hope to gain more relevant experience by working with JS frameworks. But again, that's just my experience, it may differ for other companies and/or regions.
- Bombthecat 7y agoRails isn't enough enterprisey (in my opinion..) no firm ever considers rails.. (note, I love rails!)
- qaq 7y agoI think Phoenix LiveView is offering a very compelling value here. You are basically writing a regular server side app that will perform on par with SPA for most use cases.
- UserIsUnused 7y agoI would go with spring boot. Sure rails is a faster start, but when it grows it becomes a mess. Spring boot gives you the fastest start in JVM-land, and if your product is successful and you need things to scale, or features are getting complex, you still have the spring framework in the insides that you can manage. Boot is almost just defaults. But spring boot wouldn't exist, if rails didn't change the landscape of web development.
- NohatCoder 7y agoI wonder what is wrong with single page apps? As I see it you can largely write the same code, you just have the additional option of modifying the page on the fly.
- whalesalad 7y agoNothing wrong with it if you know what you’re doing and have a strong API to power it. Most people don’t know what they’re doing and end up with a duct taped ball or spaghetti. This tendency is compounded when you’re in a hurry to get shit done.
- ficklepickle 7y agoNothing better than having to maintain 1000 line components. I wouldn't know, but I have dumped them on other people. It made sense to me when I frantically wrote it, how bad could it be? /s
- NohatCoder 7y agoBut is the server side method less spaghetti-prone? I'm inclined to believe that you just believe that because it is the way you are used to programming. A beginner will write spaghetti no matter the job, no matter the tools, no matter the method.
- theonething 7y agoNothing "wrong" with them per se, but in terms of system complexity, you're basically doubling it by having application state and logic on both the backend and frontend. When I work on a big SPA, I feel like I'm working on two applications and have to worry about syncing state and logic together.
- brillout 7y agoWhat is it that Rails has that Node.js doesn't? Node.js is missing a great ORM but other than that I don't see many things missing in Node.js anymore. There is also Rails' admin panel but most projects don't need that.
- whalesalad 7y agoI’m not sure if you’re familiar with what Rails really is. It doesn’t have an admin panel. Node is a language that you could compare to Ruby. You can ostensibly do the exact same thing with Node that you could do with Ruby on Rails... but you’d be reinventing the wheel all over the place and duct taping lots of different modules together that all utilize different design patterns. If you’re good at designing systems, you can do it just fine, albeit slower than I could with Rails. But it’s possible. I have nothing against Node but there’s a time and a place for all tools. Getting an MVP up is not one of them, imho.
- tim333 7y agoCheck the top comments here https://news.ycombinator.com/item?id=20920555 https://news.ycombinator.com/item?id=20920555
- rpedela 7y agoI agree with your overall point, however I disagree with the "just pick Rails and don't do SPA" part. For startups or any small team, the right approach is whatever boring technologies the team is comfortable with. If that is Rails, great! I personally don't know it so that would be a horrible choice for me. Likewise SPAs are comfortable and easy for me (aka boring), but a bad choice for someone else who isn't comfortable with them.
- phlakaton 7y agoHowever, the post indicates React + Redux for the front-end. Perhaps it's my bias as a back-end curmudgeon, but those strike me as _unboring_ choices in the front end, particularly if you're not targeting SPAs. My point being: one person's "boring" could be another person's anything from "clunky and archaic" to "faddy" to "efficient and sensible." Not even Rails, built upon Ruby's idiosyncratic blood magick, is an entirely uncontroversial choice.
- lubonay 7y agoSo, boredom is in the eye of the beholder?