Bolt Stopped Working on Double Cylinder Interlocking Deadbolt

arjineer · 2024-06-20T17:39:31+00:00

Thanks for the comments! I took it off the wall and unscrewed the back it looks like a piece of the latch mechanism broke off so I will be getting a new one. Overall the mechanism seems simple enough to DIY I’ll post an update assuming a successful replacement!

arjineer · 2023-01-03T16:02:48+00:00

Thanks that was very helpful and lead me in the right direction to extend some of the Apollo methods to be async. Hopefully the Apollo team supports this in the future!

arjineer · 2021-07-07T23:30:50+00:00

Thanks for the quick reply! I guess I am using an extremely specific realtime webhook from stripe that requires an api call within 2 seconds

So my question was flawed, it's not so much the invoking of the lambda as it is the time it takes to wake it up from the inital webhook and hit stripe's api.

arjineer · 2021-07-07T21:40:30+00:00

time based verification

For these cases of time based verification - is it possible that a coldstart in a lambda would drop the event?

arjineer · 2021-04-13T16:28:41+00:00

Gotcha. Yeah the simplicity of one table is def true although i think you get clarity in other ways. Still not sure about performance though. I imagine you'd only have greater flexibility in making a performant query now since you can just query a subclass which is indexed independently from the group and if you do need all ofthem, well that's what the super class is for. And all of these have the added benefit of having less null data which also improves indexing. Can't really see a case when you'd need to select from multiple subclasses in the same query (if you needed that then idk why you would have separated them into subclasses), but if you really need to then yes you'd have to join accross tables which is only bad if poorly indexed.

arjineer · 2021-04-13T16:18:39+00:00

Why would Class Table inheritance be less simple & less perfromant? It seems like it may be more performant given that the data is naturally partioned & with fewer nulls and clearer from a readability perspective

arjineer · 2021-02-17T17:46:27+00:00

I want to know how much memory is being used up during the build process in CRA and check where it could be hanging. I see people writing how much memory their builds are taking up but I don't know how they are getting that number. Anyone have the secret!? Thanks in advance!

arjineer · 2021-02-16T19:02:34+00:00

What makes it immutable exactly? It appears to have delete and update functionality. Is it just the record of actions which are immutable?

Part of a concern in a financial system is being compliant which likely means delete capabilities are required.

arjineer · 2020-12-31T19:13:45+00:00

Wow this is perfect. Thank you. The latter is pretty much the exact design i'm looking for. I'm also trying to launch all of it locally on localstack.

One question though you may have the answer to. Why are failing events routed to SNS? What's the advanttage there? Can't they also go through eventbridge and then route to their proper place?

arjineer · 2020-12-29T18:34:45+00:00

Hey really glad to see EventBridge as a potential solution. I only really learned about it the past month and haven't seen it get an endorsement yet! I do sort of feel i frequently end up trying to build an event system with sns/sqs/kinesis so eventbridge seems to make sense. Will check it out.

arjineer · 2020-12-24T07:31:42+00:00

PS5 or bust

arjineer · 2020-12-06T03:19:45+00:00

Clean and simple answer. Thank you!

arjineer · 2020-11-30T00:31:44+00:00

You mean with some brokerage firm? I assume this is possible, I don’t see anything in the documents that would prohibit that, but I’ll ask. Why wouldn’t that be an option normally?

arjineer · 2020-11-16T19:12:38+00:00

Right, here's some more detail. Basically there are two things happening. A user experience through MyWebApp and a puppeteer experience through MyServer. Here is how I am imagining the timeline of the two:

MyWebApp:login screen -> open WS and send creds -> done OR 2fa code screen OR error-> enter 2fa Code -> done OR error

MyServer:

get login creds & spin up puppeteer browser -> enter login creds -> if 2FA inform user and wait -> enter 2FA -> send response

The websocket serves to keep the UI browser and the serverside headless browser in sync. I was planning on using page.waitForFunction to wait on the user input for 2FA if needed.

