No offense, but this sounds like a terrible camera for your use case. It sounds like you know that.
My Sony that I've been using as a webcam since COVID can do that, and it was 6 years old when I bought it. Upgrade when you can!
1,969 karma · joined May 25, 2015
My Sony that I've been using as a webcam since COVID can do that, and it was 6 years old when I bought it. Upgrade when you can!
USB can do just about anything. Video out is one possibility. But HDMI can already do that.
It doesn't make sense to expect the manufacturer to provide a free app to make USB do something you can already do over HDMI, and for which HDMI is intended.
This article is rage bait where there's no real cause for outrage. But it's adjacent enough to "right to repair" and "subscription fatigue" that it sounds outrageous.
This is how I've used my Sony camera since COVID. It works great.
I wasn't sure at first if OP was trying to do something nonstandard, because you get video to your computer with a video cable. Plus a way for your computer to capture that, which for me is CamLink.
Honestly, I'm surprised there's a relevant manufacturer app at all. Not surprised that it costs money.
This is a bit like not having power in your home to charge your camera with and asking the manufacturer for a generator. They may have a solution, but the price will be bad.
Why not both. I hire, and it crossed my mind to reach out to him when I read the ending. The project shows ambition and independent thought, two virtues in my book.
He's smart to leverage the attention. Might as well get some benefit out of the university's heavy-handed policing here.
Remember Monica? She was a Stack moderator who got in trouble over Stack's new Code of Conduct a few years back.
The Code required using people's pronouns if they listed them. Monica always used gender-neutral pronouns and wanted to keep doing so, but Stack took issue with this.
Pronouns are a pretty standard part of interacting with someone in English -- and so is the "thank you" in GP's Stack post. So why is one social convention mandatory while one is forbidden?
Because it's not about what's on topic and what isn't. It's about archetypes. And the highest archetype for a certain kind of programmer is the Vulcan. Be respectful, be noble, but don't "waste time" on pleasantries that are just there to convey warmth and friendliness.
The problem is that not all programmers are Vulcans, and more and more non-Vulcans have become programmers as coding has become more and more mainstream. But Stack essentially set up test cases for how Vulcan its users are. That tends to be an alienating culture for those who aren't.
Well, yeah. Sometimes the status quo is good. Sometimes you don't want to learn how to do simple async page updates for the thousandth time.
Because many of us here have been there, done that. Over dozens of years. With dozens of libraries.
It's a hamster wheel. It's boring. It's pointless.
In the end, if your website/app does what HTMX is good at, just use it.
I learn dozens of new things every day as a solopreneur SaaS guy. I don't want to relearn how to make async page updates ever again, unless there is a very, very compelling reason to do so.
Which leads me to...
- Is this closed source?
- Does it cost money?
- How does it discover data relationships?
For me, I'm a bit of a screen junkie with social anxiety. One of my blockers was negative self-talk. I would think, "They're going to get angry. They're going to ignore you. They're busy. You're going to waste their time."
I started replacing that with images of the person being interested and delighted by the interaction. That helped, but I also knew that wasn't realistic if I just walked up and blurted out, "Hi, I'm an isolated remote dev and I'd like to talk." Someone might be sympathetic, but I didn't want sympathy; I wanted people to have fun. So I started using the techniques I mentioned.
This can all be learned from books on small talk, personality psychology, social dynamics, etc. But unfortunately, it's rarely talked about or taught, at least in my circles. And people are suffering as a consequence.
Learn the dying art of in-person socialization. Memorize interesting things to talk about if needed. Buy a deck of icebreaker cards for inspiration.
Strike up conversations anywhere and everywhere. Learn magic tricks to entertain people with. Film things in your neighborhood and show people clips that you think they'd like.
For the rusty or nerdy (like me), write test cases for your interactions. Figure out what went wrong if someone isn't receptive. Refine your approach until you figure it out.
"Digital everything" has proven to be a dead end. We need to go backwards to go forwards.
Using a poetic descriptor like "mournful" in this context seems out of place.
(For those who haven't used it, fzf is a fuzzy-searchable menu for the command line. You pipe lines of input to it, and it shows them in a menu. You start typing and it fuzzy searches the menu and selects the best match. Then you press Enter to pipe that out, or Tab for multi-select. It's fantastic.)
I have convenience functions in my profile script that pipe different things to fzf...scripts, paths in the current directory to copy to the clipboard, etc. It's indispensable.
Bonus: progressive enhancement. If someone doesn't have fzf/those convenience functions, it's just a directory with shell scripts, so they don't have to do anything special to use them.
This year, I actually had a prospect thank me for a cold email I sent him. He said in his 20-year career, had had never gotten one that was so helpful.
Of course, that was nice, but the metric I'm most concerned with is sales -- and yes, they lead to those as well.
The best ones, like the "best in my 20 years" one, have been the result of a lot of research, hand-crafting prospect lists based on what I believe are their exact needs, then writing a message that speaks to those needs.
I'll add since this is HN: I have no course to sell and my startup isn't mentioned or linked anywhere. I'm just writing to share what's worked for me.
> This claim is hard to reconcile with the CDC's official numbers which show a typical life expectancy for the entire area
Buettner's focus was on the outliers. Loma Linda is a longevity hotspot, and the question is why.
He found the long-living outliers practiced certain behaviors that they associated with Adventism, like vegetarianism.
Not all Adventists practice those behaviors. About half of Adventists eat meat, for example.
But the long-living outliers were Adventist and practiced the behaviors that he highlighted. So that was his takeaway.
That's my point -- the region's average lifespan is irrelevant. It's only relevant given the misconception that Loma Linda itself has some special properties of rejuvenation.
But that doesn't mean it's not a longevity hotspot. Even if the average lifespan there were lower than normal -- say a large number of unhealthy people lived there -- it still wouldn't negate that, if an abnormally high number of healthy centenarians also live there.
The CDC's average was purely geographic and irrespective of lifestyle, which is different.
The CDC looked at average life expectancy in Loma Linda across all demographics. Purely geographical and on average.
The blue zones focused on the greater longevity specifically of Adventists in Loma Linda.
It wasn't a question of whether living inside the municipal boundaries of Loma Linda automatically conferred some special health benefits -- clearly it doesn't.
It was, "Why is there an unusually high concentration of outliers living here, and what behaviors cause them to live longer than average?"
The researcher's criticism of Loma Linda isn't that people don't live longer there; it's that Adventist Health purchased Dan Buettner's marketing company Blue Zones LLC in 2020.
Adventists are teetotalers, so he questions why they'd want to be associated with the Blue Zones guideline of drinking "every day at twice the NHS heavy drinking guidelines."
Which is a fair question -- but it doesn't have anything to do with whether Loma Linda is an area with greater longevity.
Reddit has worked around their lack of it to some degree with location-based subreddits like r/AtlFilmmakers. But subreddits are high maintenance, and they isolate content. Plus, the naming conventions aren't standard. Maybe there's r/AtlFilmmakers for filmmakers in Atlanta, but another subreddit for musicians uses the state in the name instead of a city.
It's a bit like folders vs. tags. It would be nicer to have a single filmmaking subreddit with the option to filter on users' locations -- and default filtering out of location-specific posts in other places.
That wouldn't just make for better dating, though it probably would compared to something like Tinder. It could also lead to stronger local communities and better health outcomes.
- Less physical activity, more obesity. Both have known effects on memory and cognition.
- Childhood screen time, which has been linked to poor sleep, worse communication skills, and developmental delays.
- Easy, anonymous access to infinite novel pornography, which may affect the development of gray matter and the functioning of the prefrontal cortex.
- The decline of community and communal spaces and the detrimental mental effects of isolation.
Getting people suspicious that more science education will decrease IQ is about the last thing we need. (And I wasn't a STEM major, for the record.)
No studies are cited. The assertions are corroborated by the author's personal experience.
Take its claims with a grain of salt.
This is about how people self-described when they feel alert and productive. It doesn't necessarily mean there aren't benefits (or conversely, detriments) to "early to bed, early to rise."
It's possible that the work of those who feel the most alert in the morning is more physical -- for example, manual labor. Maybe they have less of a need and opportunity for cognition, so their scores are poorer. Maybe, too, the work makes them feel differently by evening from how night owls feel.
It's also possible that those with a high need for cognition tend towards work that can be done at any time of the day or night, and they are tired in the morning because they (whether optimally or not) stayed up late in the night working on it.
So, a follow-up question is how this relates to behavior. If night owls consistently go to bed around the time of peak melatonin production and wake up early, do their scores improve? Do their preferences change? And the same question in the inverse for larks.
Think of spreadsheets as a convention-over-configuration low-code environment with a tightly coupled GUI for spinning up run-almost-anywhere apps that non-coders can modify. One of the few low-code environments that I actually like.
I'm a solopreneur whose SaaS product I coded from scratch. I love GPPLs, but I also create spreadsheets all the time.
Sometimes that's because of the stage of an idea: There's a new process you've discovered you need, but you don't have time to invest in building/buying/learning a tailor-made solution.
A case in point is a business overview dashboard I built to keep an eye on the metrics I care about. It pulls data from disparate sources using Power Query, which is built into Excel and can pull from databases, APIs, CSVs, etc. There's no hosting infra and no new monthly fee as I already had the Excel license.
Another nice thing about spreadsheets is that today, they're multi-user and real-time collaborative. You can send someone a link and both edit an Excel or Google Docs spreadsheet in the browser with very low ceremony. And if they're on a power user, they can modify the formulas themselves. That's a bad thing for some use cases but a truly great thing for others.
The ubiquity, the local-first option, the tightly coupled GUI, the widely known syntax...those things make spreadsheets very attractive for certain types of projects.
For others, building an app is the right answer. They both have a place.
If it's a small, standalone CRUD app on a SQLite database, mocks would probably be a bad option, sure.
On the other hand, it could be an integration platform that integrates with many third-party services. Some of them may not have test environments. Or some of the integrations may be written by third-party contractors, and we can't expose service credentials because of poor permissions granularity. Mocks are a good option there.
This goes back to team size and skills. Not all teams have build engineers. And not all mocks are so complicated that they take up that much time.
Again, it depends on the scope and the resources. The article goes too far by calling mocking an anti-pattern. It simply isn't.
Some of the advice is good, like decoupling I/O and logic where that makes sense. But the general idea of mocking being an anti-pattern is overreach.
This kind of thinking is overly rigid/idealistic:
> And with Postgres you can easily copy a test database with a random name from a template for each test. So there is your easy setup.
> You need to test reality. Instead of mocking, invest in end-to-end (E2E) testing.
"Easily" is like "just." The ease or difficulty is relative to skill, time, team size, infrastructure, and so on.
As for testing reality, sure. But there's also a place for unit tests and partial integration tests.
In some situations, mocking makes sense. In others, full E2E testing is better. Sometimes both might make sense in the same project. Use the right tool for the job.
Your numbers come out to $250K/year at Google and $230K/year as an entrepreneur. That's a small price to pay for this kind of real-world education.
There's no guarantee his next business will be successful -- but there's no guarantee that those kinds of Google positions are going to keep existing, either.
On the other hand, there's also the chance that his next business could be massively more successful because of lessons learned, and open the way to much higher amounts than he could have been earning at Google were he still there.
Overall, I think it was a massive win for him. And it may have been more beneficial to society than the work he was doing at Google.
I opted out a week or two ago, but the past code is there. If a competitor asks it how to solve a problem that I already solved, the model will be that much better at solving it than it was before. I effectively just commodified part of my code base.
The same goes for Slack: The fact that Slack started training on private chats alarmed me. Conversations encode patterns of processes at a business. And Slack isn't exactly a small fly-by-night operation. (Edit: In their blog post, they at least say they aren't using the data to train LLMs that will be public, unlike OpenAI is doing by default with ChatGPT chats.)
These companies wouldn't release unmodified customer data into the wild, but the zeitgeist seems to be that trained models are different.
That said, I agree with your point about my startup's core value. I don't want this to become a distraction that impedes business. So it isn't a top priority by any means. But it's definitely on my radar now as a rainy-day project.
I also agree that a nonstandard experience could well lower the quality internally, but I might just consider that a cost of doing business until there's more regulation around this.
https://www.reddit.com/r/ios/comments/1cryayx/latest_ios_upd...
"Uber Migrates" (beginning: company that I'm interested in does something) "1T records" (middle: that's a lot of records; I wonder what happened) "from DynamoDB to LedgerStore" (hmm, how do they compare?) "to Save $6M Annually" (end: that's a good chunk of change for me, but was it worth it to Uber? Why did it save that amount? Let me read more)
It's a simple and engaging "there and back again" story that paves the way for a sequel.
Versus:
"How LedgerStore Supports Trillions of Indexes at Uber" (ah, okay, a technology supports trillions of indexes. Moving on to the next article in my feed)
"Migrating a Trillion Entries of Uber’s Ledger Data from DynamoDB to LedgerStore" (ah, a big migration. I'm not sure who did it or whether anything interesting came of it, or even whether it happened or is just theoretical because of the gerund, and moving one trillion of something is cool but not something I probably need to read about right now, so let's move on)
YMMV. Some probably prefer the more abstract/less narrative titles, but the first one is more of an attention grabber for me.