I still consider Asheville home although I've been in Austin for 15 years now. I would move back in a heartbeat (provided I could convince my wife). Luckily, family is still there, so I get to visit regularly.
Distributed team of 3 engineers with over 40 years of combined experience that have worked together for 6 years. Our current contract is winding down. Open to Contract or maybe FT.
Location: Austin, TX / Dublin, Ireland
Remote: Yes
Willing to relocate: No
Technologies: Java, JavaScript, Kotlin, AWS (you name it), Kafka, Elasticsearch, Druid, Snowflake, Recommender Systems, Ad Tech
There are some more friendly options than Google Authenticator if it's a hassle to keep setting up over and over.
I keep my 2FA in 1Password, and it works pretty well. I can access the codes from the desktop app without getting out my phone, or from my phone or tablet if I'm mobile.
The only scary issue is that all that information is encrypted in Dropbox. And I use 2FA on Dropbox! Hello cyclic dependencies! As a result, Dropbox is the only 2FA that I don't store in 1Password.
SMITH: Ashley tried to get another job in banking, but she found that she never made it very far past the initial interviews. She suspected that Wells Fargo had put some sort of black mark on her record somewhere. And it turns out that is exactly the case. Wells Fargo wasn't joking around when they said they would make it hard for her to find work again.
ARNOLD: No. Wells Fargo wrote her up on what's called a U5 document. It's like a report card for bankers basically. We tracked it down, and we asked Ashley to read what it said.
ASHLEY: Failure to perform job duties.
SMITH: Any bank - any bank that Ashley applies to will see this line, failed to do job duties.
ARNOLD: The form does not mention that those job duties were the sales goals that everyone we spoke to said were unrealistic and that are at the center of a series of ongoing investigations at the state and federal level.
SMITH: It just says failed to do job duties. It was the first time Ashley had seen it in print.
ASHLEY: It's like having a black cloud that's kind of looming behind you. And I'm always trying to get in front of the cloud, out of the cloud, into the sunshine, but it's always there.
Have to agree here. The article's use of Optional is well intentioned, but shows use of the construct in a way that it was not intended. It should be used minimally, and only as a return value to signify the absence of a value. When you notice that Optional is not serializable, this starts to sink in.
Apache Tapestry has a library called Plastic that serves the same purpose and is also built on top of ASM. Plastic helps Tapestry handle a lot of the boilerplate and ceremony with common Java patterns (decorators, chains, handler pipelines, etc), and can be used as an independent library.
I'm interested in what and how quick the development/testing cycle is. How quickly can you spin up, populate, and destroy a test instance for integration testing? How do you iterate on feature development against it?
Any best practices or gotchas about query authoring in comparison to a typical relational database? What part of the traditional relational db mentality needs to be changed or thrown out as I write queries. For example, should I avoid using this aggregate function or that join in a way I'm familiar with in the context of something like Postgres.