I remember it being around 2001 - 2002 and seeing the first implementations of Microsoft for Javascript requests and at the same time the DOM was started to be a thing you could actually manipulate and I started experimenting on doing programmatic page updates for a system I was developing for the office I was working for (I worked for a state office back then).
Then the big crisis of 2002 hit (I live in Argentina), I lost 2 of the 3 jobs I had at the time (And the one that I kept was the one bringing in the less amount of money) and I ended up moving to Spain for a few years.
When I finally managed to land a job coding (2007) AJAX already had its own name and dynamic pages were taking the world by storm (And to hell, via callbacks).
P.S.: That "I invented AJAX" was obviously tongue in cheek. I'm pretty certain that there was a lot of people doing the same thing all around the globe, and very likely that was the idea that got that implemented on the MS side of things in the first place.
This was like 2004ish.
I invented a lot of things for myself... AJAX was one of them but also I used a lot of animated GIFs for transitions
I made dailytutor.com back in 2003 or so!
The domain name expired so I saved the site at http://thetutorbase.com Sadly the hostgator or whatever hosting it made php errors now for sessions But some of it still works Check it out :)
They didn't think that would work.
The fun result of that was for a few weeks I thought that I was going to get rich from having invented unit testing.
What we have today is far more efficient, I don't miss it but I definitely look back on those days with nostalgia.
It's a pity that this point will be lost to downvotes.
There is a common problem when the work of people that put the time in to really understand, test, improve and document the things we rely upon is undervalued and when that which is rewarded is superficial understanding and gluing together things that barely work is prioritized.
Yes, iterating quickly is important. Yes, it's also important not to waste time making something more robust than it needs to be. I'm not disputing that, what I AM saying is that as things scale up and hundreds of users turn into hundreds of millions of users, it's extremely important to have a culture of rewarding the people that take the time to make these systems robust and continue to ensure they perform well.
As a small anecdote, this was really driven home by a one-on-one meeting I had with an old manager: I'd started working at a small startup which almost completely lacked any kind of documentation and almost everything needed to be figured out by trial and error or (equally common) by pestering the couple of people who had things like passwords and keys and admin access to do things necessary to let a new developer begin development work.
Realizing this was going to be a giant pain in the ass as we scaled, I took the time to write a ton of documentation, checklists, scripts and onboarding docs so that new developers could get up to speed quickly. I then trained the new devs as they came onboard to ensure they got up and running as fast as possible.
Back to the one-on-one: I ended up getting told that my performance was a concern because, unlike myself, the new developers had managed to get up to speed and become productive very quickly and it reflected poorly on me that I had taken so long.
Since then, I've taken a lot more care to assess the culture of a company before doing what I consider to be "the right thing" and do deeper-level work.
It's easy to be cynical about modern software, but remember it can still be sold and the economic benefit of being able to quickly throw together something that looks like a finished product to test an idea is hard to quantify.
I developed a product like what you described and started a company using nothing but my laptop and an AWS account. To make the same product in 1997 would be difficult if not impossible without very deep pockets.
And likely 10-100x the quality and reliability, and without needing to sell every bit of your personal information. Has anyone stopped to ask, maybe we just don't need all of this software?
The selling of personal data is a good point, though. We surely could use less of that.
`import <a career's worth of work>`
I sometimes feel like every project is either learning a new thing as you go (for no other reason than that it’s new and cool) or maintaining some written be someone who was learning as they went (because now that bug ridden pile of crap is running in production).
I saw a group of people in a web community (comics sharing group in a small town) self-organize to collectively fund a couple of them (one artist, one writer) for printing a short story that they'd done and never got payed for. Each person that contributed got a signed copy!
I thought, hey, this could generalize to all sorts of stuff if there was a platform to help organize it! Mused around with it for maybe a couple of hours, became a bit disheartened by the legal aspects of it, and put it on a 'TO-DO' list.
Six months later I heard the first things about Kickstarter and realized I missed the boat
It doesn't work against an adversary that can intercept and change your packets ("Mallory"). If properly implemented, it can work against an adversary that can only observe them ("Eve"), but I've seen implementations that just hash your password before sending it on the wire. In that case, you just have the same problem as before, but the hashed version of your password is your "real" password.
For games, the catalyst was 3D games consoles.
A bunch of folks online had their own scripts as well. Eventually a few people would release their scripts and it would become known as a "weblog" and eventually a "blog" and many people profited from that.
Wild times.
The biggest thing I remember to have "invented" by myself in early 1996 (at the same time as thousands more) was the database driven website: I was tasked with creating a "virtual campus" kind of website with forums, chat, assignments, calendar, grades, news... and the sparse examples and models I had found for all those functionalities used plain text files as storage.
After completing a prototype I was obviously sick of dealing with those files and suddenly thought: "hey, dumping all this crap on a few tables in a database would make everything so much easier!" It felt a bit mind-bending, because you were taught that databases were for internal "databasey" things: Accounting, addresses, customers, widgets and their prices, that kind of stuff. Using a database as storage for a forum or a public-facing website felt almost like a revolutionary concept.
By the end of the project I was quite bored of writing plain SQL and I had something very close in spirit to many ORMs/ the Active Record stuff from Rails. So I sort of "invented" that too.
Another thing to reflect on is that I wrote all that as plain C through CGI. The database was mysql. I tried to run it a couple years ago and it compiled and ran almost straight on a modern Linux system, after like 20 minutes fiddling with Apache and the makefile, 20 years after the fact. My current projects seem to rot every time I take a short vacation.