My father took me to that conference so that would be closer to 2000 or 2001.
Fun fact, around that time I attended 3 "microsoft summit" - that was the name of the event - and every time the absolute banger, booked out months before the event, was a workshop with a guy who specialized in optimizing windows licensing for enterprise.
That was still the time when MS charged per CPU on servers, and the guy used to give couple seemingly basic scenarios and asking crowd how would they deal with licenses. Every time his version was 3-4x cheaper than what you would think of.
Ever wondered why, even on modern websites, css is riddled with repeated statements with this weird "moz-" prefixes?
In 2006 when working at Wikia I wrote a tiny lib for deep linking.
The lib started at 25 lines with naive implementation of the documentation.
Two weeks later when I had all browsers on all operating systems mapped out it was close to 1,000 lines.
I've spent half of my coding time working with Flash, and the monopoly was great. You could make a layout, write a code and have absolute certainty that the outcome will look and feel exactly the same regardless if you ran it on desktop, in the browser - any browser, mobile or kiosk.
Few years later I did UI for The Witcher and Dead Island and with that you can add xbox and playstation to the list.
Last time I did some web programming was 3 years ago, but it was still a far cry from that experience.
In 2004 we solved the types for JS with ECMAScript 4 (or ActionScript 2.0).
Unfortunately this was in the middle of browser wars, so no one cared about the standards and all of that work was lost like tears in rain.
Around that time I attended MS conference where they introduced IntelliSense and it was a forming experience for myself. You could do actual programming basically with <space>, <dot>, arrow keys and <enter>.
"x = " and there are only two variables in the scope with the same type so IDE will present them to you in a drop down and you can already think about the next line.
Fast forward to ~2015 when I'm working on Angular project. The whole idea feels like a caricature Chinese whispers of an OOP framework. Each component is divided into three files, all of them have to identify themselves using a magic string, and that string has to be manually entered into each file.
There are couple of type systems, like the one from Facebook, but no one is using them. And everyone claims that OOP and types are the thing of the past.
Part of that corelates to a joke I was making back in 2013, soon after Apple killed Flash and everyone started doing JS everywhere. Major companies where posting job offers for senior javascript devs asking for 5-7 years of experience. But someone who was doing JS for 7 years in 2012 has all his career focused around gluing together jquery plugins.
Anyway, I'm as well glad that we finally did a full circle and finally have some sanity in the industry...
would it be possible to gdrive/rsync/git the data between machines and then use the data on an online server for retrieval (given that I would handle data sync myself)?
also what exactly are you using for search? does it support trigrams? how do you sort results?
I'm sorry for not taking the time to read the docs, but I have a question.
Some 20 years ago a friend of mine has set up a local proxy (python if I'm not mistaken) that was gathering all his web traffic and served him as a long term memory. The proxy had a web interface and allowed him to quickly find something he saw ca. 10 days ago, or that specific algorithm he recalls but can't remember it's name.
For years I've been collecting links to different work related trivia which I use on a daily basis as a rabbit-from-a-hat solution to answer random question from friends and coworkers. For example someone randomly asked me for an idea for color palette for data charts and I can immediately give them a scientific research into the color palette. Or an obscure algorithm.
But with time the collection has grown substantially and it's really cumbersome to find the proper things.
also a tangent - I can't find it right now - something I feel quite similar, albeit far less practical, was an experiment in which neural network was laid out as a 2D grid, i.e. screen, and it was trained so that specific inputs would fire very specific neurons and in that way the "screen" would show a specific image.
what was particularly interesting about that experiment was the fact that you could pack quite a few images in a very small network.
My biggest gripe about AI is that very few people actually understand that, and many think that LLMs are "thinking" and capable with "coming up with a novel solution".
They are not. The only reason one might think the solution is novel is because they never saw it before, but what they are actually receiving is an excerpt from someone elses blog post or stack overflow answer. [1]
A bit terrifying thought experiment is to accept for a moment that programming is dead and all its left prompt engineering. Fast forward 5-10-15 years and whos left to actually produce new code and ideas to feed LLMs?
[1] one thing I like to do from time to time - especially when I'm asking for something I know little about - is to copy and paste the answer back to google and look where did that answer originated from.
One time I asked a very specific linux shell command and the answer didn't sit right with me. I googled it and it pointed me to a stackoverflow question. It was the first answer with ~1000 upvotes. But it also had a comment with ~700 upvotes explaining why you never ever should do that. :)
My mental model and go to ELI5 is "imagine you compressed the whole internet into a zip-like archive and you have an extremely clever and efficient way to search it for data".
I'm old enough to remember the time when you could order wikipedia on CDs and I don't see much difference between that and downloading LLM.
On one hand I've been using almost the exact statement 25 years ago in my Flash (ecmascript) tutorials to narrow down the point of operator precedence.
I still believe it's a good piece on your powerpoint if you want to teach.
It's easy to fall, easy to grasp, and easy to unroll all the rules - that is, if the rules are actually set in stone.
On the other hand I've been through couple FAANG interviews, and twice I was presented with something similar and after I glanced at it for a half a minute the interviewer quickly proceed to "a ha!, you don't know! the interview is over , but I'm happy to tell you the right answer".
I literally went to an Apple Store the other day after every influencer released their video on yt claiming that it's a great computer, you just have to install the pad in less than 3 minutes and it will work like a charm...
So I asked the salesperson about that and they told I'm not allowed to tamper with the device and it will void the warranty.
Seasoned, well trained engineers have created hundreds of thousands in billing on AWS through a simple mistakes overnight.
It's immediately reminds me of putting microtransactions into children games on mobile devices - a venue that has been thoroughly explored some 10-15 years ago.
I can't see payment and provisioning as a blocker in any scenario.
This has a potential to create a massive yet very dubious income stream for the company.
It's easy to stop drinking when you do it socially.
There are many people who would consciously love to stop drinking but can't find alternative to stop the storm in their heads. This could be caused by many things, from trauma to ADHD.
The best quote I heard about addiction is: "I only have control over my first drink".
The worst part is that alcohol and drugs have a strong stigma, but for people who are suffering anything that can turn their mind off is viable, gambling, binge watching tv or playing video games. The latter are often overlooked and ignored by relatives.
Back in the days I was making Flash games, usually a 3-5 weeks job, with no real QA, and the project was live for 3-5 months. Every time I was ahead of schedule someone came with a brilliant idea to test few odd things and add couple new features that was not discussed prior. Sometimes literally hours before the launch.
Every time I was making the argument that adding one new feature will create two bugs. And almost always I was right about it.
Fast forward and I'm working for BigCo. Few gigs back I was working for a major bank which employed supper efficient and accountable workflow - every release has to be comprised of business specific commits, and commits that are not backed by explicit tickets are not permitted.
This resulted in team having to literally cheat and lie to smuggle refactors and optimizations.
Add to that that most enterprise projects start not because the requirements were gathered but because the budget was secured and you have a recipe for disaster.
Let say I am a junior SWE in EU. I incorporate in Estonia and issue my employer with an invoice from said company. That company pays for my house, my car, my dental service and whatnot, and what's left I take as a employee salary.
I pay local tax for that salary, but that's only a fraction of what I've billed my employer.
You're not wrong, but you're missing the best part.
Estonian company does not pay taxes (*). As long as the money stays within the company he's golden. The company can pay for his car, his apartment/office, etc.
It is only when he decides to withdraw the money the problem occurs.
What you're saying applies to most EU countries. Here where I live you have to reside for majority of the year in given residency to pay taxes over there.
Here's the tricky part.
Estonia is part of Schengen Area. Which means you can travel there and back without passport. There's no paper trail of your arrangements. You can easily create a reality in which you reside there for majority of time.
But again, that's not the selling part of Estonian LTD. Which is - it's extremely easygoing and as long as money stays in the company you're not paying taxes.
My father took me to that conference so that would be closer to 2000 or 2001.
Fun fact, around that time I attended 3 "microsoft summit" - that was the name of the event - and every time the absolute banger, booked out months before the event, was a workshop with a guy who specialized in optimizing windows licensing for enterprise.
That was still the time when MS charged per CPU on servers, and the guy used to give couple seemingly basic scenarios and asking crowd how would they deal with licenses. Every time his version was 3-4x cheaper than what you would think of.