reflectiv

my current job still uses it deep in some abstraction created ages ago...

AI in general at the time was led by a VP and a particular group (that was AI tech specialized) under him. The initial idea came about from them. We were trying to find new ways of using AI to research new sources of crude at the time.

Another AI project I worked on there was a chemical tank use estimation and refuel application which used tank sensors, previous use history and some other metrics to pre-purchase and deliver product to keep tank reserves above a certain threshold.

For context, all of this was circa 2018-2021.

I was a developer at Shell a couple years back and led a project where we were using nascent GPT-1/2 to process and search over mountains of documents. It was a fun project where I wrote a complex/fancy UI for a stratigraphic filter and indexing system...

Seems this is just a natural progression...neat.

...and its been hugged to death in minutes.

What kind of stupid statement is this...no it certainly does not.

But humor me with an explanation, please...

The 'light-based' network thing kinda threw me for a second...wifi IS technically light, its just a frequency (RF) at which we can't see it and that can (somewhat) penetrate walls.

His timeline sounds exactly right to me, I basically did the same thing.

Mid-late 90s I used Beej's network programming guide to write an IRC client.

> Which sites do that for any meaningful reason?

Literally none...this is just the argument of contrarians or people who've only ever worked on personal projects who take offense to real applications used by actual audiences.

> I actually can't imagine any other use for vh that isn't related to screenjacking

Creating fixed panels on the left or right side of the viewport that are full height and sticky.

I think we're making a supervillain recipe here guys...chill

Yes, I do this too...its a different thing when you are talking about your own insular project or something at a smaller scale.

The thing I was talking about was larger scale projects like the ones mentioned by the author (of the sort I work on at my day job) where you have teams of stakeholders and outside influence combined with a desire to release rapidly in an iterative form.

Software these days is just done differently in those contexts...we can't slow down enough to do what was detailed above...I just wish the world was sorted in a way or slowed down enough to do REAL engineering.

I really wish software was written this way these days.

These days I am always being rushed through sprints barely knowing what is going on.

What you described sounds like a wonderful way to actually engineer a great API.