The boring technology behind a one-person Internet company (2018)

Post by NohatCoder » Tue, Sep 17, 2019, 3:45 PM UTC

simion314 wrote: post #384

em-bee wrote: post #370

Earlier quoted context omitted.

how is that any different from a custom rails server with dozens of gems that need to be upgraded. how do you build a site without any of these risks and make it last for a decade or more?

As the other mentioned there are other devlopment stasks that are stable, to give more examples but not for Web, you can get ther code for an old .Net,Java,Qt application, download the SDK used for that version and just build it. There are not 100+ things you need, the SDK contains the compilers, a huge standard library other build tools. If the project had other dependencies those are some standalone .dll or .jar fi…

Post by NohatCoder » Tue, Sep 17, 2019, 3:52 PM UTC

jeremija wrote: post #356

Volrath89 wrote: post #333

Earlier quoted context omitted.

Completely 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

I've started to use TypeScript and React on the front end, with a JSON RPC middleware on an express server with helpers that automatically implement service interfaces for API calls, action creators and reducer handlers. And all of them are type-safe. I've spent a lot of time building CRUD APIs and GraphQL interfaces, and this is the simplest solution that has saved me so much development time. JSON RPC gets so much…

Post by whalesalad » Tue, Sep 17, 2019, 4:07 PM UTC

NohatCoder wrote: post #390

whalesalad wrote: post #273

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 architectur…

I 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.

Post by ficklepickle » Tue, Sep 17, 2019, 4:16 PM UTC

strken wrote: post #385

motogpjimbo wrote: post #380

Earlier quoted context omitted.

By choosing a language with a large standard library and then relying on that library rather than on frameworks of the day as much as possible. For example, many vanilla PHP applications written 10 years ago will still run just fine today, whereas upgrading from one version of Laravel to the next version can be a major trauma.

From what I remember of php applications written around 2009, a lot of them had SQL injection and bizarre roll-your-own-security vulnerabilities. There were some pretty appalling things like the same (wrong) CSRF token validation code being copy-pasted into fifty different files, or passwords saved in plaintext, or customer credit card info sent over email, or every single site being mashed into joomla and drupal no…

Post by ficklepickle » Tue, Sep 17, 2019, 4:22 PM UTC

whalesalad wrote: post #396

NohatCoder wrote: post #390

Earlier quoted context omitted.

I 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.

Nothing 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.