HN user
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.
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.
In Java, Lombok @Slf4j on a class is very convenient. Adds a static field for the logger.
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.
In the US, Verizon offers (sometimes includes for free) a battery backup unit for their ONT for FiOS service, in the name of providing only the phone services during a power outage. In general there’s nothing stopping any customer from using an off the shelf UPS.
Anecdotally, CBTC is a greeat improvement in many scenarios. On long and straight stretches between express stops, trains now fly along (probably at least 40mph; never got to see inside the TO’s cab). And upon approaching an occupied station, they slow down to a crawl but keep moving until about 25-50 feet before the station, instead of being stuck several fixed blocks back before the station. Thus there is much greater track capacity = more (potential) trains per hour, and generally more reliable trips.
We can argue about exact implementation, but SRE demanding all apps (assuming non-interactive ones run on servers) log to the same channel (with enough tagging info to ID the app/server) is a good thing. In my case we are automagically configured with a Splunk appender for Logback (and the platform also sends the stdout/stderr to Splunk under a different sourceType).
I’ve never used Jaspersoft, only seen the marketing pages of recent years on Tibco’s site. But much of that developer experience sounds like my 4-ish years with BIRT: differing versions of the designer GUI in Eclipse breaking things; debugging a report required starting up our entire monolith app.
How much better is SSRS in these aspects than the aforementioned Java-based solutions? Or I guess “paginated reports” in Power BI nowadays.
This token based approach is slowly arriving. Don’t know if Plaid does it yet. Yodlee and Intuit have already implemented it (OAuth and FDX) with at least and handful of banks.
https://www.yodlee.com/envestnet-yodlee-and-charles-schwab-e... https://developer.yodlee.com/resources/news/yodlee-and-jpmor... https://media.chase.com/news/chase-intuit-to-give-customers-...
Now they make you manage the very limited subset of router options (essentially SSID and WPA passphrase) from their web portals. Then they push the updated configs to your router via remote management protocols. How many vulnerabilities do those open?
If it’s a reasonable company, they will be willing to move your start date upon (polite) request, justified by the delay. In my recent job change, there were a couple of things that moved the timelines (only a couple of weeks, not months like your case), and the recruiter adjusted my start date like it was SOP.
Re resigning: make sure you have some concrete evidence of passing all contingencies in the hiring process (even go so as to ask the recruiter if any steps remain). Only after that, give your notice.
Ah, iDEN has gone the way of floppy disks. My old Moto i955 for Boost Mobile (MVNO of Nextel, later carried along with Sprint on CDMA) is a quite heavy and rocky solid paperweight.
In the world I live in (big org using Jira), that sounds like an epic, with lots of stories underneath. Some stories are defined early on, more can be added as the business comes up with new reqs or devs find things that need more work.
It’s been a self-hosted products for over a decade in the form of Visual SourceSafe and then TFS (wonky TFVC not withstanding; Git support was added a while ago as well), now living on as Azure DevOps Server.
A white collar worker in good shape going from, say, Rego Park to Wall St is a great candidate for the subway. But that’s the happy path. If you need to go from there to the far parts of Brooklyn, or any part of the Bronx or Staten Island? Virtually impossible (if you want to get to work before lunch time) without a car. And certainly many with disabilities would have a hard time (as much as the MTA is improving on this front).
The US has the social security program, to which both employer and employee make mandatory payroll contributions, but it pays very modestly in retirement. Many employees now contribute to their own self-managed retirement savings/investments. Employer sponsored pensions are disappearing.
Among other things that have been incompatible for a while: - many system tables use the Aria engine; has been impossible to start a MariaDB server over a data directory created in MySQL for many versions - mysql.user table has some completely different columns and authentication plugins diverged greatly as of MySQL 8.0, ie no caching_sha2_password (makes writing a user migration script challenging) - Even the data dir initialization scripts/programs are very far removed
You would be right to expect the DB library to escape the string so that no SQL injection is possible.
SQL in some (hopefully good number of) cases is much safer than that. Going with MySQL prepared statements here: parameters are not sustituted into the SQL statement string, but rather sent as seperate data packets in the wire protocol.
Now add a date/time stamp. And thread name, current class/method, request trace ID, severity level, etc., to every log line in your app. Or just grab your favorite logging lib from Maven Central and call it a day.
I worked for a (small boutique) consulting firm and the much larger telecom company they placed me at required a drug test. The culture in my group there did happen to suck, bad enough that my form pulled let me come off the client after just a month.
JHipster (https://www.jhipster.tech/) goes a bit beyond that. From my reading, its basic functionality is taking in either interactive command line inputs or theor custom DSL, and spitting out DDL for a MySQL DB, Spring Boot backend, and Angular frontend.
I worked on a Pega project once. There was nothing in there that the business people would be able to touch, especially after the requirements exceeded the capabilities of Pega’s primitives. One of the local friendly FTEs (the dev work was contracted out) would’ve been happy to use C#/ASP.Net web forms like everything else in the org.
Aliases are pretty much mandatory if you need to join the same table twice; otherwise you have no way to disambiguate column references. I understand the case of auto-gen’ed queries. However, in page long queries that I’ve written by hand, short aliases (typically the acronym of the table name, sometimes with a one-letter suffix if the table is joined multiple times) make the whole query flow like a nice story.
How do you trust that the devices are allowed to pull down the private key?