Choose Boring Technology (2015) • Hacker News Board

Re: Choose Boring Technology (2015)

#371

Post by collyw » Thu, Feb 25, 2021, 4:58 PM UTC

bitwize wrote: post #168

NomDePlum wrote: post #146

Earlier quoted context omitted.

Lots of good reasons to use NoSQL. All pretty much hang off what sort of data access pattern you need. If you have an application that retrieves an works on a top level entity then NoSQL fits very nicely. When you have a dataset that is shared and aggregate information is needed not so much and you are likely better of considering a SQL database of some sort.

> When you have a dataset that is shared and aggregate information is needed not so much and you are likely better of considering a SQL database of some sort. There are best practices for this. Simply create a microservice per table, and then create a microservice that acts as a client to the other services and aggregates or joins the data from those services. No, I'm not kidding. This is literally what people do and…

I bet these people are running on a single server.

Re: Choose Boring Technology (2015)

#372

Post by jjeaff » Fri, Feb 26, 2021, 10:24 PM UTC

reasonabl_human wrote: post #358

jjeaff wrote: post #347

Earlier quoted context omitted.

He was an ex-googler, so I'm sure only some combination of c, go, and java would have sufficed. Php 7.2+ is great for a lot of saas products and is super fast now. and mysql 8 is rock solid and battle tested in a lot of production systems. Starting over, I would consider PostgreSQL because it has some nifty features. But now that mysql has added json support, I am less inclined and I see a lot of complaints about per…

We use a document based DB to run a massive azure SaaS service offering and it gets the job done quite well, why the hate for non-relational?

Definitely has it's place. I use redis for caching and queues. And elastic search for document search.

But I assume you have a relational database somewhere to manage users and do other relational-type things?

Re: Choose Boring Technology (2015)

#373

Post by danjac » Mon, Mar 01, 2021, 1:05 PM UTC

tluyben2 wrote: post #249

Nextgrid wrote: post #63

Earlier quoted context omitted.

In the case of a lot of tech companies, the entire market is broken and leads to weird incentives rarely seen in any other industry: companies that aren’t profitable, don’t have a real product people pay for, don’t have a clear, plausible path to profitability and yet somehow stay in business because investors are happy to burn money. This completely reverses the typical market dynamics. The company is more focused o…

I often wonder why investors love paying 5 figure aws bills; even worse, why they consider lower bills or not using 'the cloud' a sign of cto incompetence. Even if the company can run on $500 hosting instead. Must be because it is easy to do DD on: AWS, check, TS (JS is now a reason to not pass VC dd I heard from friends) check , React check, microservices, check, etc.

I wonder if this isn't so much about the tech itself, but rather the expectation that the best realistic outcome for a startup is an aquihire. Following the current "industry best practice", even if it's more expensive and might not even make sense for your product requirements, is just insurance that your acquisition will pass a future tech compliance audit: a buyer will want to be able to support your product and cannibalize it if necessary and that's harder to do if it's written in a lesser-known language/framework.

This also goes some way to explain the leetcode, "hiring only the best from Stanford/MIT" hiring nonsense for pretty mediocre cookie-cutter products that could be perfectly well executed by couple mid-range developers: your developers' resumes are as much a part of any potential acquihire package as the codebase and user data.

Re: Choose Boring Technology (2015)

#374

Post by zingar » Mon, Mar 08, 2021, 9:26 AM UTC

ZephyrBlu wrote: post #346

zingar wrote: post #316

Earlier quoted context omitted.

My current employers hire +- 1/100 applicants. The vast majority fall off before even getting to a coding test. Of the last 20, most are not fluent with conditional logic and iteration, or cannot use a dictionary in an algorithm. In the most recent interview, an "experienced" React developer could not set properties on a JS object.

Why do you think this occurs? It doesn't make sense that people apply for a programming job without being able to do any programming...

I think it's because they have some success with making wordpress do what they want (after a fashion), or copy and paste some Javscript. That makes them a programmer, without knowing what they don't know, even 10 years later.