rdez6173

Double seems more like a feature than a product. I feel like Copilot could easily implement those value-adds and obsolete this product.

I also don't understand why I can't bring my own API tokens. I have API keys for OpenAI, Anthropic, and even local LLMs. I guess the "secret" is in the prompting that is being done on the user's behalf.

I appreciate the work that went into this, I just think it's not for me.

Hey, sure, let's destroy the Earth and its inhabitants with zero regard for anything! As long as we get to take vacations to the moon! Right?

This is preventable, and should be prevented. I don't care if it's Elon Musk or anyone else. Engineers should not be reckless in their endeavors.

Nope. Greed.

It costs way more to build out physical ergonomic interior controls when they are permanent fixtures for several model years and any changes require new physical elements to be created and fit (and designed for mass production).

Software can be updated over the air, so there's less pressure on engineers to get it perfect.

The solution is not to point fingers and guess, but instead measure and revise. Study the amount of time drivers' eyes are off the road for routine tasks, develop acceptable limits and enforce them.

Software engineers of any ilk are just as capable of following sensible guidelines if everyone else in the company is obliged to as well.

This gets into hairy territory of derivative works. I think this will be an uphill battle for content creators until laws are updated for the new state of the art.

Prior to the unfettered access to generative AI, derivative works took time and effort comparable to the original. Now, derivatives can be created en masse and in seconds.

Where's the line? What's fair use now? These questions will likely be answered in a court or by legislative bodies.

In the meantime, protect your images, paywall high res versions, watermark thumbnails, etc. Also, if you're going up against a company? Lawyer up.

Amprius has 400+Wh/kg that are commercially available. I'm sure they ain't cheap, but the tech exists.

https://amprius.com/products/

Edit: well, I'm a dummy and OP said mass-produced. Sorry.

Cool! I like the monochrome gradient variant!

Fun exploration and exceptionally impractical. Love it.

The parent commenter said this:

> People [..] freak out about this because [..] in 99.9% of companies, running code on an engineer's workstation would immediately be the highest possible level of breach.

So it's not selection bias, it's a counterargument. The poster also said engineer not "VP-level".

So, your comment is not really relevant.

