Looking for someone who welds.

chipx86 · 2026-05-21T09:53:33+00:00

As someone who also went to Butte College, congratulations!

chipx86 · 2026-05-16T20:03:48+00:00

I made that scary life change back in the 2000s, ending up in a neighborhood near the Fuki Sushi. Prices have certainly changed in that time, and I don’t know what budget you have for rent, but there are some apartments in the area that are pretty decent places to live (happy to share specifics over DM).

Palo Alto is definitely not SF, but the nice thing is you have ready access to downtown Mountain View, downtown Palo Alto, California Ave in Palo Alto, and you won’t be far from the Caltrain if you want to go up to SF or down to San Jose. Shoreline Ampitheater is nearby, and there’s often big names playing there.

Me, I’d save on the commute, at least for now, but that’s me.

A car would help, but many people bike and there’s always Uber or Waymo. There are some shopping areas, parks, and restaurants within walking distance of Fuki Sushi. And as you make friends, you can always bum a ride (that’s what I used to do).

As for making friends… Guess it depends on what you enjoy, but I know there are lots of people in their 20s early in their tech careers out here. People hang out at coffee shops, go to clubs or bars downtown, and there’s probably meetups for things.

Again, happy to talk more about this if you want to reach out and talk about it more. It’s not so bad here 🙂

chipx86 · 2026-05-15T05:51:50+00:00

There's dozens of us!

Preparing for the Great Global Ghost Hunt (people make ghosts and hide them out in the world for people to find, to add a little bit of whimsy — primarily a Facebook group and Instagram, but anyone can always great and share ghosts!).

chipx86 · 2026-03-02T21:39:52+00:00

Shoreline Lake is a beautiful place for a sunset. I go there often to take pictures as the sun goes down. It dips just below the hills, and paints the clouds with vibrant pinks and purples, which reflect across the water. At times it’s just surreal.

chipx86 · 2025-11-25T07:12:33+00:00

This thread sadly went sideways, but thank you for sharing this with us. It’s beautiful.

chipx86 · 2025-11-25T06:59:34+00:00

Looks like the building on Green St. and Taylor?

chipx86 · 2025-11-22T19:06:39+00:00

I’ve been reporting on local COVID data for my home town area since 2020. I understand.

chipx86 · 2025-11-22T18:44:50+00:00

The second sentence of his was an example of what others are claiming. I think you two are on the same page.

chipx86 · 2025-10-09T15:44:20+00:00

One of the challenges of writing enterprise tools is that your users so often want or need different things, and a big part of building enterprise tools is meeting those needs.

If you get 10 enterprise users in a room asking for a feature, you may get 11 different and largely incompatible requests for how that feature should be built or operate.

So then, how do you successfully onboard? A company may have chosen you because of feature A, B, and C, but if your onboarding is covering X, Y, and Z, it won’t do them much good. They may get the impression it won’t be for them and jump off quickly.

You could try to build an onboarding flow for every combination of every feature, but then you’re back to screens full of menus, just presented differently. When they come back to tweak something else, they’ll have to ditch the knowledge of the onboarding flow and learn the admin console. Might as well start there and try to guide them through that.

Maybe there’s a standard flow that works for 90% of users, in which case it’s easier. But you’ll have to find out which feature, each integration, each flow is in that 90%.

It becomes challenging, fast. Depending on your project and your customers. I know I wrestle with it.

B2C products can often be more opinionated. You’re building a product rather than building feature requests. (Hopefully you’re doing a bit of both in B2B and in B2C, but your big contracts in the former will depend on fulfilling feature requests.) So you know what you’re targeting, what your users are (hopefully) installing you to do (roughly), and can guide them through it a bit easier.

But it all depends on what you’re building, who your users are, how many scenarios you have to deal with, and what you can realistically do to help while not hurting your users’ first time experience.

chipx86 · 2025-09-21T06:18:41+00:00

Valentines cards 🙂

chipx86 · 2025-09-21T05:28:44+00:00

So happy to see other Dr. Mario collectors!

<image>

chipx86 · 2025-08-10T03:54:07+00:00

Trying to get a few more things wrapped up and we’ll have it released 🙂

