I get that you want to be "open", but is everyone involved in these transactions ok with them being shared?
Even if they are, this doesn't seem like a good idea security wise. I see partial account numbers and other IDs/numbers that I assume you'd prefer not be public, regardless of how insensitive they may seem now.
EXPENSIFY, INC. VALIDATION XXXXXX5987 THE HACK FOUNDATION
+$0.89
FRONTING $10,000 TO CHRIS WALKER FOR GITHUB GRANTS MADE FROM PERSONAL ACCOUNT
-$10,000.00
You've found an optional feature called Transparency Mode!
I admit, this is A LOT of information being made accessible. We at Hack Club (the nonprofit organization behind HCB, and the owner of the transactions above) have chosen to make our finances publicly available on the internet. You can read more about it here: https://blog.hcb.hackclub.com/posts/transparent-finances-opt...
That link (https://hcb.hackclub.com/hq/transactions) shows our donations and spending down to the cent since we believe donors deserve to know what their contributions are funding. As a nonprofit, you can talk about what you’re spending money on, but transparency in every transaction builds trust for supporters. This level of transparency is definitely atypical, and I can see why it may raise concerns.
Other organizations using HCB (such as Reboot) can choose to enable this feature too (it's off by default), and they're briefed on the potential risks and level of exposure to decide whether it's right for their organization/team. HCB supports 6.5k nonprofits, and roughly 64% of organizations have chosen to enable this feature.
> I see partial account numbers and other IDs/numbers that I assume you'd prefer not be public, regardless of how insensitive they may seem now.
> EXPENSIFY, INC. VALIDATION XXXXXX5987 THE HACK FOUNDATION +$0.89
As for the account numbers (e.g. XXXXXX5987) visible in some transactions, these are our own defunct operating accounts, and we're aware they're out there on the internet. We have a new way of managing account numbers via Column.com, so these older transactions are less of a concern for me.
I very much appreciate you bringing these to my attention! We're always looking to improve, so I'd love to hear if you find anything else.
This isn't the first time an article is also marketing. Besides, what is wrong with marketing something via a use case article?
This is a fairly tame example of it and I found it an interesting and useful read, knowing full well it was also marketing.
I did a masters on design a autopilot to optimize fuel consumption in formation flight. What is interesting about the aerodynamics is that if placed in the upwash wake of the leader, you are essentially increasing the wing aspect ratio of the system, resulting in gains for both the leader and the follower aircraft. Feels very unintuitive but basically the donut spool is larger and the combined wing is bigger in the spool.
I did a lot of testing with Krea. The results were certainly very different than flux-dev, less "ai-like" in some ways and the details were way better, but very soft and bit washed out and more ai-like in other ways.
I did a 50% mix of flux-dev-krea and flux-dev and it is my new favorite base model.
Anything the requires me to use a different IDE is a non-starter for me.
I can imagine it is a lot easier to develop these things as a custom version of VSCode instead of plugins/extensions for a handful of the popular existing IDEs, but is that really a good long term plan? Is the future going to be littered with a bunch of one-off custom IDEs? Does anyone want that future?
>Anything the requires me to use a different IDE is a non-starter for me.
Windsurf is, ultimately, just an IDE extension. They shipped a forked VSCode with their branding for... some reason. But the extension is available in practically every IDE/editor.
The extension seems to provide the exact same functionality, so I'm not sure what's really needed there. In fact, I have had better results with the Jetbrains and Sublime extensions than the Windsurf editor.
In the end that’s just a business decision: how much revenue can you expect from emacs/vim users versus users that prefer it integrated in an easily installable ide? I would choose to ignore the vim users expecting more revenue from a standalone IDE. You can’t cater for everyone.
> Hot take: if your job can be partially or wholly eliminated by AI, that’s a GOOD THING. If your job has patterns that predictable or labor that routine, AI automation is a GOOD THING.
The article never says why this is good. It just states it then moves on.
> As a whole, I’m sure it’ll give birth to entirely new systems we haven’t even conceived of yet and, one can hope, free up that time and energy towards more meaningful or creative pursuits.
The people's who job it takes probably don't give af about the patterns of their job, or creative pursuits they can do while unemployed. They are probably just trying to pay their bills and feed their kids.
> one of the worst misconceptions in product design is that a microwave needs to have a button for every thing you could possibly cook
"Worst" is a stretch. Not to mention these often actually do more than just power and time. For example detecting humidity and/or varying power over time.
> You can just have a time (and power) button. People will figure out how to cook stuff.
You could, but people don't always want to figure it out, especially when they are hungry.
This would have been a better article if the takeaway wasn't basically "people are smart, make them learn the underlying structure".
I think good design is recognizing when and how to either expose the structure or paper over it, all while making it pleasant to interact with for all users at either end of the spectrum of willingness to learn it.
For a bike, it pays off to learn. For other things maybe not so much. Combining these two very different cases and then making a blanket statement that "Good designs expose systematic structure" doesn't land well.
Yes, it's absolutely great to have a "low floor" -- common use cases should be easy to do, without needing to learn a ton up front. But, hiding the structure is not the only way to achieve that!
For example: a microwave could have presets like "we recommend cooking a potato with this power for this time. If it's undercooked, try higher power, but avoid max power because XYZ."
The simple use cases should guide the user while building up a coherent mental model. If there are fancier sensors being used, those could be explained and exposed to the user directly.
Otherwise you end up with no path to further learning. If I have no idea how potato mode works, then I don't know when it applies or doesn't apply, I don't know how to adjust when it doesn't work well, and I don't know how it relates to the other modes at all.
I think the microwave ones are useful even if they are just presets for time and power.
With a new bike, you can get a feel very quickly for what "5th gear" works well for and experiment with it and get immediate feedback and try other options pretty much no downside.
With a microwave, I don't necessarily want that level fine grain control. I probably just want to eat and not ruin my food and I certainly don't want to spend time running experiments. Having a preset at least gets you in the ballpark.
I get that you want to be "open", but is everyone involved in these transactions ok with them being shared? Even if they are, this doesn't seem like a good idea security wise. I see partial account numbers and other IDs/numbers that I assume you'd prefer not be public, regardless of how insensitive they may seem now.
EXPENSIFY, INC. VALIDATION XXXXXX5987 THE HACK FOUNDATION +$0.89
FRONTING $10,000 TO CHRIS WALKER FOR GITHUB GRANTS MADE FROM PERSONAL ACCOUNT -$10,000.00
CHECK TO LACHLAN CAMPBELL +$800.00
Transfer to Emma's Earnings -$1,923.08
reply