I've never had Windows Defender use a noticable amount of CPU. It is, by far, the least intrusive antivirus/anti-malware that I've used (and I've used them all).

Unfortunately, I can only provide my anecdotal experience, but it seems to be in stark contrast to your comment.

The refactored version is doing what pipes would do in a language that doesn't support pipes; it's reordering the statements into execution order rather than having to use a mental "stack" to grok the original version.

Given that the OP stated that they like the pipe syntax, and the refactored version illustrates the hoops you'd have to jump through without it, I guess your comment is just a strange way to agree with the OP?

The point is that the "tree" is not exposed to the user. I feel the author makes this extremely clear.

The only person that made this about the CISOs gender is you. OPs point was about the lack of credentials, which would apply to anyone.

I think it's a reasonable conclusion to draw, due to the nature of the very sensitive data at risk.

Having professional accreditation that you should be overseeing the security of peoples most sensitive information is objectively a good idea.

Muddying the conversation with virtual signaling is more surprising to see on HN.

The same could be said about the use of images on a site.

The solution is to develop sites with accessibility in mind. Use a screen reader; experience what ALL your users will experience. Experiment with various rendering tools to emulate color blindness.

There are even more tools to performance tune your website.

This all comes down to the site author taking the time to cater to as many users as possible. It is not inherently a problem with the use of JavaScript, or dynamic elements.

So, yeah, there are a lot of shitty websites out there. Folks that choose to deliberately cripple their browser are more likely to see these shortcomings.

I think it's important to remember that candidates should evaluating the viability of the company as a potential future employer. This seems like a reason to look elsewhere. They do not seem to value the candidate's time (assuming positive intent otherwise).

I'd skip the shenanigans and look elsewhere. I think "thanks, but no thanks" is a good response in this case.

I'm not sure why this is being shared if the site is wholly incomplete. Outside of the TODO links and bogus videos, two of the listed libraries point to invalid or archived repos in GitHub.

Agreed that Apple should be consistent in their enforcement of their rules. However, you can opt not to use the App Store. If you think that will impact your product, then this confirms that the App Store provides value - value you will need to pay for.

I am a software engineer and I was once asked during an interview at a large hedge fund to pick a side and debate why war is justified.

When I pressed them about the relevance, they indicated that they often have heated debates on all manner of topics, so they wanted to see my thought process.

I enjoy solving complex problems, but socio-ethical problems are way outside of my wheelhouse.

I politely indicated that I didn't think the company was a good fit for me.

I wonder, for a container plant, if you can reliably use weight as a measure of soil saturation. Of course plant growth would add to the weight, but I suspect that could be accounted for.

Could it be argued that the knowledge of which finger (or part of your finger) you use for authentication is equivalent to a passcode?

These anecdotes seem a little light on detail, so it's hard to really see how Fred was treated poorly.

Through the course of my career there have been personality conflicts. I think this is natural and common. In the world of startups it can be even more dramatic.

The bottom line is that you should be confident in your skills, but not be an asshole (and you should expect the same from your colleagues). And, unless you have an equity stake, you can always move on.

It sound like Fred did this - he dealt with some standard workplace BS, then moved on when it was untenable. Good on him.

I just wish the examples were a bit more detailed and illustrative of the post's title.

The iPad is a tool for consumption rather than production. For those without an iPhone, I think the iPad is a terrific device for consuming content.

I think that if the iPad could serve to bridge the gap between consumption and production, then its place would be clear.

I own a Surface Pro 3 and I adore the ability to switch between consumption and production. However, its presentation and implementation leave a lot to be desired. It's often jarring switching between the clean Windows Store apps that were designed for touch, and the "Desktop" apps that dump you into the familiar, but frustrating, desktop where the mouse and keyboard dominate.

I feel that, if done well, a multipurpose device could supplant the incumbents.

I think this is about finding a balance between pragmatism and perfectionism. We should strive to find the simplest, cleanest solution to problems and continually refactor to keep complexity at bay. The SOLID guidelines, practically applied, may help in achieving that goal, so they are worth having in your toolbox.

I find the thought of communicating directly with someone a bit anxiety-inducing, but I would really love to volunteer for something like this.

I would be happy to transcribe a letter, or product expiry date so that I could be read back to the user with text-to-speech in real-time.

I suspect that I'm in the minority and this is likely a non-issue.

When the app is forced to coexist with cheap/freemium applications in the App Store, it can be easy for consumers to make an apples-to-oranges comparison. That is, Angry Birds offers a lot of value at $0.99; does this app offer 100x the value? Is the value comparable? The user comments presented in the article seem to indicate unreasonable expectations set by the App Store market as to the value of software.

Perhaps they need to focus more on operating within the constraints of the market rather than fighting against them. There are several business models that work, and it doesn't need to be advertising based. They could offer tiers of functionality that that are priced accordingly. They could make it a subscription service. They could make make the functionality modular and offer a la carte in-app upgrades. In addition to all of these, they could offer a lifetime "platinum" version at $99.

This is not an all-or-nothing proposition. Unit tests have their place in protecting against regression and validating known invariants. Granted, by not starting with a test for every bit of functionality, it's not really TDD, but why can't we balance practicality with perfectionism?

I think that DHH was implying that blindly following the TDD methodology may lead to worse code that's riddled with architecture simply for the sake of testing.

I feel that using TDD for one or more subsystems may make sense. For the entirety of a large-scale application under tight shipping constraints? I haven't seen it work - but that's not to say that it doesn't.

What's important is that we test our code. If you need some strict guidelines to keep you in check, then perhaps TDD is perfect. If you know that your can get significant coverage from integration testing, then it's probably sufficient. If you find a bug, and put a unit test in place to make sure it never happens again - then you're likely on the right track.

So, dropbox hasn't optimized for what they consider a corner case. I hardly think this warrants the sensationalized, apocalyptic, headline.

Should they address this issue? Yes, and it sounds like it's on their radar. Do we need to sharpen our pitchforks? Not likely.

I don't know how much it matters what the screen looks like under magnification.

I think it's a matter of preference and which best suits your lifestyle; there are pros and cons of both.

I imagined the signal to UI representation would be a fairly standard algorithm. I'm surprised this issue didn't come up in their testing.

Then again, I really don't know how complicated this can be. It just seems like there have been enough phones released that did (perceivably) display the bars correctly that this should be a non-issue.

I imagined the signal to UI representation would be a fairly standard algorithm. I'm surprised this issue didn't come up in their testing.

EDIT: then again, I really don't know how complicated this can be. It just seems like there have been enough phones released that did (perceivably) display the bars correctly that this should be a non-issue.