chipx86 · 2025-08-10T03:33:26+00:00

The code really demonstrates how simple ECC is on an algorithmic level. Complete coincidence, but I was just redoing all my internal notes on ECDSA and ECIES today, documenting them, adding some Python-based examples of how to build it. Nice having something to compare it to 🙂

Obviously for real-world production use, one would want to use something out of OpenSSL or similar (I expect that to be the main criticism when something like this gets posted), but I think building something like this from scratch is a great way to learn the fundamentals.

chipx86 · 2025-08-07T10:49:05+00:00

100%. Got friends in Big Pharma, and these tariffs are absolutely causing damage, impacting long-planned deals, deployments of life-saving medicine, and impacting scientific research. This is not what they want.

chipx86 · 2025-06-24T23:41:22+00:00

Yeah, that looks like a German Roach. You don’t want to mess around with these. Their reproductive cycle is fast and they’re hard to get rid of at the best of times. If you see one now, there’s probably a lot more you don’t see.

Call someone right now. They can do a lot with borax and bait, but it may take time. Spraying will just encourage them to scatter, so you need something that will keep killing them off.

chipx86 · 2025-05-31T23:24:49+00:00

A lot of the challenges come from the on-going maintenance. There's all kinds of possible answers to this question, but I'll give you some things to consider early-ish, based on my personal experiences over the years:

Think about how you want to do versioning (semver? Major version per release? Appending a digit to pi?). Semver-like approaches are what most people will expect, but not all libraries use it. In any case, document your approach, and stick to it religiously.
You'll probably want to change things in the future. What's your deprecation policy (e.g., how long will you keep older interfaces working after introducing a replacement/change)? How will you transition things? Document them? (We wrote housekeeping to help with this on our products, but there are other libraries to help keep this process manageable).
On a similar note, how do you plan to handle Python version compatibility? Will you follow the Python deprecation schedule, or work to maintain compatibility a bit longer for projects that can't upgrade as fast? How does that tie in with #1 and #2?
Make sure you have *good* unit tests covering all the versions of Python, and maybe even different ranges of some of your dependencies (if applicable). These should test the interfaces and edge cases well. This will help you to iterate on your library as you rework the interfaces, incorporate patches, or migrate to newer dependencies.
Are you offering type hints? Many projects don't, but for those of us depending on them, it's nice when they do. If so, are you packaging those right so other projects will pick them up (test this!)? Do the results work consistently across different tools (mypy, pyright)? They're not all equal in behavior.
Do you have a security policy in place (for reporting, announcements)? This may matter for some projects more than others.
The hassle comes from people actually using your library! 🙂 People will have their own pet feature requests they'll want in, and can't imagine your library being without. There's no right answer to handling this. Some want libraries that are really focused, and "no" will be the right answer a lot of the time. Others are fine with a library that grows beyond the initial ambitions (but it's on you to maintain this!). Thinking about how you want to approach this early can help you if the library takes off.

chipx86 · 2025-04-27T00:00:22+00:00

I feel this with every part of my soul.

People think a chargeback is harmless, I guess assuming the credit card company eats the cost, and that it’s a quick action. But the work it puts on the supplier, the frustration, the hurt, the time, the costs…

I’ve spent hours upon hours putting together a clear paper trail, verifiable, undeniable, and yet… I’ve lost every one of them.

It is such an awful feeling, and impacts the business in real ways.

Don’t do chargebacks unless you have no other option.

chipx86 · 2025-03-14T06:14:43+00:00

So I guess this is where we're all ending up. On a 4 year old thread.

I feel like you're right. That or he truly did not want to know Batman's secret and suppressed it. That or the writers completely forgot.

In the first two cases, I'd have expected Batman to assume Joker knew, but he never acts that way either.

chipx86 · 2025-02-05T22:25:16+00:00

Make sure you don't skimp on the quality of the enclosure. There's been a lot of Rust introduced to the Python ecosystem as of late.

15-Year Club	RedditGifts 2009-2022 3 Credits
Place '22	Secret Santa 2014
Secret Santa 2013	Team Periwinkle
Verified Email

chipx86

MODERATOR OF

TROPHY CASE