3,404 karma · joined October 26, 2016
The reason I say I believe the person had to be Chinese is that the city, from what I know, is well known to be hostile to people who don't live in the city, and especially to people who look western and aren't with an escort. It was a very insular place, where even that person doing the runthru was taking a big change being stopped by someone, but probably would've had less hassle than someone who definitely didn't look like they belonged there.
Anyhow - it was a kind of "urbex" video of a place that - at the time - was still a vibrant, if mostly lawless - place of people going about their lives. Quite amazing to watch and see, honestly.
MS worked with SGI on a project known as Fahrenheit - to unify Direct3D and OpenGL:
https://en.wikipedia.org/wiki/Fahrenheit_(graphics_API)
...well, we all know what happened - but I've often thought that Microsoft hastened their demise.
Somewhere in there, of course, was also the whole SGI moving away from IRIX (SGI's unix variant) to Windows NT (IIRC, this was on the Octane platform) - there being some upset over it by the SGI community. Maybe that was part of the "last gasp"? I'm sure some here have better info about those times; I merely watched from the sidelines, because I certainly didn't have any access to SGI hardware, nor any means to purchase some myself - waaaaay out of my price range then and now.
Of course - had SGI not gone belly up, I'm not sure we'd have NVidia today...? So maybe there's a silver lining there at least?
> Hilbert Curve pattern
OP is going to be outside for a while depending on the level of precision of that particular "pattern"...
If it doesn't do that, then the other annoying thing it sometimes does is drive off into a bedroom and go underneath our king-size bed, then "dies" (runs out of battery) somewhere in the middle of the bed area, which makes it very difficult to coax out. Neither my arms nor my wife's are long enough to reach it; I generally have to use a broom handle or such to shove it closer to one side to pull it out.
First-world problems, right?
I found an old Friendly Robotics lawn mower robot on Craigslist and purchased it for $50, thinking of using it for my lawn but I never got around to doing anything with it. Mainly because I couldn't think of an easy way to detect the perimeter of the lawn without an edge wire!
I guess it's not an easy problem to solve.
I had considered a bunch of options, a few of the ideas I had were:
1. Some kind of camera or color sensor, looking downward, to detect "green" vs "non-green" - assuming the grass was green and non-grass would be some other color. That would work ok for most of my yard, but my lawn in front doesn't have an "edge" with the neighbor's lawn - so it would mow their lawn, too - not what I want.
2. A passive perimeter, consisting of a bunch of spaced (maybe 6" between?) magnets - I thought maybe plastic golf tees with a rare-earth magnet glued on top would be ok; then use hall-effect sensors on the robot's perimeter to determine if it had crossed over the line of magnets.
3. This one was more to detect cut vs uncut grass - but use some kind of humidity sensor; assuming cut grass has higher humidity than uncut grass, "sniff" the ground and avoid uncut (drier) areas. The problem with this concept, mainly, was in not being able to find high-speed humidity sensors/detectors.
At any rate, I never followed through with any of this, but maybe someday I might return to it? I am curious on the cost of this iRobot lawn mower, though. I'm guessing 4 figures, given what I know about the price of their vacuums (which my wife loves; every time one dies, she buys a new one, and the old one I save for my future Roomba army to take over the world with).
If my guess is accurate, then I'll just have to put off buying one, as it will still be cheaper to continue to pay my landscaper to cut my lawn (and this robot won't trim trees or bushes yet, so...)
Loading paper onto those printers wasn't an easy or fun task; there were typically two tractor mechanisms, one below the printing area (usually inside the sound deadening enclosure), and one above it (still inside, but under the "lid" of the enclosure). You had to get things lined up just right, and then snap the feeds closed on the bottom (while kneeling and looking - sometimes with a flashlight - at an awkward angle under the printer, inside the enclosure, with a large box of paper in your way), then advance the paper past the print area, and align it properly with the second set of tractors, then close those - then run a test job. If all went well (which it usually did), you had things loaded and could continue with your other tasks.
Oh - and the cleaning of those printers - so much paper dust, plus the "chads" from the holes (not all were cleared on a run of paper, so the tractors would pop them out and they would get lost all over and inside the machine).
> Jobs were printed with special "separator pages" to help to operators find where to split the perforated printouts and deliver them to the right users' collection bins.
Fun times to find your "job" and split it off to take back to your cubicle; also fun to find someone else's job and deliver it to them on the way back. Sometimes they'd be thankful or surprised, but it was also fun to do it when they had gotten up to go to the printer - they'd get there, couldn't find their job (but could find the ones "around" it), go back to their desk in a huff, then sit down and find the printout on their desk...hehe.
I kinda miss those days (but I don't miss having to build and format reports - talk about a nightmare and thankless task).
I applied for a position (any position; at the time, I was still in school) and they hired and trained me as an "operator" (because I didn't have a degree, they told me, they couldn't hire me as a programmer). They put me in a small cold room with the main computer they worked on (via serial terminals) - an IBM RS/6000 AIX box. There was also a vacuum column 9-track tape drive (which they taught me how to load and use), and a large Genicom 4440 printer.
IIRC, the printer was a dot-matrix line printer, so it could fire one row of "dots" out, eventually forming the characters as the paper moved. Even in it's enclosure, it was loud, but it could rip thru a box of greenbar in no time flat.
The printer was something they sold as VAR to their clients, because it could handle multi-part carbon paper forms, like checks. We'd write programs to print to these custom forms (holding the paper up to the lights and lining up the characters with the form positions - ugh!). So, when the client used a program that printed, they were also expected to check if the printer was in the middle of a printing job, and had the write paper loaded.
Sometimes, though, we'd "dial in" to their machines to test certain code and get feedback via phone; sometimes that code was for a printer (imagine trying to debug proper printing formatting and such over a phone - hair pulling!). Well, sometimes they wouldn't check the printer before we'd run the software (even after we told them to do so). That printer would take off...
...and then we'd hear a scream over the phone for us to "stop the printer" because it would be ripping thru the box of multi-part check paper (actual physical checks with carbon copy) with whatever we were printing (generally, not checks).
Clients sometimes did this themselves as well - and eat thru an entire box of checks before they knew it; multipart check forms were (from what I understand) stupid-expensive (because they were custom printed for an individual account, not too mention the special paper they used, plus the carbon copy capability).
Ah - those were the days.
And yes, I eventually got hired as a programmer (aka SWE), before I turned 19; in between me loading tapes or running print jobs for the programming teams and such, I would also play around with learning the software they used (a variant of PICK called UniVERSE), writing small games and other such things. One of the sysadmins gave me a copy of a book on PICK to help me along, and they were "monitoring" my account. Eventually, they started handing me small tasks - "fix this bug" or "code this custom feature" - to see if I could do it.
I could, I did, and I eventually was hired, sans degree, as a programmer - and started my career that I still am doing today, as an SWE, nowadays doing SPAs using Node.js, React, and other technologies (I've lost track of the technologies and software over the years I have known, used, programmed in, etc - suffice to say, I haven't done it all, but I've carved a big chunk out, certainly).
Oh - and that place was also my introduction to Unix (via AIX on that IBB RISC platform); by the time I left that job, I knew terminfo like nobody - I had to, because we were always needing to set up clients systems with it properly to handle their serial terminals, and do it in a way that was also usable with terminal emulators on PCs, and such - it felt pretty crazy at the time).
One of my earliest "computer memories" as a kid was being in a Radio Shack in the early 1980s and seeing a large dot-matrix printer outputting a maze on greenbar paper; the printer sat on a cheap printer cart thing that Radio Shack sold, and as the head moved back and forth, it caused the cart to also "flex and sway" with the movement (again - cheap particle board and screws, bad construction, age - all factored in).
I think the printer was connected to a TRS-80 Model 3 or 4, IIRC.
At the time, I "owned" (parents purchased - and I still have it) a TRS-80 Color Computer 2; which is probably why I was in the store with my Dad, probably buying something for it. It was my first "real computer" (my first "computer" - and introduction to programming - was the controller of the Milton Bradley Big Trak; I still have it, too).
You could do this easily with cheap parallax sensors (like you find on Neato vacuum cleaners, and which are now sold as separate units - RPLidar and such). This has also been done using SICK coffeepot-style 2D LIDAR units (such rigs tend to be large and heavy, tho).
Something I've often considered is the idea of a "stochastic" scanner - that is, don't worry about strict angles, just let the sensor scan at random angles, and note the angle and reading. Over time you'd build up a complete scan. Just an idea I've rolled around in my head; the idea was to eliminate the need for syncing and timing of the scan hardware (2D or 3D), at the price of not necessarily getting a complete perfect scan all the time. It was something of a thought experiment I had while thinking up ways to DIY a LIDAR sensor in a very cheap manner, beyond what has already been done.
But I kept getting mired and "stuck" in how I should architect things, or what framework to use, or this or that. I eventually decided that I wanted it to be a browser-based app of some sort (thus the road of ES6) - but then I started to wonder what tooling to use there. Lots of questions, etc - and I never got that far with it.
I eventually wised up and realized that it didn't matter what I chose - what I needed was the application to work. Who cares about frameworks, requirejs, css frameworks, etc - I just wanted something working. So I stepped back...and decided to chuck all of that away.
I ended up with a basic webpage, with a script tag and the code inside that - nothing fancy, purely procedural, old-school javascript functions, tied to events. Bare bones, basic.
...and I made real progress for the first time.
Basically, by regressing to the relative simplicity of Javascript back from the 1990s, I was able to get my tool finally going, without having to worry about the last two decades of cruft around that language. Now, I could have also done it using Python or anything else, in the same manner - but again, I wanted it to be browser based.
As you note, my own journey, and not something I'd tell anyone else to do (and certainly not something meant for a production environment!) - but for myself, and my need, this fit the bill. I'm still working on it; I figure when I complete it proper-like, I can go back and refactor it to something more respectable. Or maybe not.
After all, if it works, why try to break it? In the end, I want the results from the tool - who cares what it looks like under the hood, so long as it works.
I think the only way this could happen would be if SWE only used waterfall or some similar kind of practice. Agile and the like might be able to be tweaked to work, but even there...
The problem in software is that you can basically "start in the middle" of something and work your way outward; start coding something, get the design details later and refactor.
You can't do that with a bridge or other regular engineering work. You have to plan, design, multiple sign-offs, etc - then build, and you can't build it randomly or a component here and there then fit it all together (well, you can to an extent, depending on the project and design), and if anything changes - well, in a real project it can't change much, not without a lot of money and time being lost.
Several years back there was a series of commercials on TV, I think for an insurance company, which showed (using CGI effects) "impossible building strategies" - one showed a huge scaffolding structure and cranes building something like the Great Pyramid from the top downward (for instance); I think another had some kind of skyscraper being built from the middle outward or something of that nature.
That's essentially SWE applied to regular engineering - or at least, that's how it feels at times. Now tack on Agile and other practices, and it gets 10x worse. Actual engineering is a strict discipline, starting with almost set-in-stone practices along with a lot of hard-won knowledge about materials and mechanics (books filled with tables and diagrams), that are then all used to inform an engineering design, which is then tested and retested in simulation, perhaps coupled with scale models that are also tested, and the plans changed and signed off by multiple other engineers, etc - long before it ever gets to building the thing.
And then that thing is built in a very specific and strict manner; I won't further belabor the point.
Even with all of this, sometimes things fail terribly.
Today in software, we have a ton of tools and practices we are constantly trying - and despite all of them, at least from my perspective - things really haven't gotten much better than they were 20-30 years ago. I would say that widespread use of software versioning tooling and testing frameworks, etc (plus automated build and deployment) have made some of it better - but even after all that, we still seem to be making the same number of bugs and errors that we had before (and rather than a QA department usually, we've farmed this out to the end user for the most part).
So while I'd love to see SWE become more like regular engineering practices (with the selfish request that I and others like me could be "grandfathered" in, as I don't have any kind of compsci or comparable degree, but I have been doing this for 25+ years) - I just don't see it happening for the above rational and reasons.
I could be wrong, though (and if anyone has a counter argument, please post it - I'd love to read it)...
The amount of processing power we each carry in our pockets (even the cheapest throw-away smart phones) would have been almost unthinkable 30 years ago; it's akin to the difference of an Altair of the 1970s vs what was available just 10-20 years prior. What took up a room now sat on a desk and could be purchased for the price of a car.
Now, what took up a room now sits in your pocket, and almost could be given away in a box of cereal its so cheap.
Heck - think about what's available in the embedded computing realm for pennies (or just a few dollars in single quantities) - it's mind boggling to an extent.
Something I've often wondered, and there are probably good reasons why, is that billionaire tech moguls - even the ones who are outwardly technical (or were in the past - people like Bill Gates, who we know had technical chops in the past) - that none of them (that I'm aware of) haven't ever tried to build "their ultimate computer".
For instance, if I had their kind of money, I've often thought that I would construct a datacenter (or maybe multiple datacenters, networked together) filled with NVidia GPU/TPU/whatever hardware (the best of the best they could sell me) - purely for use as my "personal computer". Completely non-public, non-commercial - just a datacenter I would own with racks filled to the brim with the best computing tech I could stuff into them (on a side note, I've also pondered the idea of such a personal datacenter, but filled with D-Wave quantum computing machines or the like).
What could you do with such a system?
Obviously anything massive parallelism could be useful for - the usual simulation, machine learning, etc; but could you make any breakthroughs with it - assuming you had the knowledge to do such work?
Which is probably why none have done it - at least as a personal thing.
I mean, sure, I would bet that people who own large swathes of machines in a datacenter, or those who outright own datacenter (like Google or Amazon) - their founders and likely internal people do run massively parallel experiments or whatnot on a regular basis, ad-hoc, and "free" - but it's a commercial thing, and other stuff is also running on those machines...
But a single person is probably unlikely to have or think of problems that would require such a grand scale before they would just "start a company to do it" or something similar; because in the end, just to maintain and administer everything in such a datacenter, if one were built, would require (I would think) the resources of a large company.
Of course, then I wonder if such companies - especially ones like Google and Amazon, which own and run many datacenters around the world, and also sell the resources of them for compute purposes - weren't started in some fashion (even if only in the back of their heads) by their founders with that idea or goal in mind (that is, to be able to own and use on their whim "the world's largest amount of computing power"...?
I hate the reality that developers can't easily develop a portfolio of work because generally their work is owned lock, stock, and barrel by the companies they work for, and can't be legally shared outside of those places.
So we have github, but even that is suspect and many potential employers don't look at it, unless you are some well known contributor or founder to one or more open-source projects. Even then it can be a crap shoot; I've read on more than one occasion somewhat famous developers of tools being turned down for positions at companies that use the very tools they developed. It is somewhat maddenning.
You can just about forget it if your repositories are for your own personal projects, but that's better than nothing - and that's also where a blog has some influence. Basically, as a place to show something of your coding ability and knowledge, and the value you can bring as a new hire.
But honestly, that can get tiring; sometimes when I go home from work, I'll do something interesting - but many times, I just want to relax and not think about coding or other projects too much. I've found myself becoming more this way as I've grown older (currently approaching 50).
I've been an SWE for over 25 years now, but every time I find myself looking for a new position, it feels as though my previous experience counts for nothing. I can't show any future employer what I worked on in the past (and in many cases, that work is long gone along with the previous employer), they rarely want to look at my github or (back when it existed - I really need to restart it - sigh) my personal blogging site. It feels like every such interview and encounter I am starting fresh.
It sickens me. I don't know of any other kind of career where this kind of thing is the norm, except software development and engineering. If you aren't extremely famous and known, or you don't have a deep and wide network, or whatever - you can't just drop your resume, have a decent conversation about your past work and skills, and be given a chance. Instead, you are more often than not forced to jump thru a variety of ill-conceived hoops (many of them on fire, too!), which in the end might get you the position, or more often than not, you are rejected without any explanation or reasoning that might help you to understand what you need to work on in order to be more successful the next time around.
It's fairly absurd when you are on the younger end of the scale; now imagine you are old enough in some cases to be the parent of the person interviewing you, and still being questioned in such a manner, after likely being employed in the past longer than they've been alive.
It's almost Kafkaesque.
If you have an HOA - there might be a bit of problem...
I live in Phoenix; in my neighborhood it's basically the same way. City comes around, tears up the sidewalk to fix something (water main or such) - and you the homeowner are responsible for fixing the sidewalk. Yay.
About all the city will do is put some asphalt over the bare dirt, but if you want the sidewalk to be concrete, you have to pay for that work.
Since a lot of the properties in my neighborhood are rentals, you can guess how often such asphalt patches are properly "fixed". Usually, you have to put in a blight notice to the city to have them contact the actual homeowner to get them to actually fix it properly.
One of the downsides living where I do. But then again, I live "below my means" (as an SWE), and I don't have an HOA, and block construction, and I can work on my cars when I want, where I want, how I want. If that means an angle grinder and welder come out at 8pm, so be it. Neighbors can't complain until after 10pm or so, and only then for excessive noise.
Take the good with the bad...
You can still find a lot of this old code if you dig for it; lot's of it can be found on various SIMTEL MS-DOS ftp archive sites, for instance. I also think the textfiles site has some of it. Also archive.org might have some of it.
Take a look around using google and such: "ftp msdos source code" etc - you'll find plenty to be sure (and even if you don't find what you're looking for, you're sure to find stuff you weren't expecting!)
It really isn't much different from floor/ceiling rendering code.
Something else I was thinking was if you flipped it upside down (and kept the current view), you could render "caves"; heck, it probably wouldn't take much effort to mod the current code to achieve this.
Somewhere I have code to a voxel rendering engine someone made in QBasic; they posted a demo of it on youtube, but never posted the code - I got in contact with them, and they sent me a copy of the code. The interesting thing they did, though, was add voxel rendering of "buildings" - you could easily go inside spaces and outside, all voxel rendered, and it was fast (for QB code).
Note - I know about Ken Silverman's voxel and other 3D engines he did in QB (and posted his old code), prior to Duke Nukem 3D - but this wasn't that code; it was completely original...
Anyhow - this is a great little "3D" engine; I'm glad it was posted!
Initially turned out that it had been set to RS485 mode, and I didn't have an adapter, and I didn't even know if it worked if I was able to get it into that mode. So with the help of a sympathetic engineer at SICK, he had me send to unit to them and he reset it (to RS232) and tested it. When I got it back, I tested it with the machine again and it worked perfectly. He didn't charge me anything for the service.
You don't see that kind of support anymore - almost no company will say "yeah, sure, send us a unit you bought second-hand off Ebay to us and we'll take a look at it, fix it, etc - and no charge to you, either - even though you're just a hobbyist and have no support contract" - it shocked me.
Not too long ago I remarked here on HN that I expected VB6 programmers might become in demand in the future (when, I don't know), similar to how COBOL programmers were/are.
Basically, for the need to convert apps, written internally for a business, from VB6 to something else (likely to VB.NET or C# - maybe on Mono - but there are other options too).
I expect this to happen when Microsoft finally kills off the VB6 runtime DLL - but so far they haven't; from what I understand, it's still available in Win10...
Vultrs: https://www.vultr.com/
It's an albatross around Microsoft's neck, but every time they update Windows, they keep around the runtime DLLs - because so many businesses have software written internally and otherwise that can't migrate to something else.
If you know VB6 - and you are confident in migration to another platform, or willing to maintain old code (maybe while migrating) - you'll likely have work long into the future.
The most likely migration path would be from VB6 to VB.NET or to C# - staying on the Windows platform. Another option would be migration to GAMBAS or Mono (aka .NET for *nix).
Those feeling adventurous might try Python with QT, or some other GUI framework; at some point, it might be better just to examine and understand the core logic and flow - then convert it all over to a web-accessible system (of whatever choice you want).
I imagine that in time we'll see some kind of VB6 to WASM compiler or something, if someone hasn't already taken a stab at it. What we won't see, though, is Microsoft open-sourcing VB6 or anything like that. They've said they want to, but due to the various licenses used in the development of the language (and components) - it's virtually impossible for them to do it.
I coded in VB (3-6) for well over a decade, but it's been forever since I last touched it. That said, I'll always have a soft-spot for BASIC (having grown up on a version of Microsoft BASIC on the TRS-80 Color Computer line) - so I could probably pick up where I left off once I rebooted the VS compiler/IDE, without too much trouble.
I expect that might be where my career turns to as I get older (currently 46 and working in SPA Javascript/NodeJS apps).
In an accident, it should continue to do this to the best of its ability. Let's say something weird like a ball joint fails while driving at speed on the freeway. Now, for those of you that don't know, in a regular car this is a bad situation - essentially, your wheel is about to fall off and you have limited to no steering control.
But if the car hit the brakes, turned the wheel (however ineffective that may be), and/or did other inputs to try to avoid a pedestrian on the sidewalk, or another car, or whatever - in an attempt to come to as safe a stop as possible...
...but it still injured or killed somebody - then I'd say it did the best it could, same as a good-to-great driver would. Assuming it logged everything about everything; what went wrong, when it sensed it, what it did in response, what it saw or sensed, etc - then I'd say it should be exonerated, or at worst "charged" with involuntary manslaughter or something of that nature.
If it was programmed (whatever that means, ultimately - I'm just an amateur self-driving vehicle enthusiast; I've taken a few MOOC courses on self-driving vehicle technology, including the Udacity nanodegree for Self-driving Car Engineers - so I know some things about how this stuff really works from a code and mechanical and sensor perspective, but I am no expert) to do the best it could to avoid the situation, but it still failed - and it could be shown it tried - then can we hold the vehicle, the owner, or the manufacturer responsible?
I suppose if maybe the driver (owner?) knew they had a failing ball joint (or whatever) that led to the accident (how they would know this? especially on a fairly new vehicle) - maybe fault or blame could be laid there. Or if road conditions caused the problem (chuckhole causing a blowout at speed?) - maybe the city/state?