So my parents got speakers integrated into their monitor. A few years ago (like 3-4) they made me turn off the sound because it annoyed them since all they did were playing some shitty flash games and some office work. Now they needed the sound back on and this is how it happened.

1. Confirm they plugged the right cable in. I know them so I knew that could be a problem

2. Made them download Teamviewer because I know they can't even doubleclick without guidance

Now the juicy part was to tell them they need to turn on sound on the monitor. As I was watching via teamviewer I saw them trying to click on the menu items from said monitor. Took me 5 minutes to explain that their mouse can't do shit on that because they need to navigate with the buttons underneath the monitor.

Turned out they couldnt get things right and I had no idea what they were seeing because they explanations went like "All I can see is Main Menu and Exit." - "Is that really all dad?" "Yes thats all. Main Menu, Brightness and Exit" turnes out the middle part is interchangable like "Brightness, Saturation, etc..."

After 2 hours I gave up and told them to pick up my speakers tomorrow

Medical device able to track heart rate, oxygen saturation, respiratory rate and more non-invasively.

Still working on it. Starting clinical trials soon. Best side job in the world!

Ladies and gentlemens, my everyday workstation.. at work.

i5-5300 2,30Ghz, 8gb ram and 128ssd. Bloated external screen with low resolution and even lower colour saturation.

Running VM, handling big as images, editing and a tiny bit coding.. and they wonder why I'm asking for a new setup..

(._.) ( l: ) ( .-. ) ( :l ) (._.)

Cheers ☕

Is your code green?

I've been thinking a lot about this for the past year. There was recently an article on this on slashdot.

I like optimising things to a reasonable degree and avoid bloat. What are some signs of code that isn't green?

* Use of technology that says its fast without real expert review and measurement. Lots of tech out their claims to be fast but actually isn't or is doing so by saturation resources while being inefficient.
* It uses caching. Many might find that counter intuitive. In technology it is surprisingly common to see people scale or cache rather than directly fixing the thing that's watt expensive which is compounded when the cache has weak coverage.
* It uses scaling. Originally scaling was a last resort. The reason is simple, it introduces excessive complexity. Today it's common to see people scale things rather than make them efficient. You end up needing ten instances when a bit of skill could bring you down to one which could scale as well but likely wont need to.
* It uses a non-trivial framework. Frameworks are rarely fast. Most will fall in the range of ten to a thousand times slower in terms of CPU usage. Memory bloat may also force the need for more instances. Frameworks written on already slow high level languages may be especially bad.
* Lacks optimisations for obvious bottlenecks.
* It runs slowly.
* It lacks even basic resource usage measurement.

Unfortunately smells are not enough on their own but are a start. Real measurement and expert review is always the only way to get an idea of if your code is reasonably green.

I find it not uncommon to see things require tens to hundreds to thousands of resources than needed if not more.

In terms of cycles that can be the difference between needing a single core and a thousand cores.

This is common in the industry but it's not because people didn't write everything in assembly. It's usually leaning toward the extreme opposite.

Optimisations are often easy and don't require writing code in binary. In fact the resulting code is often simpler. Excess complexity and inefficient code tend to go hand in hand. Sometimes a code cleaning service is all you need to enhance your green.

I once rewrote a data parsing library that had to parse a hundred MB and was a performance hotspot into C from an interpreted language. I measured it and the results were good. It had been optimised as much as possible in the interpreted version but way still 50 times faster minimum in C.

I recently stumbled upon someone's attempt to do the same and I was able to optimise the interpreted version in five minutes to be twice as fast as the C++ version.

I see opportunity to optimise everywhere in software. A billion KG CO2 could be saved easy if a few green code shops popped up. It's also often a net win. Faster software, lower costs, lower management burden... I'm thinking of starting a consultancy.

The problem is after witnessing the likes of Greta Thunberg then if that's what the next generation has in store then as far as I'm concerned the world can fucking burn and her generation along with it.

It is the year 2451 ad and mankind rules the galaxy with a lazy iron fist. There are roughly 14,000 civilizations, comprised of just over
17,000 intelligent species on a quarter of a million earth-like
worlds. And all of them call themselves 'the galactic empire'.
No one told them that twenty planets doesn't qualify them for the title "galactic."

Well, we could rule, if we wanted to. Most of its just backwaters that no one wants anyway. It turned out that the reason no one invaded earth before was because they were too busy fighting themselves. Stupidity it appears, is not a unique human quality.That and the sex robots. Theres more of them in the galaxy than actual meatbags. Many species had taken to artificial wombs and 'vatbabies', which is exactly what they are called. Those poor bastards will carry that label for life.

We never did break light speed, but most of the rich exist in hypersleep anyway. Most of them only wake up once a year or so. There are some that only creek out of bed to check their stock portfolio. I hear there is even one trillionaire thats up and about once a century to ask if we have broken light speed yet.

