Sodman

Being built right into the phone is a huge advantage! Even if you manage to get a perfect bluetooth connection (which, on Android, is a much bigger ask than many realize), and ignore the fact that you now have another separate device to charge - there's no beating this form factor. Your options are to use a horrible oversized clamshell design (eg [0]) that turns your phone into a tablet, or don't physically attach to your phone at all and end up being a 2nd device / accessory to carry around with you / manage / lose.

[0]https://www.amazon.com/BESTLIFE-Universal-Wireless-Bluetooth...

I still consider my old Nokia E70[0] my favorite phone of all time, so I am definitely in the target demographic for this, as I'm 100% sold on the usefulness of a physical keyboard on a phone... However the CPU just doesn't match the "pro" branding, or the price range. I'd personally rather throw an extra $200-300 on top to get a flagship CPU and then it would be close to a perfect phone for me! As it currently is, the Snapdragon 662 shipped in the pro-1x gets blown away by my current Pixel 5's Snapdragon 765G - and Pixel phones recently have been generally characterized as having "above-average hardware specs but not enough to justify flagship prices".

Separately, I am also curious for a phone like this that could run Android, LineageOS, and Ubuntu Touch - are there "dual boot" options in the mobile space? With 256GB storage it seems like it should be possible. I'd like to have old reliable Android as a daily driver, but maybe periodically drop into a less stable but more flexible environment like ubuntu.

[0]https://en.wikipedia.org/wiki/Nokia_E70

You see this very frequently in DIY how-to videos. There's usually about ~30-60 seconds of very helpful instructional content, buried somewhere towards the end of an 11 minute video of rambling and common knowledge. I suspect largely because the monetization gets better if your video is longer than 10 mins...

This is wild to me, as my rule of thumb is the exact opposite! I assume anybody whose profile picture isn't themselves is either a bot, a troll, or a throwaway account they use for comments they know will be controversial. It's the equivalent of having a username like "@John448172312". (Not that you should really trust either group to argue anything in good faith on Twitter).

I see the "GitHub Pages" suggested a lot whenever this question comes up, but it's worth noting that it's against their ToS[0] to use it for commercial purposes:

"GitHub Pages is not intended for or allowed to be used as a free web hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS)."

So it's great if you want to host a personal site / blog or some other non-revenue-generating website, but for anything more than that you could run into issues.

[0] https://docs.github.com/en/github/working-with-github-pages/...

There's a difference between editorializing a headline vs having an article titled "X is the best", where the content is literally "Well X obviously isn't the best, that would be ridiculous. Also we have no idea what the best is."

Some anecdata as a hey.com user myself: It feels like they've optimized a lot for initial load of the main homepage (The "Imbox"). Obviously this is super important for an e-mail app... but once you start trying to load anything older than the most recent ~20 e-mails (Eg scrolling "The Feed"), then the load times can be horrifically slow (>10s, followed by a janky pop-in of HTML suddenly loaded). I'm not sure if this is caused by this technology in particular or if there's some kind of cache miss happening here, but coming from and comparing to gmail - which hey's makers like to dump on regularly - the performance is miserable. Sure, the number of transferred bytes is small and there's not a lot of JS to load - both of which I'm a big fan of, but the actual load time that I feel as a user is pretty bad for these AJAX calls.

Overall I'm a fan of what they're trying to do with Hey.com, but this particular use case feels like a big UX miss to me.

Having multiple offers on the table certainly helps - but I feel a lot of people know what they're looking for in terms of comp range when they're going into the interview process. Recruiters will usually ask you up-front what your target comp range is before even submitting your resume to a company. At engineer salary levels in the US, +/- $5-10k isn't going to be a life changing amount of money (especially after taxes), and is likely within the realms of negotiations anyway. The main reason for big jumps in comp are if you're applying to vastly different types of companies with wide levels of stock options on the table, eg FANG vs seed-stage startup.

You have to take it on a case by case basis. I think the important thing is to have a candid conversation between the candidate and the employer.

"I have a final round interview in two days with another company that ends a 3 week interview process, and I'd like to compare offers"

is a very different response to

