4 ms·

> Again, you’re looking at your little piece of work that is a speck in an entire organization. > He’s not losing sleep over whether you put a facade over your

> Again, you’re looking at your little piece of work that is a speck in an entire organization. > He’s not losing sleep over whether you put a facade over your data access layer because in some distant future long after he is gone, AWS may raise prices. Of course not — he’s paying experts to avoid that situation, aligning with his strategic priorities. That’s my job. You also resorted back to personal attacks because you can’t make your point directly. > If the spend is large enough, he’s going to talk to his dedicated sales rep to lower prices long before he comes to zmgsabt and asks him did he make his data access class “cloud agnostic”. Like this ridiculous comment to someone whose job is being hired by CTOs looking to migrate. They literally come to me, for help doing exactly that. > Hell, I released code that was part of a major official open source “AWS Solution” and got complaints a few weeks later that it was dependent on a region and that’s not the first time I’ve seen that happen. > I hardcoded the partition. > “Oh shit. The data team is loading data into the database using the AWS extension that lets you load data from S3 using a sql query” Yes — that’s why companies pay me: I’m used to doing things that can’t depend on a region, service, etc while AWS engineering frequently makes that mistake (eg, all the US-East-1 magic). That’s precisely my point: Quality coding avoids and bounds mistakes like that, which slow your migration. - - - - So you’ve resorted to personal attacks, but didn’t actually respond to my specific example, and were insistent on my credentials but still haven’t shared the largest system you personally have migrated. But please keep it up: I make my money from people like you causing CTOs to hire people like me to clean up the mess — “whoops, accidentally wrote regionalized code!” or “we need over a year to migrate 100 VMs due to self-induced complexity!”

scarface_74 3y ago
Scenario: I have $aLotOfData in S3 and I need to move it to a MySql database. Are you going to: A) write an ETL job that is going to be slower and more complex to avoid the “lock-inz” Or B) just call run “load data from S3…” As a sql extension? Are you going to tell them that they can’t use Glue? Athena? Redshift? Quicksite? When your company needs a call center are you going to tell them not to use Amazon Connect? Now they need to integrate the call center with Salesforce - are you going to tell them they can’t do that because they have to use Lambda? They want to have speech to text - now they need Amazon Lex. Then they want a reporting dashboard that comes from their contact trace records. Now they need Kinesis which is going to stream to S3. The typical company uses over 250 SaaS products that they have some form of integration with. Are you going to tell them not to use any of those either? Are you going to tell them not to use Salesforce? ServiceNow? Microsoft Office? If you work in the health care industry are you going to tell them not to use Epic?
- zmgsabst 3y ago
  That question depends on their priorities as a company: how do they value developer time vs lock-in vs complexity? Which contrary to your repeated personal attacks is the sort of conversation I have with corporate leaders: they determine the strategy; I make it work technically. But yes — there are clients who insist on avoiding those services (and generally would, if they’re migrating out of S3). And in this particular context, we were explicitly discussing the decision of how to migrate a product into the cloud where I advocated using the cloud solution but taking a small step which would both ease that transition and any future ones — and you flipped out. - - - - To address your dramatic nonsense: You don’t have to use Lambda to integrate with Salesforce; and you know that non-AWS call centers are used by most AWS customers. > Are you going to tell them not to use any of those either? Are you going to tell them not to use Salesforce? ServiceNow? Microsoft Office? This is just ridiculous dramatics completely unrelated to anything I said. - - - - Let’s ask a few questions to refocus: - why were you so insistent on my credentials, but won’t share yours? …are you embarrassed by your largest migration? - why can’t you address my specific example? …because it shows I have good advice and you spouted nonsense? - why are you melting down into unrelated dramatics? …or pretending I advocated against using cloud solutions? …or integrations at all? I think you’re just throwing up arguments at random because you can’t admit that on the original issue I was right.
  - scarface_74 3y ago
    You absolutely do have to use Lambda to integrate your call center with Salesforce. Your call center agents use their familiar Salesforce screen when a customer calls in. But you’re so concerned with “cloud lock in” and you completely ignore the other 200+ services that the average enterprise is using. Why are you so concerned with the cloud, but not Salesforce, ServiceNow, Sharepoint, Okta, Azure AD, etc? It makes no technical sense to spend developer time and add complexity to create an ETL job to do what a simple SQL statement can do. None of this is “making the beer taste better”. I’ve shared by credentials up thread - 2 years heading a migration and integration when a private equity owned health care company was acquiring companies to get big and go public, 3 years leading the application modernization effort for another company that was acquired at 10x revenue and three years working at AWS in the Professional Services department and now building out a professional services practice for an MSP for applications modernization. And before that over 20 years as a professional developer

scarface_74 3y ago

Scenario: I have $aLotOfData in S3 and I need to move it to a MySql database. Are you going to: A) write an ETL job that is going to be slower and more complex to avoid the “lock-inz” Or B) just call run “load data from S3…” As a sql extension? Are you going to tell them that they can’t use Glue? Athena? Redshift? Quicksite? When your company needs a call center are you going to tell them not to use Amazon Connect? Now they need to integrate the call center with Salesforce - are you going to tell them they can’t do that because they have to use Lambda? They want to have speech to text - now they need Amazon Lex. Then they want a reporting dashboard that comes from their contact trace records. Now they need Kinesis which is going to stream to S3. The typical company uses over 250 SaaS products that they have some form of integration with. Are you going to tell them not to use any of those either? Are you going to tell them not to use Salesforce? ServiceNow? Microsoft Office? If you work in the health care industry are you going to tell them not to use Epic?

zmgsabst 3y ago
That question depends on their priorities as a company: how do they value developer time vs lock-in vs complexity? Which contrary to your repeated personal attacks is the sort of conversation I have with corporate leaders: they determine the strategy; I make it work technically. But yes — there are clients who insist on avoiding those services (and generally would, if they’re migrating out of S3). And in this particular context, we were explicitly discussing the decision of how to migrate a product into the cloud where I advocated using the cloud solution but taking a small step which would both ease that transition and any future ones — and you flipped out. - - - - To address your dramatic nonsense: You don’t have to use Lambda to integrate with Salesforce; and you know that non-AWS call centers are used by most AWS customers. > Are you going to tell them not to use any of those either? Are you going to tell them not to use Salesforce? ServiceNow? Microsoft Office? This is just ridiculous dramatics completely unrelated to anything I said. - - - - Let’s ask a few questions to refocus: - why were you so insistent on my credentials, but won’t share yours? …are you embarrassed by your largest migration? - why can’t you address my specific example? …because it shows I have good advice and you spouted nonsense? - why are you melting down into unrelated dramatics? …or pretending I advocated against using cloud solutions? …or integrations at all? I think you’re just throwing up arguments at random because you can’t admit that on the original issue I was right.
- scarface_74 3y ago
  You absolutely do have to use Lambda to integrate your call center with Salesforce. Your call center agents use their familiar Salesforce screen when a customer calls in. But you’re so concerned with “cloud lock in” and you completely ignore the other 200+ services that the average enterprise is using. Why are you so concerned with the cloud, but not Salesforce, ServiceNow, Sharepoint, Okta, Azure AD, etc? It makes no technical sense to spend developer time and add complexity to create an ETL job to do what a simple SQL statement can do. None of this is “making the beer taste better”. I’ve shared by credentials up thread - 2 years heading a migration and integration when a private equity owned health care company was acquiring companies to get big and go public, 3 years leading the application modernization effort for another company that was acquired at 10x revenue and three years working at AWS in the Professional Services department and now building out a professional services practice for an MSP for applications modernization. And before that over 20 years as a professional developer