3,627 karma · joined April 11, 2011
My most recent projects: - vaultaire.app - iOS vault for photos, videos, and files. Pattern-unlocked AES-256-GCM encryption. No account, zero-knowledge. Even we can't see in. - pdfpix.com - Set of PDF tools operating strictly in the browser. No accounts, no limits, no risk of loss. - gethasp.com - Local secret manager for AI coding agents. Hands encrypted credentials to a process for a short window, then takes them back. The values never leak.
Presenting it as such does disservice to any serious conversation.
I added it after users asked me to solve their problem of being strip searched like this.
I know some people keep crypto wallet keys in the vaults. Someone else wrote me that they carry sensitive documents they don’t want to be exposed.
When I was designing my secure vault app for iOS[0], my approach was to make one of the “folders” (I call them vaults), to trigger the wipe out without any sign of doing so while retaining the data in the opened vault. It technically only deletes the index and the keys, and obfuscates them by replacing them with random bytes.
I already heard from a person that was forced to open their app but was let go, because they complied.
I am not even going to pretend that this is financially reasonable option. I simply wanted to have a local models. Maybe down the line, as cloud models become less subsidized, I might benefit from having a local setup, but for now, it wasn't the most prudent financial decision.
But one big benefit is that I never have worry about my account being randomly banned nor I have to worry about running out of quota. I still use codex and opus for some specific tasks, but as tools are improving, I need them less and less.
Frontier users: 527,865 Light indexed: 527,865 Ready to queue: 9,083 Fast scores ready: 0 Activity events 24h: 30,266 Fast scores completed 24h: 19,123 Deep jobs completed 24h: 3,043 Fast-score ETA: n/a Deep-hydrate ETA: 69h Stale running jobs: 0 GitHub backpressure jobs: 19,113 High automation signals: 4,608 Medium automation signals: 1,327 Completed jobs: 74,714
Biggest challenge is Github's rate limits. At this pace it will take two more months to have 98% coverage. But after that the maintenance should be quite straight forward.
I remember how website security was before frameworks like Django and ROR added default security features. I think we will see something similar with coding agents, that just will run skills/checks/mcps/... that focus have performance, security, resource management, ... built in.
I have done this myself. For all apps I build I have linters, static code analyzers, etc running at the end of each session. It's cheapest default in a very strict mode. Cleans up most of the obvious stuff almost for free.
Pex is a digital rights technology company, enabling the fair and transparent use of copyrighted content at the speed and scale of the Internet. We serve everyone who uses the Internet to view, share or create content – from the largest platforms and rightsholders, to independent creators. Our advanced licensing infrastructure allows platforms to manage and license content before it’s published, empowering creators to upload freely while respecting copyright. In return, rightsholders are able to monitor and capitalize on the content they own.
We are hiring for Senior Reverse Engineer/Senior Data Harvesting Engineer (Europe) to help us bring our services to the masses! Reach out to jobs@pex.com.
We offer:
- salary: $103,000 – $110,000 USD per annum
- equity, with a 10-year exercise window
- 30 days of paid time off + 9 local holidays + the day off on your birthday
- generous paid parental leave
- a fully remote work environment, supportive culture, and excellent work-life balance
To learn more about our hiring and culture, take a look in our blog posts titled: - Interviewing at Pex? Here's what you can expect during our hiring process [1]
- Pex culture: Focusing on what really matters [2]
[1] https://pex.com/blog/interviewing-at-pex-heres-what-you-can-expect-hiring-process/
[2] https://pex.com/blog/pex-culture-focusing-on-what-really-matters/[0] https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3221625
Modus is a continuous workforce management platform that makes headcount planning and reconciliation easy. The platform analyzes thousands of bits of data across the organization to help leaders optimize their workforce and increase forecast accuracy. With the help of AI, Modus synthesizes insights from HRIS, ATS, expense and finance systems so leaders can visualize and execute workforce plans, grow efficiently and compliantly, and unlock high performing teams in one unified workflow.
While we are just at the beginning, both founders have extensive experience in the industry. One of the co-founders was early Google engineer and built multiple companies in the past, writing significant amount of code at each company. The other cofounder has scaled from 100 to 2500+, through to IPO and beyond. Joining as our first engineer and designer means you have will have an outsized influence on the tech and design choices.
We are currently only looking for very senior colleagues to help us move much faster:
- Staff level frontend engineer - At least 5 years of staff level frontend development experience with Svelte, React, Next.js, Vue (strong preference for Svelte)
- Principal Product Designer - Preferably designer with strong rapid prototyping skills, 10+ years of experience with designing B2B software, especially complex dashboards with a lots of data (strong preference for either Fintech or HR tech experience)
All candidates must be physically located in the US. No exceptions. Bonus for being located in CA and even better, San Diego.Interview process: phone call, interview with each founder separately, reference checks, and offer (can be done in less than a week).
If interested, please reach out to hire@himodus.com.
BTW kudos on zanzibar. Love the tech and the code).
But ultimately we are using SQL, queue, concurrency, single tenancy and monolith (few to none micro services).
Unfortunately, majority of candidates are interested in the take home challenge over doing live coding session. And we optimize for the widest reach.
In regards of the results, I can't speak for others, but I write code for 26 years. What I look for is how the candidate thinks of the problem. Here is one of my favorite exercises [0]. I would obviously love to do this live but people get super nervous and stop thinking. I then have tendency to help them too much and learn much about them.
Imagine a file with endless list of URLs. For each URL check if it contains an image. If it does, identify the top 6 colors and store it memory so it can be printed/stored later.
In something like python this can be as short as 20 lines of code: - open the file - read line by line - validate if the URL is valid - call the URL - check if it's image - if image, read pixel by pixel and check the color - store it in dictionary/hashmap
Here is what I look for: - does it compile/work? - what language did you choose? (like python is fast to write this in few lines but hard to introduce concurrency) - have you introduced some kind of caching for the URLs? (so you don't waste resources) - are you checking if the URL is valid or you just run them all and wait for errors/timeouts? - are you checking the file type from HTTP header or body of the file? - how do you handle errors? - are you attempting concurrency? If yes, how?
I actually done this exercise myself in dozen or so languages to see what choices I make based on the language. Obviously one can spend significantly more time on it if they really desire, but the design choices are visible from the beginning.
I am not sure about other firms, but we personally look for how the candidate thinks about the problem more than anything. Did they handle exceptions well. Are they focusing on efficiency, readability, speed, or?
We found out that from a simple assignment that shouldn't take more than 30 min, we learn more than sitting with the person for hours. Plus they can do at their own pace without someone breathing down on their neck.
Modus is a continuous workforce compliance and planning platform that enables various employees throughout the organization to stay compliant with labor laws, visualize and execute workforce plans, and make data-driven decisions to ensure fairness and equity. You can think of us as Vanta for HR. Our mission is integrity. We've all been through the pains of levels, benchmarks, compensation inequities. Why can't HR tech be intuitive, easy to use, and encompass workflows for everyone in the org?
While we are just at the beginning, both founders have an extensive experience in the industry. One of the co-founders was early Google engineer and built multiple companies in the past, writing significant amount of code at each company. Joining early means you have a significant say into tech and design choices.
We are looking for curious and motivated colleagues to turn our vision into a reality. All positions are 100% remote with no on-site requirements of any kind. We are currently looking for:
- Javascript/frontend developers
- Designers
- Backend developers
Interview process: phone call, "take-home" exercise, interview with each founder separately, reference checks, and offer (can be done in less than a week)If interested, please reach out to hire@himodus.com
I have the opposite experience with Mastercard. Of the dozen or so disputes across 5 cards I had over the years I essentially lost them all. Visa is somewhere in the middle. They tend to side with customer but also will investigate thoroughly.
[0] https://www.hcii.cmu.edu/news/software-defined-cooking-using...