HN user

nerdwaller

443 karma
Posts0
Comments274
View on HN
No posts found.

Volta Circuit | Senior Front End Engineer | Remote (US) | https://voltacircuit.com

At Volta Circuit, we specialize in developing secure and innovative smart contracts that empower users to take full control of their digital assets through enhanced self-custody solutions. We believe in providing companies with the tools and technology they need to manage access to their digital wealth with confidence and autonomy through multisig and an advanced rules engine to delegate access.

We are seeking a talented and passionate React developer with experience in decentralized applications (dApps) to join our small team. As the primary front end developer, you will play a crucial role in owning and guiding our front end architecture, ensuring that our users have a seamless and secure experience when interacting with our platform and smart contracts. Your expertise in dApp development will be invaluable in creating a user-friendly and intuitive interface that empowers users to take full control of their digital assets.

We are looking for a self-sufficient individual with excellent communication skills who can work as a self manager and as part of a team. dAPP and full stack experience, specifically with Golang and Postgresql, are a bonus as we all work across the stack (React, Golang, Postgesql, EVM, Cosmos).

If you’re interested in learning more, email us at hireme [at] voltacircuit.com.

Just wait until their home banks interrogate them about how they want to spend their local currency they wish to withdraw or banks shut off withdrawals entirely due to systemic issues.

Bitcoin may not be the end all solution, but it's a great current option.

The types of secrets ought to be a bit different and less consequential on a developer's machine. If they're not, that's a pretty big red flag. It's one thing to gain access to clone some repositories (e.g. ~/.ssh) but an entirely different thing to get production aws credentials. Not to mention all the other protections that should be in place that mitigate the fallout (for example: no pushes to main/master/prod branches, requiring status checks and reviews before merges, etc).

The issue isn't when you get what you're wanting. The issue is when either you accidentally get something you didn't want (such as type-o squatting - a not too distant issue on PyPi) or a package was published maliciously (imagine bumping a patch version and it being compromised) - a few fairly recent issues on npm.

I agree that the happy path is ideal and hopefully the common case. Regardless, anything with access to production secrets for my team is run on the most minimal image possible (and none of those secrets are available during dependency installation and compilation).

Some packaging ecosystems are more risky than others, primarily because they allow running arbitrary code at some point during the install cycle. Node and Python being two notable ones, especially considering how commonly they are used[1]. Others do it more safely where, at a minimum, no code can run until the library is imported and run with application code.

Depending on how and where you deploy, you can mitigate some of that by isolating the installs and not keeping sensitive information there (e.g. in a docker image).

[1] - I don't follow node/npm closely anymore, so this may have changed.

Campfire 2 years ago

They did a live stream this morning and said they've already crossed the six figure mark on the initial private/soft launch. I was pretty surprised by that, as similarly I questioned the market.

Agreed, this has been a really fun experience to follow. I know these last couple will continue to be engaging, but I hope there's something else in the future from the author!

I find that I really appreciate the explicit rather than the implicit comparisons (requiring `===` in js), especially picking up a new program or coming back to one after some time away. I view it like a database - do I really want multiple ways to show a value is empty? For something like a Boolean you have: `false`, `true` and `null` as valid values (trilean?) that now have to be handled.

I wasn't aware that Prusa is floundering and wouldn't have minded a little more development there. However it wouldn't surprise me as when I was shopping for my latest 3d printer replacement it was too easy to choose something else. For the price of the Mk4 most of the market is within the same budget (many options arguably better and more capable).

This post is the Armin Ronacher take that the author here is talking about: https://news.ycombinator.com/item?id=38768997

Isn't that a myopic view? While sure, if someone is forever depressed they may not help others (beyond sharing their experience others may relate to). Imagine the people that are in a rough place for a period that come out the other side. I hope those types engage today and share as things change.

What OS are you on? Most my experience with ghub is windows. I think I have 4 dpi stops set and it's typically defaulting to the lower middle one - unless I'm gaming.

I believe there's options to have the mouse run in device mode (settings stored there, but I think the features are more limited) or via ghub where the settings might be stored on the computer. I'd need to dig in again though to remember, I've not touched it ghub settings in a while.

Pixel 8 Pro 3 years ago

At first the AI photo editing features surprised me as likely awkward, however with two little kids - I can see a lot of value here if it works well.

Pixel 8 Pro 3 years ago

I didn't click all the way through, but I'm hoping you don't have to turn in the old phone immediately... I'd like to hang onto it for at least a couple weeks just in case I find the backup/restore process hasn't completely done its job.

Last I remember looking the timeline is within 30 days of receiving the new device.

I no longer have this need as often, but back in the day I set up something for myself just using Traefik and OpenSSH (in docker). Traefik would manage the certs and route traffic to the OpenSSH container that would port forward to my local host with th standard `ssh` commands. It doesn't have all the features of ngrok (maybe SirTunnel does), but was generally enough for my needs.

I have a 2006 vehicle I can still work on and is reliable - so there's no reason to get anything newer for me or my wife. I'd easily jump in it and do a cross country road trip (and will at the end of January).

I don't particularly find that inconsistent, though it's usage may not be super common (depending on the type of work you do in go). If you ever need to do atomic operations, it's rather helpful. Though they have been adding new features in go 1.19+ that help there (Int32[1] type, for example). As an aside, for those using atomics - Uber's wrapper library[2] is pretty pleasant to use.

[1] https://pkg.go.dev/sync/atomic#Int32 [2] - https://pkg.go.dev/go.uber.org/atomic

Now you see the Apple Watch Series N wherever you go, which is ~$400, not the Ultra. It will be interesting to see how common the ultra is over the next few years. My guess is it won't be super common, as it's large, fairly unattractive (IMO), and much more expensive for features that don't even match the competition that much of this Garmin/Ultra/etc type of demographic cares about.

In my opinion that's too specific as you'd need a dozen methods just to accomplish the common needs. Why not use a type as the argument that's explicit and meets even more use cases? Meaning instead of accepting an int just accept a `timedelta` in python or a `time.Duration` in go, or `2.seconds` (I don't recall the type) in rails?

I'm no where near as experienced as you and your team, but that is what I was thinking as I read this. Tesla rather quickly went from the expensive sensors to the camera based setup they have now and it'll be interesting to watch how all this unfolds, safely from my 2006 vehicle with nearly no computers.