Can we simply say, Javascript driven SPA was a bad fad
Can we simply say, Javascript driven SPA was a bad fad
Except people in a typical company who might provide quality feedback on the new website, do not want to "browse Figma". They want an actual website to view - dev site or the actual new live site.
> "You can't just launch a new website and surprise your team."
Yes you can. Nothing beats launching a new site to motivate quality feedback. If you expect feedback to arrive soon after launch, you can use this to your advantage.
If you like the sound of crickets, share a link to Figma and ask people for feedback. Designers and developers will respond, others like sales and non-technical staff often won't. Why? Because people prefer the security of their web browser's familiar reference point when assessing a website. As opposed to browsing an app that gives them a special window to a slippery canvas where an impression of the website is found.
That’s like half the point of prototyping software vs graphic design / illustration software!
Non-designers want to see “the site” open in their browser and be able to click through the pages, instead of use some design app—that’s like half the point of figma.
If it is possible to access the data from a Linux machine - that would be perfect.
I did hit one issue once with maps on my fénix 7 where I had to plug it in to a windows computer specifically.
Although I agree with this there is also another, more subtle thing going on. Rewriting the code that works and someone else is maintaining is a waste of the rewriter's time and is unprofessional. It also denies the original person an opportunity to learn because they don't see how lower quality code wastes time in practice (the time wasted in the refactor doesn't count because Abramov did it by initiative).
The clean code approach is better, but the issue here isn't code. It is that he was wasting his time while not providing useful feedback to the unnamed coder. He was making terrible choices. He isn't maximising the business or team outcomes. The best outcome is the original coder raising their standards and him going and working on something that needs work. He should have angled to that. Ie, the correct option was to do a code review.
The original code established a pattern and left space for where and how to add code to handle edge cases, when they arose, whereas the clean code solution was implemented as though it was the complete and final solution.
A first draft is often incomplete, and in an oversimplified first draft, it’s easy to pull out patterns and remove “duplication” which is a result of the simplification, not an inherent feature of the problem being solved.
My phone's battery is 4385 mAh @3.7V, or 0.016 kWh, and my power costs $0.1252/kWh, or about $0.002 per phone charge. Based on some super surface-level estimates from googling, a typical shower is about 2 gallon/min, and the cost to heat water is about $0.01-0.02 per gallon, meaning for me it's actually about 4 seconds of hot water per phone charge.
Many phones are essentially abandoned by the manufacturer and don't receive any security updates not too long after release, which might just be an issue: https://source.android.com/docs/security/bulletin/2023-12-01
Not only that, but many apps won't run on the older versions of the OS either, due to the API level deprecation in Android: https://support.google.com/googleplay/android-developer/answ...
In other words, you don't really get much of a choice, unless you are buying a flagship device and not everyone will be able to do that. The same goes for the comparatively expensive iPhone devices, the cost also being a factor there for many.
Search found (view HTML or click "More about our materials") on https://shop.fairphone.com/fairphone-5
> In addition, we account for 100% of the cobalt used in the battery by buying cobalt credits, which support the improvement of working conditions for artisanal cobalt miners in the DRC.
Presumably that's what the map signifies. Good to know/in case anyone else was curious.
Related discussion 10 years ago, only one I could find on HN https://news.ycombinator.com/item?id=5813730
Added: https://www.faircobaltalliance.org/supply-chain-wide-collabo... and presumably what the improvement mention above is about https://www.faircobaltalliance.org/approach/professionalizin... ?
I did upgrade a few weeks ago because the iPhone 15 cameras are amazing and I care a lot about that but I honestly had zero performance reasons to upgrade. I’ve never had an issue with a 5-6 year old phone and I always keep my old phone as a backup specifically for banking.
When it comes to leaking secrets, don't trust tools. It's hard, it's human, it just happens.
As for what StackOverflow should do — make it easy to fix leaks, which they do a good job at. Ie. users can edit or delete answers, comments after posting them. Even better if there's a means to create confidential back channels with poster or admin if you spot a potential leak.
It’s easy to find a way to get internet anywhere, but getting an sms message at a phone number is way harder (or easy but expensive); bonus points if you restrict it to local phone numbers only. Lots of countries require ID checks to get a local number and the system breaks with foreign IDs.