But it happens to be that product managers know (or at least about) and keep tabs on the relavent regulatory environment. I think it’s not scalable if every SWE in the team is going to legal to understand things. Like why we actully do need to hard delete data when customers click the Delete button.
If you force every SWE to go to legal for every technical decision, or ask for permission, it's not scalable, yes. On the other hand, if the team is in the long haul of developing this kind of regulated applications, the knowledge will get accumulated over time, and it'll trickle down from product managers to seniors to juniors.
This is the kind of tribal knowledge you want to spread among a development team, and if a collaborative document of "Why it's done this way" can be propped up with pointers to relevant sections of the regulation, it'd be a very good thing.
The value prop of Plaid, Yodlee, et al is that they can do this with one(-ish) API surface for tens of thousands of financial institutions. In their efforts to ensure Bob down the street won’t be sold any data, they do treat each customer (of the API, not the end users they pull data on behalf of) as an isolated tenant.
Great in concept, especially if you know what you’re doing. In my non-North American locale, I ordered a fiber hookup, and specifically asked to use my own router.
Supposedly they will give you an ONT in SFP module for free, and then rent you a media converter ~3 USD/month, and then the rest is up to you (assuming it supports PPPoE). Some friends have done this a while ago successfully.
Reality on install day: technician grabbed the white-label ONT/router combo from the truck and refused anything else :( And unrelated, he found a “defect” in the existing fiber drop (clear as day with the visible-light tester), so I had to pay for pulling a new drop from the street :(
Where I live, CS is all chat bots that are simply text representations of the phone tree. You can Whatsapp the company! And get the nicely formatted menus.
Anecdotes from my experience, in a large US bank (millions of customers), specifically in a product with active investment:
Yes, processes for getting things done are dull and frustrating. Team leads often urged minimizing time spent on them by using political clout with the gatekeepers to expedite them.
Tech was not too exciting, all the open source stuff used were mature, vetted by security folks/scans, and possibly had in-house layers built on top of it.
Did get to see where my projects fit in end to end, including contributing to data shown in a widget high up on their mobile app’s dashbord, and also to several thousand internal users who are movers and shakers.
Standing up a new REST API and exposing it to the internet required much upfront design and lots of approvals. But at the end of the day it’s to ensure minimal risk while making maximum impact on the tremendous customer base.
Pay was not approaching the FAANG stratosphere. Had two WFH days per week. Office had a section of a floor reserved for the group, and hotdesking with “soft” reservations based on history of actual desks used.
Overall did learn a lot about tech, business, and leadership, but the cog feeling was still definitely an undertone.
Also at a very big BigCo using Citrix Workspaces; experience is decent. Got an 8 core/64 GB RAM VM and it’s pretty snappy for most dev work. The portability is nice compared to lugging a work laptop, and connection doesn’t need a janky VPN client. Using Zoom for VDI with the VDI plugin on my home machine is even smoother than same thing on the thin client in the office.
How do you get the $1 price for kids in 2023? Currently the rule is “Up to three children under 44 inches tall ride for free when they’re with a fare-paying adult.” https://new.mta.info/fares
It’s great to write carefree SQL, with the DB platform totally abstracted, until there’s a massive spike in query latency. Then hash joins vs nested loops and full table scans is useful knowledge which is a) mostly vendor specific b) requires a good prod-sized dataset to test on.
Then there’s the times people update the bug-tracker-table-in-a-Confluence-page, and Confluence sends an email alert about the edit to those “watching the page (which is everyone who ever edited it). In Outlook the scroll bar literally shrinks before my eyes as it renders the email from top to bottom.
