Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
zupo
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
Devenv 2.1: Nix with zsh, fish, and nushell via libghostty
(devenv.sh)
3 points
by
zupo
5mo ago
|
2 comments
2.
▲
by
zupo
8mo ago
"The capability based approach is interesting, but trusting developers to declare all their needed capabilities seems brittle. Modern OS level sandboxing or containerisation provides strong isolation without relying on each library to
3.
▲
by
zupo
10mo ago
This is a good reminder that ‘AI pair programmers’ can create subtle bugs that are hard to spot.
4.
▲
by
zupo
10mo ago
Fascinating vulnerability. It shows how browser integrations can create unexpected attack surfaces. I’d love to see more discussion around hardening these kinds of local browser modules.
5.
▲
Ephemeral Win11 testing VM for a few bucks per month
(paretosecurity.com)
2 points
by
zupo
1y ago
|
0 comments
6.
▲
Automating Distro Updates in CI
(paretosecurity.com)
18 points
by
zupo
1y ago
|
6 comments
7.
▲
No Moar Cookies
(paretosecurity.com)
2 points
by
zupo
1y ago
|
1 comments
8.
▲
by
zupo
3y ago
IIUC Magic Nix Cache uses Github Actions Cache, which means there is waiting for the cache contents to be loaded onto the runner instance. This can in no way be as fast as what namespace.so does, which is mounting a disk image with /ni
9.
▲
by
zupo
3y ago
What worked great for me for speeding up CI was using Cachix + namespace.so. This works so well I moved all my personal and our company CI to GitHub Actions. With "it works so well", I mean: * CI is cheap because namespace.so runn
10.
▲
Tesh – TEstable SHell Sessions in Markdown
(blueracer.io)
2 points
by
zupo
4y ago
|
0 comments
11.
▲
by
zupo
4y ago
I've seen the following multiple times in the past: 1. something changed in test layer setup that made all tests slower 2. something changed in application code that made all tests slower (!!) And most of the times, they were avoidable
12.
▲
by
zupo
4y ago
Not quite 2019 levels, but here they have mostly rebounded.
13.
▲
Block Pull Requests that made tests slower
(github.com)
5 points
by
zupo
4y ago
|
5 comments
14.
▲
by
zupo
4y ago
Unit tests tend to get slower with time, wasting a lot of developer hours. BlueRacer helps you keep them fast by posting a unit test performance summary on every Pull Request.
15.
▲
A checklist to speed up your pytest suite
(github.com)
3 points
by
zupo
4y ago
|
0 comments
16.
▲
by
zupo
4y ago
That's great feedback, thanks!
17.
▲
by
zupo
4y ago
Which is exactly what the device on the link does. It's using a real SIM card to receive 2FA codes and then forwards it to wherever you configure it to.
18.
▲
by
zupo
4y ago
Slack is mostly used as a placeholder in the name. It's trivial to change the code to send the webhook anywhere: https://github.com/teamniteo/sms2slack/blob/master/src/esp32...
19.
▲
ESP32 device to forward SMS 2FA codes to Zapier, Slack, etc.
(github.com)
1 points
by
zupo
4y ago
|
0 comments
20.
▲
Forward SMS 2FA Codes to Slack
(sms2slack.com)
3 points
by
zupo
4y ago
|
6 comments
21.
▲
by
zupo
4y ago
Yep, completely agree. We had a project before when it "clicked" and we could tell.
22.
▲
by
zupo
4y ago
Additionally, there is a huge difference in getting free users and getting paid users. We tried with a very low-price plan and got a lot of interest & signups. The moment we raised the prices a bit to cover hosting costs, the interest w
23.
▲
by
zupo
4y ago
The trick is in knowing where to draw the line. We definitely felt we had "some" tracking. We had hundreds of people sign up to our newsletter. We had a couple of users that absolutely raved about the product (or as it turned out
24.
▲
by
zupo
4y ago
It's "zero trust". I.e. no-one from Pareto Security, nor anyone from your company can access or track any of your Macs. The only thing that the local agent running on a Mac does, is sending a list of failing checks every now
25.
▲
We spent $980k on a failed SaaS project
(niteo.co)
75 points
by
zupo
4y ago
|
17 comments
26.
▲
by
zupo
4y ago
OP's coworker here, thanks for taking the time for writing this, I'm definitely cheering for us to give Render another try!
27.
▲
by
zupo
5y ago
As much as I hate to say it as a developer: code is trivial. Finding users is the hard part. Additionally, our long-term vision is to make the bulk of revenue from Teams subscriptions, where most value comes from a web-based dashboard ( htt
28.
▲
by
zupo
5y ago
TL;DR: Quick & easy process, do it. Minor part of revenue on long term, though. They reached out to us. We integrated their SDK (trivial), provided sales copy and screenshot, then waited about two weeks for the review. For the first few
29.
▲
by
zupo
5y ago
I'll report back in a year or three if it does in fact work in real life hehe
30.
▲
by
zupo
5y ago
Thanks! And it's open source: https://github.com/paretoSecurity/pareto-mac/
More ›