Despite all the progress over the last 400 years, historians all agree about the most significant event in modern history.
The lobster went extinct two hundred years ago on earth.
Theres been riots ever since.

* * *

In other news I'm still working on the game I guess. It's like totally the most okay indie game you'll ever play--if I ever finish it.

I put about a year of work into the NPC system, and then chatGPT came out.

After everything thats happened, at this point I may just make a game about an indie dev making a survival game, being stuck in the actual apocalypse or some weird political dysopia.

Put it on rewind, it was originally a zombie game. But at the time the market got flooded and steam sales for zombie games cratered. So I pivoted to something more along the lines of fallout. Then the flash market crashed, bunch of publishers folded, and adobe stopped support for flash (probably for the best). Then newgrounds, which I was gonna launch on for promotion (because actual marketing is expensive), ended support for flash.
Was going the route of kickstarter, and that year the KS market got flooded and the bar rose almost over night so you needed super high production quality out the gate, and a network of support you already built for months.

We had a brief nuclear war scare, and I watched the articles come out about market saturation for post-apocalypse games, so I pivoted back to zombies. Then covid happened and the entire topic was really fucked. So I went back to fallout meets rimworld. Then we had a flood of games doing that exact premise pretty much out of the fucking blue, so I went for a more single-survivor type game. Then ukraine happened and the threat of nuclear war has been slowly sapping the genre of its steam, on well, steam.
Then I was told to get a cancer screening which I can't afford. Then I broke a tooth and spent a month in agony.

Then a family member died. Then I made no money from the sale of a business I did everything to help get off the ground, then I helped renovate an entire house on short notice and sell it, then I lost two months living in a hotel
while looking for a new place to live. Then I spent two and a half years suffering low-level alcoholism, insomnia, and drifting between jobs.
Then I wrote amazing poetry. And then I rediscovered my love of math. And then I made out for the first time in over a year. And then I rediscovered my love of piano and guitar. And then I fell into severe depression for the last year. Then I made actual discoveries in math. And I learned to love my hobbies again, and jog, and not drink so much, and sing, and go on long drives, and occasional hikes, and talk to people again, and even start designing games and UIs again. And then I learned that doing amazing things without a lot of money is still possible, and then I discovered the sunk cost fallacy, and run on sentences, and how inside me there was a part of me that refused to quit because of circumstances I couldn't control, and then I learned that life goes on even when others lives have ended, even when everything and everyone never had an once of faith in you, and you've become the avatar of the bad luck brian meme..still, life goes on.

And we try to pick up the pieces, try, one more time, because the climb, and the fall, and the getting back up, is all there is.

What I would recommend, if you're thinking of making a game, or becoming an independent game developer, is, unless you have a *lot* of money upfront (think 50-100k saved, minimum, like one years income *bare* minimum), and unless you already have a full decade in the industry--don't make a game.

Just don't.

Apps are getting saturated now, i dont think if app development has a future anymore.
No matter what you make its quiet difficult to beat the top 10 trending apps.

I often wonder why JS is the only language that has the native support from browsers and native built in DOM apis?
The world has come up to a saturation point for so many techs:
- if a software is needed to be created for mobile, it must go through 1 layer of java (aka JVM) or objective C (i guess? for ios) before being understood by the CPU

- if a software is needed to be run via browser( which itself is made to run on jvm, objective c or machine language), it must go through one layer of js interpretters before being understood by the CPU

all the OS are made on C but the application and application platforms are made on specific languages. I wonder why can't there be a single application platform, if all of them(browser, JVM,objective C and whatever .exe apps run on) are doing the same thing and are equally mature to handle every usecase?

Social keep seeing everyone gush over every new Samsung S series devices displays and got to test out the s10's display and you know what...

I hate the displays, the saturation is unbearable and it just looks over done and like it's compensating... Am I the only one?

I feel like there's an over saturation of dev sites talking about "tutorial this" and "best practice that". Would be refreshing to have developers just talk about their grind and not so much their showing off of what they just learned from Stack.....oh wait a minute!! Must be how this devRant came to be! Hmmm....fuck me, epiphany. Who knew?

I think web dev has reached its saturation point... App dev still has got some scope since everyone in the world carries more smartphones than laptops.

Hello to everybody. You cannot imagine how blissful it feels to know that those who are reading this are sane. The rest of the world has gone mofo bat shite certified crazy. My question is I acquired a Samsung Desktop (it's a laptop) pc with the cam app 2020.127.20.0.
The cam app is horrible. There's no colour saturation and when I increase the brightness I look like a photocopy from and old machine.
The thing is I don't even find a chat link or phone number for the USA on their site. Does anybody have that info?
Thank you in advance, Jonno