Joined 13 years ago
Best bet is to do mobile web development, most of the parts can be under your control and those that aren't (the phone) are beholding to web standards which can't change too radically.
Company develops product A with a crack team of developers, cutting edge stuff. Product is shipped, so the star developers go off to another project or are put in lousy roles and leave. Product doesn't change for a few years and is in maintenance mode.
When time comes to crank out a new version, those hotshot developers are gone and the new crew doesn't quite get it - they want to change the tool-chain from X to Y, remove that overly complex (but very useful) feature, radically change the UX, incorporate AI, etc. New version is mostly compatible but way different.
Seen that happen all too often.
Most of my filtering is just to keep the bots from clicking on some forms and excluding them from visitor logs. No problem with most crawlers. The bad ones are the ones that cycle through IPs, mimic agents, and space out their hits, they are the ones that clog my logs - some hit the same page multiple time (I assume some SEO tactic, which is not how my sites rank items).
My best bet might be IP filtering (restricting to US only) - wondering if any have implemented that (is that a big hit on page load time?), I would think with VPNs that doesn't always work that well...
Second, I think the power of the 64 was its' limited BASIC but it was a good start (still the best line editor of most systems, just cursor up change the line, press return and done), The no-frills in the language but not in the capabilities made it a platform where there was no one definate way to do graphics or sound so there was a lot of experimentation most good, and some downright awesome. I think not having those features baked in the ROMs made the community a lot more dynamic.
1) I was more into messaging so I would log in and read and post in the forums. Sometimes if they have a good files area might download some programs, and play a game or two (usually some simple competition game like Risk like ones.) Many boards were long distance so after a few years I started my own BBS
2) Computer magazines had BBS lists sometimes. Local computer stores usually had a corkboard with flyers of local BBSs and word-of-mouth amongst the nerds in the area, at school, etc. To connect I usually used CCGMS terminal for the C64 (for the color/graphics BBSs CCGMS is still used for the C= Telnet BBSs) and Desterm 128 or NovaTerm for the PC boards so I could see the ANSI characters. For running BBSs there were many some in BASIC or compiled BASIC, some in ML and most with a mixture ML communications/data code with BASIC modules. I ended up with Image BBS which was a modular BBS system for the C64, had lots of community mods available.
3) fragmented, depending on what you were interested in, my BBS was Commodore, Gaming, and Science Fiction forums and Commodore Files and some games. There were PC boards with the fancier games and larger FIDONet forums some other forums - sports, PC, etc. There were Apple, Atari Amiga BBSs a lot of like computers would contact those to get info and download programs (Amigas were probably the biggest on pirate software BBSs, there probably was PC ones out there too I didn't know those)
4) More fan oriented talking about your favorite things, not always too technical. Sometimes there would be some e-newsletter you could download to read more technical stuff. DIY discussions and helping others. Pretty much like internet forums and resource sites today.
5) for us some bits of BASIC and assembly, game logic, etc.
go to https://textfiles.com to get a taste of what was out there
A thing for storing and comparing schedules
a weekly schedule is turned into a run-length list (the week is in minutes 0 to 10079 - so 540,1020,1980,2460 would be 9am to 5pm on Sunday and Monday). Makes it easy to unpack the list into an array and do basic math comparison can determine whether schedule A is within schedule B or get the difference in minutes that schedule A falls outside of schedule B etc.
I would say the most complicated ones I've done are some SQL queries where I had to break it into stages to reduce the amount of grinding it did on a query that was combining many tables.
You know, this sounds familiar - the big outsourcing boon to less expensive development in other countries, sure they can write the code, but it's either shipped buggy or takes a lot of management and hand-holding of the outsourced development teams to get everything right.
Octagon - an AI backdoor created by the early inventors of computers is inadvertently "activated" by a youth.
