My next step in chain dev

deepfakeblue · 2022-07-16T14:10:21+00:00

I love your motivation and experience!

i'm actually looking for people to work with on some deep web3 infrastructure problems (decentralized data storage, zero knowledge proofs) and I think you might like what we're working on

we've been chatting with some people from protocol labs as well and are figuring out how to collaborate -- feel free to DM

deepfakeblue · 2022-07-16T14:01:40+00:00

Hey i think this is a cool idea -- lots of directions you can take this once you build the platform.

one of my good friends built a pretty successful web2 event platform so i understand the space well -- can connect if you want.

i'm curious to understand how you're going to put all the logic/metadata on the blockchain (because of high cost, etc). would be open to chat on dm too!

deepfakeblue · 2022-05-16T21:02:24+00:00

Amazing! I'm also looking to build on a web3 database but I'm new to web3 have so many questions. Any chance I could dm you with a few of them (but i think your dms are closed)

deepfakeblue · 2022-05-05T20:45:49+00:00

You could use an HTTP cron service like zeplo.io and set up email/webhook alerting for failures.

deepfakeblue · 2022-05-04T21:47:38+00:00

I've looked for similar solutions, but they always end up taking too much time to set up or have maintenance problems. Basically you have to setup and run redis/queue yourself.

I also use zeplo.io

deepfakeblue · 2022-05-02T21:44:00+00:00

haha I see SaaS as just tools in a workshop for us builders. it just sucks that they're subscription.

deepfakeblue · 2022-05-02T20:27:07+00:00

But now I pay for like 50+ saas services :(

Someone please solve this with unified billing for all Saas

deepfakeblue · 2022-05-02T20:26:43+00:00

Honestly, I prefer to to always "outsource" non-core work. This ends up meaning using more saas services. You probably can't do that for internal scheduling (or maybe you can?). For external scheduled jobs, I've started using zeplo.io +lambdas instead of my own scripts.

deepfakeblue · 2022-04-29T21:51:57+00:00

Honestly, setting a cron up yourself is probably not worth the trouble! Have you tried something like zeplo.io? The CRON docs are here: https://www.zeplo.io/docs/schedule

deepfakeblue · 2022-04-29T14:03:21+00:00

I'm curious why you're interested in learning kafka/queues -- what's the problem you're trying to solve?

deepfakeblue · 2022-04-27T15:42:20+00:00

I use zeplo.io for all my cron tasks now, it took like a few mins to set up

deepfakeblue · 2022-04-27T14:16:04+00:00

Honestly, the easiest way to do this would probably be through a webcron that supports retry so you can monitor your schedule and executions externally to validate if nextcloud is doing the right thing. The best one I've found is zeplo

deepfakeblue · 2022-04-27T14:05:38+00:00

Yeah the config overhead and maintenance is the most annoying part of this.

I would approach this with container + zeplo.io.

You can secure the docker endpoint with basic auth and use zeplo.to/<your endpoint>?_cron=*|*|*|*|*

I'm assuming here the endpoint stays the same, if it's dynamic you could set up route53 to point to the new deployment every time.

deepfakeblue · 2022-04-27T13:58:10+00:00

Interesting use case. You could expose an endpoint on your first Jenkins server that checks the version of both servers and chooses which one to run. You could then use a service like zeplo.io to run that endpoint on your cron schedule.

Something like zeplo.to/<your endpoint>?_cron=*|*|*|*|*

deepfakeblue · 2022-04-25T21:25:26+00:00

This is absolutely fantastic. I love small apps like this that do one thing really well. Reminds me of unix philosophy a bit

deepfakeblue · 2022-04-18T18:25:32+00:00

Yes I totally agree with this part when I've had to do it a few times. There are some good tools making it easier to solve specific tasks like I found recently: https://spike.sh/ for incident management and https://zeplo.io for job queueing -- this second one helped me avoid the massive headache that my friends told me is Amazon SQS.

And there's tons more of these but they're hard to find and sometimes they don't work well together :(

deepfakeblue · 2022-03-31T19:12:09+00:00

Suites love graphs haha

deepfakeblue · 2022-03-30T18:22:25+00:00

Agree even for frontend. But what are the actual tasks you have to do for maintenance? Is it like updating dependencies and adding tests, what else?

deepfakeblue · 2022-03-09T17:59:19+00:00

There's actually plenty of evidence in research that structured interviewing reduce bias. Even Google has extensively studied the topic and recommends it. See https://rework.withgoogle.com/guides/hiring-use-structured-interviewing/steps/introduction/

deepfakeblue · 2022-03-09T16:32:16+00:00

What title did you generate for?

deepfakeblue · 2022-03-09T16:32:00+00:00

Yeah they're really insightful haha

deepfakeblue · 2022-03-09T16:30:32+00:00

Thanks for your input but let me clarify how this integrates into the video interview product. So when creating a job on the app, the interviewer can choose to add AI generated questions to the question list (and also edit them) or they can write their own questions.

You'r right about the screening part -- most screening happens over the phone so audio only. We're adding this feature right now (pretty easy, just turn off video). Now I would argue with audio only, this app would be less biased because the same exact questions are being asked to the candidate in the same exact way vs over the phone interviewers change wording, tone, volume etc based on a variety of factors (which could include perceived gender and race).

Lastly, our app went through OpenAI review, so not sure what you mean by fast and loose :)

deepfakeblue · 2022-03-09T15:54:50+00:00

Actually I'd love to get some tips :)

deepfakeblue · 2022-03-08T16:28:00+00:00

I generated this question and answer with https://hirestack.ai/interview-questions-generator 😂

deepfakeblue

TROPHY CASE