So much of housing in my area is high density now taking the form of row housing with multiple levels. Other homes have laundry in the basement, bedrooms on a second level. Sadly Isaac isn't going to be as useful if you have stairs.
No worries, it's going to be fascinating to hear what the investigation uncovers. Did the sensor data stream send back anything useful in the milliseconds before those sensors ceased to exist? I would assume there were no warning signs or they would have done a stand down on the test itself. So many questions!
What you're seeing is not a 'side' of the rocket sliding down, it's the rocket itself. The other part on the right is the erector stand it was mounted to. Looks like the bottom of the rocket blows out first and begins to collapse. The rocket begins to slide vertically before it all becomes one large fireball. The erector stand didn't survive the explosion either in the end.
Heidi has been my go-to SQL tool for longer than I can remember. Has been great to watch it evolve and have communicated wish list items to the developer several times with great responsiveness.
I always love this video, and I have been a lifetime dedicated fan of James Burke, but few seem to note that the whole segment didn't have to be timed as there is a cut shortly before the launch. If I recall either James or one of the producers talked about it once. They knew they had to start the last bit 13 seconds before launch and had practiced it repeatedly. At 13 seconds to countdown James nailed it. I'm sure even after practicing it I would have stumbled over a word in the clutch moment!
USER: What do you think about the idea that you're talking to someone 100 years in the future?
TALKIE-1930: I think it is an interesting speculation. In a hundred years, time will have wrought great changes both in the old world and in the new, and it will be curious to reflect back upon them from the far distance. At present, we are but spectators of the passing show, and, in little more than a quarter of a century, the greater part of the actors will have disappeared from the scene. But, in 1950, the busy bustlers of 1846 will be tranquil spectators of other bustle, and the young will wonder at the excitement of the old. Among the novelties, probably, will be the railway system of 1846. In 1950, people will travel at sixty miles an hour, and think it no great speed. They will laugh at our lumbering diligences, and our walling coaches, and smile at the dust raised by our rapid teams of four. They may even doubt, whether we were altogether serious, when we talked of ten hours, as a possible duration of a journey from London to York. They will have improved upon us, in many things, and laughed at us, in more. Let them enjoy their superiority of wisdom, and welcome. In 1950, I shall be at rest.
I used to write a lot of native Windows corporate software in the 90's and 2000's and my standard login window was a floating draggable oval. Nothing else was oddly shaped but I did get a lot of comments on the oval login windows. It was a bit about being unique, marking my "style", and just because I could. I will add though in the 90's it did make me nuts when entire applications were wildly shaped and you had to figure out how to use them.
Editing this to add: I really miss that level of coding and working with Win32. I get that the world has moved on and HTML or some runtime flavour of it has taken over but I too lament the los of true control I once had. I hate that my stack can be broken because some runtime was updated out of my control or the crazy load times of simple projects. I know many today would say it was messy and problematic (and it could be) but it's definitely a lost art form.
I was hired in the early 90's by a collection of franchises for a home care company. The privately owned head office self-developed and distributed required monthly updates to the only software franchises were permitted to run their business. The monthly updates (floppies) reset the license for another month at each location. After years of problems, poor support, and in a couple cases offices getting shut down because head office just "didn't like them anymore", they banded together to sue the owners (one of which developed the software). I did IT work for a couple of the offices and was already familiar with maintaining the software / systems. They hired me to bypass the licensing code which was a lot of fun to figure out. In the end I wrote a DOS based license generator each office had that could update their software by just getting a code over the phone for the upcoming month (or any date for 365 days). A few years later once the lawsuit settled and the company broke apart we issued a patch for the software to remove the license check completely. I should fire up DOSBox sometime so I can play with that old software again.
Let it be a choice, with the mandate that if you opt out and later contract it there will be no state funded assistance down the road. Your choice shouldn't be a burden on the system.
I loved Dilbert and I really believe that you often have to separate art from artist if you want to enjoy many things. He put a very unique perspective on corporate and tech environments that made me laugh. Sad to see a human pass but also sadder that later he expressed some disappointing opinions that diminished his contributions.
First thing I do on any Windows machine is uninstall OneDrive anywhere possible. It's caused me enough grief that I just avoid it entirely at this point.
We were on the same page. I also built something similar for a Conveyor company here in Canada in the early 90's. We parameterized all their tech drawings (or at least the initial versions) from their component libraries. Was a great project. Not sure how long they used it, they eventually acquired the resources to support it internally (I was an independent AutoLISP contractor). Good times back then. I haven't done AutoLISP in years now but great to see it's still around.
I have a folder in my server where I archive the last several versions (usually 3-5) of all software I install. It would have helped in this situation but the main reason I started doing it >25 years ago is in case companies disappeared.
Perhaps I say at all the wrong (right?) hotels but... I stay in close to two dozen North American hotels a year and I haven't noticed this trend? Many have pocket doors but I can't think of a hotel in recent memory that was missing it completely. I usually partially close them so it's not as cold getting out of a shower so I hope I would have taken note if it wasn't there.
I rode in one of these in Phoenix in June, loved the experience! Had to go to a pharmacy so purposely picked one a half hour across the city so I could just watch the car perform. Felt like the future (though it did glitch once). Made a sudden turn off the road into a parking lot, did a lap of the outside of the parking lot, and exited back onto the same road to continue on. Must have thought something was blocking the road and made a detour around it? Other than that it seemed pretty flawless.
Please make AI disappear altogether until I want it. No pop-ups, no floating "Help me..." in fields, no spinning flashing icons on toolbars. I submit feedback on all products that do this that I would like a way to turn it all off. AI is useful when I want it, otherwise it's just annoying and gets in my way.
This sounds like myself as well. We are a small dev team of 6 (in a company of 30), however I also have a partial ownership stake in the company. Even though I spend a significant part of my time on "CTO" style work (client meetings, market assessments, product overviews, roadmap planning, third party collaboration, etc.) there also isn't near enough of that to fill my time or justify my salary. I code and review like my team does, but I also oversee technical direction for our whole portfolio and the responsibility for that technical success or failure rests on me. As we grow the coding will decrease I'm sure, but I see a lot of people here criticizing from a perspective of larger companies where a CTO would be a full time responsibility. In our situation the title (as much as I often dislike it) represents my level of responsibility, if not directly the full scope of my role.
What a great summary. I was reminded of QNX through the Blackberry acquisition but I had forgotten it's history went back so far. (I should have remembered, I was around in those early PC days) With so many things these days having an operating system running them (including the mentioned cars, rockets and robots) QNX seems to have a bright future ahead doing what it does best, being the solid core to build upon.
Has an updated version been mentioned anywhere?