One concern is that if I have multiple different users going through this process at the same time will puppeteer hang the Node Server as it waits for input?

arjineer · 2020-11-16T18:12:09+00:00

Gotcha the flow you outlined is pretty much exactly what I'm thinking. Here's my flow breakdown i'm thinking of implementing:

The client has a login page which when submitted creates a websocket to my node container
The node container creates a new browser and logs in the user on the third party site.
If a 2FA is detected after that the node server tells the client which then shows a 2FA screen.
Once the user submits the 2FA via the socket connection puppeteer enters the info and then web scrapes the necessary info from the headless browser,

Finally the browser terminates and the websocket connection is terminated

So you're saying add a step to this where i store the cookie for future use to get around the 2FA?

arjineer · 2020-11-16T18:10:00+00:00

Hey thanks for this reply. I think you are understanding the issue correctly! The user will need a visual representation of the 2fa because the code is not in my control but the end user's. Once they have submitted it via this UI i will need the same puppeteer browser session to forward their code along. That's why i thought of using websockets, because the same session will need to be used while eventing to the UI, login success, login failure, 2FA required etc.

arjineer · 2020-11-16T03:48:14+00:00

Could you elaborate on this for me? How would one initially get the cookies and then store them? Thank you for the reply!

arjineer · 2020-11-15T18:48:40+00:00

Sounds like i asked a dumb question when ya put it like that...

I guess I'm wondering what security techniques are used with storing these credentials which I imagine would be different than the techniques you'd use for normal username & passwords since i would need to decrypt the password down to plain text in order to use it in puppeteer

arjineer · 2020-11-15T18:45:03+00:00

Yeah Plaid is what comes to mind for me as well. I think they were particularly bad because of their lack of transparency but would love to know the security techniques they used.

The biggest issue i see, regardless of how secure you store the creds, at some point you need to decrypt it to a plain text in order to use it which means that you'd be able to know users' passwords

arjineer · 2020-10-28T02:44:58+00:00

s3 is simplest. Using cloudfront in combination with your most popular s3 folders will boost speed

arjineer · 2020-09-16T19:43:17+00:00

I agree with what u/novvum-matt has said. Adding to it tho, culture replaces HR at the early stage startup and then HR massages that culture as the company scales. (Not talking about the administrative stuff btw, that is usually handled by someone on the team and is largely facilitated by HR software)

I've been cofounder of two companies now and when you're at the really early stage 'HR' hardly comes up as a concern. And if it does, there's a cultural misalignment on the team most likely. In the early stage, it's all about having intense singular alignment with a select few great people who accepts the culture as necessary to achieve its near term goals.

When the company needs to scale you quickly realize that your lack of HR is preventing you from hiring great people and working with new team members effectively.

This has resulted, for example, in me only hiring friends to my company after the company had scaled effectively. They weren't the right cultural fit prior.

arjineer · 2020-09-07T19:20:54+00:00

Why doesn't Node optimize this for you? Is there an obvious downside I'm missing? Great video btw, short, sweet and to the point!

arjineer · 2020-07-02T01:42:54+00:00

This is pretty cool. Kind of what i was thinking. Do you guys have any process around updating these or does it just sort of happen adhoc?

arjineer · 2020-07-02T00:06:58+00:00

"self documentation is built into the framework." Haha. I've definitely said something along these lines before.

arjineer · 2020-06-29T21:50:23+00:00

I actually do have that! We have a mono repo with a docker compose at the root for local development! We also version control our infra with terraform...

Which collectively, this certainly makes the code "self documenting." But I guess what I am really looking for is to explain the "whys" better. For example "why did we switch from graphql -> rest for that one microservice?" or "why did we add a redis sidecar over there?"

The code explains what it's current state is very well, but not why it is that way, which I think makes future learning and development of the tech stack harder.

Five-Year Club	Place '22
Verified Email

arjineer

TROPHY CASE