I've watched the video and was wondering why this hasn't been "invented" previously? It looks like it just vibrates the arm randomly, doesn't seem to be trying to perform any counter-motions or anything.
From what I've heard, the Oracle DB instances on the Oracle cloud are fully managed. They're also in a HA environment. With AWS you'd have to find a vendor to configure and manage that (or do it internally).
One major problem with RT was, even inside the realm of Windows store apps, it could only run apps targeted for ARM. Those were a subset of Windows store apps. The failure of RT may have been caused by the failure by Microsoft to produce a viable ARM compiler.
We used Oracle here, both the RDBMS and B2B platforms. Our instances were installed entirely by consultants sourced by our Oracle sales rep. A few years after installation, Oracle audited us. They found that one of our testing servers was apparently installed with the Data Warehousing option enabled, an option that we had not requested nor were licensed for. Oracle hit us up with an extra six figure invoice for that DW option. Keep in mind, we never requested it, never used it, and their own representative erroneously installed the option.
The boss was livid and the next 24 months were spent migrating (painfully) to Postgresql.
Latency considerations aside, I just don't see service interface design as being any different from designing a class used on any other layer. If people were allowed to construct gigantic monolithic service interfaces, well, that was probably poor design overall and not specific to service architecture. There was never anything about SOA that precluded building narrowly-scoped interfaces.
How is service (aka remote interface) design any different than designing a local interface? Doesn't the entire discussion of microservices just completely regurgitate overall software design discussions that have taken place since the 60s? Isn't call latency essentially the only difference?
OK, so this is a common scenario for a discounted room... the rooms facing the bar are the ones with the highest discount. You're trying to sleep and all you feel is thump-thump-thump from the bar's Ibiza-wannabe sound system.
I agree that it's definitely necessary to make sure you're getting a competitive price. My suggestion is don't lowball the operator or the joke will be on you. I think it's a somewhat recent change, too, where the hotel industry has tired of being beaten up with another layer of transaction fees and they are now meeting or beating the aggregator.
Smaller operators have been through this for decades, with the franchiser typically taking a huge cut of bookings made through the central reservations system (pre-WWW), as well as forcing the franchisee to buy particular reservations software, pay for "advertising", etc.
I actually agree with you 100% and that's what separates good hotels from bad ones. The highly-discounted rooms, at a good hotel, are rooms (in the same room class) that may be slightly noisier or may be slightly more worn (rooms near the pool wear much quicker). But every room should be clean and safe, no matter how the room was booked.
There's exceptions, for sure. It's another general rule - in addition to the best rooms in a given room class going to the least-discounted guests, they'll also fill the better rooms first if occupancy permits. The idea, on both counts, is to reduce exposure to refunds or additional discounts. In the $100 room class at "The Love Palace", the $50 guest gets a better room than the $30 guest. However, if occupancy in that room class is only 50%, they'll fill the rooms in order from best to worst.
Absolutely. The "rack rate" on the back of the door, in US hotels, just represents the highest room rate the hotel can ever legally charge. So, of course, the hotel keeps that at an absurdly high price. You should always expect huge discounts off of that, it's not really even usable for any sort of price comparison. The rate might hit that on one or two days a year, such as new years at certain hotels.
I see why you can't believe what you read on the internet, it's because you can't read. I never said to compare rates _at the hotel desk_. You also don't seem to understand that, inside of a single class of room in the hotel's stock, that the rooms vary in quality. If a $600 rack rate room that normally sells for $200 discounted is made available to you for $150, I promise you that when you check in you will get a crappier room than the guy that paid $175 for a room in the same room class.
What I meant to convey, which I did poorly, is that inside of those different room classes (ocean view, parking lot view, etc), the worst rooms are the ones that end up discounted on the travel sites. So you may have ocean view rooms that all go for $200/night and parking lot views that go for $100. The $125 ocean view room on Travago will be the crappiest one inside of its room class.
I can tell you from working in the hotel industry... the lower priced rooms are the worst rooms. Either they're the most worn, something's wrong with the A/C, or they're adjacent to noise sources. A much better recipe for a pleasant hotel stay is to find a hotel in the general price range you're looking for, then go to the hotel site and select a room based on your budget.
In the majority of the cases, the counterfeit product is a poor quality visually-similar item. It's very rare these days that a counterfeit item comes from the same factory as the legit item.
If your software is in an environment subject to SOX regulations, a developer can't have access to the production environment, nor can they have the ability to put the prod code in place.
Good to know. I do a fair amount of API work with Fortune 100 companies. I recently received an email from an Amazon recruiter concerning a position in one of their API teams. I can't remember anything and have to look up my first name when people ask, so I'll skip this interview.
Yeah, in reviewing your link and others, the only thing I can figure is that I somehow misread an article discussing Netflix's international streaming revenue.
Slashdot Mirror
You're forgetting that you are the product. Advertisers are the customer.
I don't think it would require as lengthy of an approval process as you may think, since it would be considered a Class 1 medical device.
I've watched the video and was wondering why this hasn't been "invented" previously? It looks like it just vibrates the arm randomly, doesn't seem to be trying to perform any counter-motions or anything.
From what I've heard, the Oracle DB instances on the Oracle cloud are fully managed. They're also in a HA environment. With AWS you'd have to find a vendor to configure and manage that (or do it internally).
One major problem with RT was, even inside the realm of Windows store apps, it could only run apps targeted for ARM. Those were a subset of Windows store apps. The failure of RT may have been caused by the failure by Microsoft to produce a viable ARM compiler.
It was all good until the audit. We ran 8i for over a decade, the non-licensed DW instance was part of a newer 10g installation.
We used Oracle here, both the RDBMS and B2B platforms. Our instances were installed entirely by consultants sourced by our Oracle sales rep. A few years after installation, Oracle audited us. They found that one of our testing servers was apparently installed with the Data Warehousing option enabled, an option that we had not requested nor were licensed for. Oracle hit us up with an extra six figure invoice for that DW option. Keep in mind, we never requested it, never used it, and their own representative erroneously installed the option.
The boss was livid and the next 24 months were spent migrating (painfully) to Postgresql.
I spit out my damn drink, good one!
Latency considerations aside, I just don't see service interface design as being any different from designing a class used on any other layer. If people were allowed to construct gigantic monolithic service interfaces, well, that was probably poor design overall and not specific to service architecture. There was never anything about SOA that precluded building narrowly-scoped interfaces.
How is service (aka remote interface) design any different than designing a local interface? Doesn't the entire discussion of microservices just completely regurgitate overall software design discussions that have taken place since the 60s? Isn't call latency essentially the only difference?
And those IT "hammer to wood" roles are the first ones that get shipped overseas.
OK, so this is a common scenario for a discounted room... the rooms facing the bar are the ones with the highest discount. You're trying to sleep and all you feel is thump-thump-thump from the bar's Ibiza-wannabe sound system.
I agree that it's definitely necessary to make sure you're getting a competitive price. My suggestion is don't lowball the operator or the joke will be on you. I think it's a somewhat recent change, too, where the hotel industry has tired of being beaten up with another layer of transaction fees and they are now meeting or beating the aggregator.
Smaller operators have been through this for decades, with the franchiser typically taking a huge cut of bookings made through the central reservations system (pre-WWW), as well as forcing the franchisee to buy particular reservations software, pay for "advertising", etc.
I actually agree with you 100% and that's what separates good hotels from bad ones. The highly-discounted rooms, at a good hotel, are rooms (in the same room class) that may be slightly noisier or may be slightly more worn (rooms near the pool wear much quicker). But every room should be clean and safe, no matter how the room was booked.
There's exceptions, for sure. It's another general rule - in addition to the best rooms in a given room class going to the least-discounted guests, they'll also fill the better rooms first if occupancy permits. The idea, on both counts, is to reduce exposure to refunds or additional discounts. In the $100 room class at "The Love Palace", the $50 guest gets a better room than the $30 guest. However, if occupancy in that room class is only 50%, they'll fill the rooms in order from best to worst.
Absolutely. The "rack rate" on the back of the door, in US hotels, just represents the highest room rate the hotel can ever legally charge. So, of course, the hotel keeps that at an absurdly high price. You should always expect huge discounts off of that, it's not really even usable for any sort of price comparison. The rate might hit that on one or two days a year, such as new years at certain hotels.
I see why you can't believe what you read on the internet, it's because you can't read. I never said to compare rates _at the hotel desk_. You also don't seem to understand that, inside of a single class of room in the hotel's stock, that the rooms vary in quality. If a $600 rack rate room that normally sells for $200 discounted is made available to you for $150, I promise you that when you check in you will get a crappier room than the guy that paid $175 for a room in the same room class.
What I meant to convey, which I did poorly, is that inside of those different room classes (ocean view, parking lot view, etc), the worst rooms are the ones that end up discounted on the travel sites. So you may have ocean view rooms that all go for $200/night and parking lot views that go for $100. The $125 ocean view room on Travago will be the crappiest one inside of its room class.
I can tell you from working in the hotel industry... the lower priced rooms are the worst rooms. Either they're the most worn, something's wrong with the A/C, or they're adjacent to noise sources. A much better recipe for a pleasant hotel stay is to find a hotel in the general price range you're looking for, then go to the hotel site and select a room based on your budget.
And sadly, Snapper eventually ended up in Walmart, years after that article was written.
Troy-Bilt is one of a dozen-plus garbage brands made by MTD.
In the majority of the cases, the counterfeit product is a poor quality visually-similar item. It's very rare these days that a counterfeit item comes from the same factory as the legit item.
If your software is in an environment subject to SOX regulations, a developer can't have access to the production environment, nor can they have the ability to put the prod code in place.
Good to know. I do a fair amount of API work with Fortune 100 companies. I recently received an email from an Amazon recruiter concerning a position in one of their API teams. I can't remember anything and have to look up my first name when people ask, so I'll skip this interview.
Yeah, in reviewing your link and others, the only thing I can figure is that I somehow misread an article discussing Netflix's international streaming revenue.