Email or username:

Password:

Forgot your password?
The Seven Voyages Of Steve

I’ve worked in the technology sector for 30 years and can confidently say that the right amount of technology to use to solve any problem is the absolute minimum you can possibly get away with while still being useful.

Dumb is better than smart. Simple is better than complex. Small is better than large.

Vendors will say the exact opposite because it allows them to sell you more stuff. And you definitely don’t want that (see above)

8 comments
Cornelius

@sinbad 25 years for me and same. Elegant simplicity are my watch words.

Martin Christopher

@sinbad But complex can fit so many more technically correct but meaningless buzzwords to dazzle clueless customers and investors!

CohenTheBlue

@sinbad 1/2 This is mostly why I build stuff I use myself. Wood, clay, straw and sand are incredibly flexible and most importantly, harmless and reusable materials.

CohenTheBlue

@sinbad 2/2 Having tried using expanded polystyrene, that contaminates everything around it. Wherever rodents can get to it it's spread widely, even under ground. Rodents WILL eventually get to everything. Touching a board of polystyrene while working with it breaks off chunks.

Better to build good drainage, wide roof overhangs and isolate the foundation with sand. Probably costs much less and no worry about spreading microplastics at your home.

Plastics are designed to fail and contaminate.

Sören Meyer-Eppler

@sinbad nah man. Sort your array of integers using an LLM!

Ric

@sinbad I have this argument with other developers all the time.

Standard practice seems to be that if something is maxing a server out, you just throw more hardware at it and carry on. I hate that! It's so wasteful both in terms of tech and money, and just a lazy solution.

I prefer to optimise code to perform better, so that it can execute x times more in the same timeframe or use less memory etc. Decrease the server load, don't just throw more money at the server.

Should be the norm!

The Seven Voyages Of Steve

@dev_ric The ethos for years has been that "dev time is expensive, hardware is cheap" and as a result we have a ton of vastly over-engineered frameworks that make devs feel clever while requiring stupid amounts of CPU and RAM in proportion to what they actually do, and not really saving dev time in the end because of all the unnecessary complexity

Go Up