"Thanks for the offer, there's 8 or 9 more companies that I'd like to apply to before making a decision, can you give me 2-3 months to get back to you?".

Having a conversation gives both the candidate and the employer another data point. How serious is the person about wanting to work for your company, and how much does the company want to hire you as a candidate? It also just feels like a healthier way to start the relationship.

Internet companies outside of the ad space also track you because they can use it to analyze and increase sales, much like grocery stores. They use it to inform product decisions by answering questions such as: Which features are our users using the most? Which features are the most profitable users using the most? How do we get more people to the end of the sales funnel? etc.

Are you ok with this kind of tracking? Genuinely asking... Personally I see it as "less bad" than straight up selling my data to another company, but I would still prefer companies didn't automatically track me at all, and instead relied on interviews with real users. Or at least make the tracking opt-in, Nielsen style.

Sounds like this watch is absolutely not for you then, and that's totally fine! For me, in 2021, a watch needs to display more than just date/time to earn a place on my wrist. I'm also ok spending another $50 every 3-6 years on a new watch, that doesn't seem unreasonable to me.

Conversely, I'm not keen on the idea of having to manually wind my watch, or remembering to fix the date at the start of every month.

More options is good for everyone though, so I'm glad both exist!

Very excited for something like this! I can think of a few fun projects to try that would be useful to me nearly everyday but are too trivial or niche for an Apple or a Samsung to ever spend time actually building. Some ideas off of the top of my head:

- Vibrate a bunch and notify me on-screen if my usual commuter train is running late or cancelled (but only if I haven't left my house yet). Also the same, but in reverse for my commute home

- One-button touch activate my IoT devices (toggle houselights, garage door opener etc)

- Show me how many bikes/docks are left at my local citibike station

- One-button touch to fake a phone call to my phone to get me out of a meeting/conversation in a pinch

- Show me how many minutes until it's predicted to rain

Nothing life changing, but a fun side project that will continue to be useful once it's finished by saving me 5-10 seconds here and there!

I love that this is going to get more people into the FPV hobby but it feels a little prohibitively expensive. The drone itself (without goggles/controller) looks like it'll be available as a standalone purchase for ~$740 at some point. For reference, a DIY drone using DJI's digital system can be had for $350-500. A decent DIY drone with an analog video feed can be had for ~$250.

When you're learning to fly FPV you will crash and damage your drone, it's part of the hobby. Replacing a $5 frame arm and a $12 motor is a hell of a lot cheaper than this thing will cost. In the verge review the reviewer had a moderate crash into a tree branch and the drone was basically totaled, they had to send him a 2nd review unit, which he also admittedly destroyed.

All that said, I'm impressed with the flight time! Early fpv reviewers are claiming about a 9 minute flight time while flying FPV freestyle. Usually FPV drones get about 3-4 minutes.

solo.io | https://www.solo.io | Boston/Cambridge | Full-time | Back-end Software Engineer

We are looking for extraordinary engineering talent to continue our mission to help large enterprises migrate to microservices and modern cloud infrastructure. Some of our products include a cloud-native API gateway built on top of Envoy (Gloo Edge), a Service Mesh control plane for multi-cluster and multi-mesh management (Gloo Mesh), and a Developer Portal to help publish your APIs and speed up developer onboarding (Gloo Portal).

Our tech-stack is primarily working with Go, docker, K8s, Envoy and Istio. There's also some exposure to WebAssembly and C++. Many of our products are open source, or have large open source components, check out our GitHub if you're interested in how we code - https://github.com/solo-io

We are also hiring for field engineers all over the world, as well as a documentation lead - https://www.solo.io/company/careers/

One of the biggest problems I have with these touchscreens is that, as they're generally included to reduce unit cost for the car manufacturer, they also usually have woefully underpowered hardware backing them.

When I glance at my display after an audio cue and there's a one-button option to change to a faster route thanks to real time traffic data, there's an enormous difference between quickly tapping that button and having it work as expected, vs me forcefully jabbing the screen repeatedly (while staring at it) because the processor is so overwhelmed running the maps app that the display polling isn't registering my finger. You can argue that the touchscreen is a danger either way, but one of these two scenarios is much worse than the other.

K8s absolutely has a steep learning curve, but it feels like we always focus on the most complex setups and use cases so that we can admire the shiniest new features.

If you're going from "our app is running directly in tomcat in our on-prem data center" to "we want to move to a mirco-services architecture with a service mesh, canary deployments, multi-cluster observability, fault injection, automatic global failover, etc...", you're almost certainly going to have a bad time.

I really like the concept of "innovation tokens" [0] here. Pick one or two big innovations at a time and don't add more until you're comfortable with what you have. Get your app running in docker first, and then get it running in a basic k8s setup first instead of leapfrogging to the more advanced stuff. Chances are if you didn't need a service mesh for your original non-k8s deployment, you probably don't need one for the v1.0 first pass of your k8s rollout.

[0]https://mcfunley.com/choose-boring-technology

This is such a great point and so frequently skimmed over in k8s discussions. We as tech folks tend to focus on the front page blog posts about 1000s of nodes and all of the orchestration that goes into complicated top 1% high-traffic/high-complexity use-case setups. In reality there are a lot of profitable businesses out there happily running a simple cluster set up with a single-digit number of deployments chugging along on it with zero down-time.

Really when looking at tools in the k8s ecosystem, it's better to approach it as you would importing a new library into your application. Most decent devs wouldn't blindly import a new lib so that they can copy/paste a single line of code they found online for a business critical function, and k8s tools should be no different. We must think about what value does a given tool bring, and is it worth the cost of learning/maintenance? Sometimes the answer is a resounding "yes", but too often the question isn't even asked.

It is you who is making my point for me. I agree that the 1M would be better spent on any of those things, rather than rotting away in a refuse site somewhere in MA. My argument was never that BTC is a good investment or even that it's worth the opportunity cost. I was just arguing against the "nothing of value was lost" mentality you have at throwing away all this BTC.

Put another way - If somebody were to buy SNAP stock, it's also a purely speculative investment (no dividends, no votes, etc). I may think this is a poor use of money, but I'm still confident if somebody gave me some SNAP stock I'd convert it into USD instead of just straight up throwing it into a dump somewhere and claiming I didn't miss out on any value.

If you don't want to be any richer, then why do returns, dividends, yields or earnings growth matter?

It's great that you're successful enough that throwing away over a million dollars worth of BTC isn't a big deal for you, but that's a life-changing amount of money for most folks. I'm making no claims about the features or benefits of BTC, but one million dollars worth of bitcoin is primarily useful because it can be exchanged for one million dollars, today, right now. It doesn't need any additional features, promises, guarantees or selling points.

> I mined a couple dozen and threw that laptop away. I don't feel like I missed out.

> I invest because I want value.

So you want value, but you don't feel that you missed out by throwing out over a million dollars worth of assets? (couple dozen at ~50k/BTC valuation).

Sure it has no value beyond what someone else will pay you for it, but today somebody else would literally be willing to give you over a million dollars for it.

As somebody who will occasionally have a spurt of 2 weeks hard work on a side project in the evenings, before putting it back down for 3 months, I think branches and tests are well worth it. As the saying goes, there's nothing worse than reading code you wrote a year ago.

Having every commit in a branch pass all tests is a little overkill, but gating merges to master/main on tests passing and then having branches squash before merging seems like a happy middle ground. At least that way every commit in master/main has passed tests.

Firefox is fine and quick as long as you don't need to use any heavy Google apps. Some people might even consider this a plus. For me, between work and personal use I'm effectively married to Gmail, Google Calendar, Google Docs, and Google Hangouts. Unfortunately that makes Firefox a non-starter for me. Not to mention Firefox's privacy settings trigger countless reCAPTCHA gates across most of GSuite. I get that this is not Firefox's "fault" and it's done intentionally by Google, but as a user it becomes my problem.

I really want Firefox to work for me and I'd love to drop Chrome, but last time FF made big noise about performance improvements I tried it out and Gmail was still unusably slow.

This would likely be in violation of several wiretapping laws though (Also, Clubhouse's own ToS).

Once clubhouse loses its exclusivity and becomes generally available, where will they be at? It's essentially just a discord clone with better marketing and hype. Or, in its most common format of 1-3 people talking and 1000s listening, it's basically FM radio. Is that enough for it to be widely successful (the "next social media platform")? I'm not convinced.

The biggest features it's got going for it once it hits GA, are that it's ephemeral and that it's live. There are several other platforms with decent UX already providing these USPs, also for free. I can see this being a live-streaming broadcast service for celebrities and influencers who already have big audiences, but not much more than that.

> If you see it as a place to have conversations with your professional community, your feed is going to look like a constant streamed event with the best content.

Does anybody actually see linkedIn as this? LinkedIn largely markets itself as an employee <-> recruiter <-> employer connection platform, and almost all of the posts I see reflect that. Let's say I mute the posts advertising job openings or blatantly pushing company PR. Most of what's remaining is just buzzword regurgitation by self-proclaimed "thought leaders" trying to make a name for themselves before they jump ship for a better title. There's a reason we don't see many LinkedIn links getting to the front page of HN - there's very little good original content there.

If I want to get an honest opinion from professionals in my community, I'll follow them on twitter, read their blogs on their own platforms (or the likes of substack), or even reach out directly. Everything posted on LinkedIn is implicitly poisoned by the filter of "This post exists mostly to make me look good to future employers/employees", which rarely makes for good content.

Style nits aside, I don't think it's a good idea to selectively pick the worst N things in a PR and let the rest go. If you're consistently finding 10+ things to request changes on in somebody's pull requests, you probably need to look at your engineering process. Was the high level approach discussed before it was fully coded and "ready for review"? This is something easily fixed by process changes.

Are you finding a lot of little things in the PR itself? Many of the usual suspects can and should be automated away (linting, codegen, test coverage reports, static analysis, etc). Others can easily be added to a checklist before PRs are submitted for review, eg "Have you updated the relevant documentation".

Usually newer employees will get more comments on their PRs, as they're not as familiar with the system and might fall into more traps that others know about from experience. This can be mitigated somewhat by pairing/mentoring.

Sure some people just aren't going to cut it on your team, but most engineers when corrected on an individual coding mistake won't repeatedly make the same mistake, in my experience. If you just never mention the mistake, they'll keep making it in every PR and be completely unaware. Sometimes it helps to communicate out of band (ie, not in "official" comments on the PR itself) if there are some low hanging gotchas you want to make the engineer aware of.

I would take this to mean a replacement for the "original" Facebook feature set, of sharing personal news, stories and photos with a pre-selected list of friends and family.

Many people (myself included) don't _want_ the newer marketplace / open community aspects of Facebook to be mixed into a platform where they share personal updates. If that means I have to give up 100 likes and comments on every baby/puppy picture I post, that seems like an acceptable trade-off to me. If folks want to comment on any of my updates, they can communicate with me in other channels (e-mail, text, real-life). Not for everyone, but it's definitely a market niche that's under-served right now.

This seems like a much more polished product, but it seems more targeted as a PaaS for professional content creators. The minimum requirements[0] are pretty high for somebody who just wants to self-host a blog for friends and family:

- Ubuntu server with NodeJS / Ngninx installed

- 1 GB RAM minimum required

- MySQL running somewhere

The PaaS "Everything just works" offering is probably more attractive to the "facebook, but private" market, but for $36 / month I don't get any guaranteed SLA[1] which is worrying.

[0] https://ghost.org/docs/install/ubuntu/ [1] https://ghost.org/pricing/

In the US, they are very specific, distinct things.

Tax Evasion[0] is not paying taxes you legally owe. Tax Avoidance[1] is finding ways to owe less tax. Evasion is considered illegal, but Avoidance can practically be considered encouraged, as it's perfectly legal and rewards practitioners with lower tax bills.

[0]https://www.investopedia.com/terms/t/taxevasion.asp

[1]https://www.investopedia.com/terms/t/tax_avoidance.asp

This seems to be affecting a lot of folks - https://downdetector.com/status/verizon/map/