waboremo

I believe you interpreted their comment as a sort of let them drown in hedonism moment, but from what I'm getting it's really just encouraging giving your kid space to find the joy themselves. You can encourage new forms or methods to see if it'll stick but you still have to let them be their own person. Forcing anything will just make your kid resent that entirely, and for a lot of parents they don't even realize this resentment of [subject/task/etc] also turned into a resentment of the parent.

Also I think you're too pessimistic about your past potential. You could have made a great musician, esports pro, hell there are even some successful marijuana companies now! I don't say this to stoke the flames of what ifs, but instead to highlight that it wasn't exactly your father's push for CS that is the only reason for your success. You should absolutely take some responsibility for committing and be proud of that, of course you can definitely attribute your understanding of why commitment is important to your father if that holds true!

Now that's good advice, teach your kids the importance of integral foundations like commitment, don't obsess over which specific field it is.

Even then, you don't have to throw money at the problem right away. If you feel you can save time and money by using Rust instead of PHP (just using the two languages as examples, not a specific indication of Rust or PHP's resource drain), go ahead. Making that decision early on costs nothing.

It's only after a project is off the ground that caring about these decisions winds up wasting everyone's time, that's when you wind up slowing momentum tremendously due to dangling a potential new toy in front of your team.

The problem you are trying to solve is not the elevator operator. The elevator operator is a byproduct of a rushed cheap solution to the problem of crime/access to top floor/whatever the actual problem is. Therefore yes, a retrofit could be a potential solution among many others, what actually is the problem, and how effectively does the role solve it?

I should step away from the elevator example because people are clinging to it a bit too firmly when the entire point is to question [job role], not the specific elevator operator.

All jobs rely on attention. In this example, a security guard having to divert attention to interact with guests at the elevator is going to be distracted far more.

But again, this isn't about the security man!!

We can't simultaneously claim those in the position know best (Cohen's take) and then dismiss their self-perception because it doesn't align with our perception of their role.

Further, how can we trust our perception is the better measure of the value of that job? If the person performing the role can't even assess the value properly, how are they providing that value?

What a brilliant summary of this thread.

So using your example, maybe there is something at the top floor that needs guarding. Someone manually pressing the elevator doesn't fix this, he becomes another weak point that can be easily socially engineered. One alternative solution that doesn't require that bullshit job is a separate elevator with its own lock/access, which is a very common solution used in many buildings.

I don't understand your defensiveness here. The entire point is to question the role as a solution to the problem. Literally what bullshit jobs is all about. This isn't specifically about the elevator man, so you don't need to get all weird about it.

Bullshit isn't a quantifier about how entertaining a job is. Unless the job is specifically about entertaining I suppose.

You do realize that economics relies entirely on humanities, right? Psychology, sociology, philosophy, etc without such fields economics cannot reach any of the conclusions they have suggested since the field's creation.

But it is hysterical to see people try to separate economics from humanities.

Ask yourself: what problem is that job solving and how effective is the solution?

A security guard who has to manually press elevator buttons is not solving the problem effectively. Are you more secure that the guard manually presses the elevator button? Hell there could be an assault in the elevator and he wouldn't know a damn thing because he spent time away from watching cameras to press the elevator button. Therefore, it is a bullshit job.

I'm sorry but someone who is unable to determine problems with a tool they've used for 7 years is a huge red flag. That sort of blindness to frustrations is legitimately a massive problem in this field.

The problem is that a lot of developers consider things forever tools when they are not forever tools and not even close. SQL is one of the forever tools, but even in your short list I would absolutely strike down two of them as "forever tools". They're more like "my favorites that I've invested decades into".

The average is still 100k. Acting like all engineers are somehow the rare FAANG hires who are making 250k+ is absurd. Further, you ignore the context in which "the wealthy" is used, which is describing those who profit directly from extracting value from labor of those who work beneath them. You know, the people who can offer someone 100k in salary because they know they'll make tenfold in profit back anyways.

Your logic doesn't work because salaries are not attached to performance.

That's the catch though, these absurdly high levels of testosterone have not proven better quality of life. Especially for those who aren't suffering from a severe lack of testosterone (far beyond the aging process).

I didn't interpret their question as hostile, this might be a case of you projecting. You felt enraged at the question, responded hastily and labelled them in a certain way. Try not to do so in the future.

It certainly exists/works, but is it productive? With my time using Tamagui I would go with no.

There are just so many traps everywhere. 99% of it isn't your fault, just the name of the fragile RN game. Install another package here to handle one use case on one platform, avoid this component on one platform because RN doesn't support this thing, entire blocks of very simple styles commented out due to performance cost. List goes on. It's a never-ending game of your codebase feeling horribly fragile, and that's if you remain within the RN = Android and iOS realm. As soon as you start trying to get it to be truly cross platform with desktop apps - endless nightmares.

I so desperately want cross-platform development to feel as smooth as people proclaim, but it's really like playing russian roulette with every new component added. At the end, you question if it was really worth it due to how much you've had to rewrite anyways. You become sort of delirious after working on a project that uses such solutions, wondering if you traded user experience for developer experience and wound up messing both up in the long run.

Beautiful site/docs though.

You do realize you still have to write a lot of native code in cross platform apps, right? It's what all the most used apps do.

This idea that individually you can be more productive on a cross platform app has no basis in reality. You're still having to concern yourself with platform specific aspects, except now you're also throwing in another layer into the mix for your shared aspects. These shared aspects tend to also not be up to user expectation most of the time, so you're having to rewrite things that comes easy for native apps, to ensure consistency and accessibility.

Such moves makes sense for Facebook. Given who they hire, what they work on. Same for Microsoft, but not sure using them is a good example considering their app experiences are universally terrible. For a lot of other places though? There has been a grand total of zero proven demonstration of increased productivity or dramatic savings. You still have to hire android/ios/windows/mac/linux devs respectfully whenever you eventually want to expand to those platforms.

Seconding this. The cross platform experience has been so abysmal for so long, that I question whether the benefits of "easier to support" are even real considering the generally worse experience, longstanding bugs that are harder to nail down, and the added time of having to switch mental models between cross platform and the native code you're going to have to eventually write.

I'm at the point now where native apps are still back in heavy consideration, as it's far more straight forward to cascade launch your products on different platforms than it is to half-ass everywhere.

Your equation isn't complete. You can't only care about getting 95% of the way there if the final 5% takes substantially more time than it normally would or worse halts development entirely.

Not sure how much weight this really has in a market such as mobile phones in which additional external competitors are never going to become a reality.

You'll want to look at worker's share of corporate income for the full picture of wages and prices, and that has not recovered since 2008.

None of those things are exclusive to social media, some of them aren't even bad (gossip), and the rest have equal positives (misinformation = abundant information, bullying = uplifting each other).

I always question what intention does someone have painting social media in such broad strokes. Especially when we consider who actively gains from narrowing where information can be accessed.

You contradict your own argument. You recognize Facebook finds ways around it and previously used egregious bullshit, such bullshit that Apple tolerated for years. Yet somehow you believe Apple will protect you, again despite them failing to do so for years.

Avoiding widely used social apps is a great solution. Stop encouraging people to use such apps and believe in a false sense of security. Facebook on your phone at all is giving them far more data than alternatives such as a sandboxed desktop environment, or using a hardened browser. You are not protected by Apple from Facebook here. You just bought into the latest marketing scheme by Apple in their aggressive move to really start prioritizing Apple Ads as a huge moneymaker.

And I say all of this as a huge Apple fan, with multiple Apple devices in rotation. But this encouragement of using the likes of Facebook because "Apple keeps me safe" needs to stop immediately. It was never true and is harming people from seeking proper alternatives.

Macbooks also work OOB and are not a walled garden.

Yep still the case. Good if you're already using cloudflare and therefore the at cost pricing can wind up saving you a bit, otherwise you would be better served with the likes of porkbun or namecheap. Gandi used to be another before it was sold.

Now would be a good time for Cloudflare to announce they've (finally) added .app and .dev support.

Nonetheless, Squarespace isn't bad but I found their domain pricing to be overpriced to target the specific market that doesn't really care about domain pricing they just want their domain and Squarespace set up at once. I can't see myself sticking around post the grace period mentioned.

I think you might just not be allowing time for the seed to sprout.

You should be proud of doing some of the hardest tasks already, so focus more on planting the seed and letting it grow by regularly showing up and watering it. So much of networking is pure chance. Showing up to the same coffee shop, remembering that grocery clerk, going to the same gym every Tuesday, helping out with the same conference group. That repeated action creates a natural sense of trust between people so it becomes much easier to form connections.

I've met people through volunteering, but I wonder would we have become friends if I didn't just keep showing up? Maybe the day we met they could have skipped volunteering because they had something else planned in their usual volunteer time slot, but since they chose to volunteer earlier in the day our schedules finally aligned. Those sort of thoughts, but it's happening all the time! The universe is strange like that. Fate I guess.

It's not easy, especially as an adult, but really you just have to give yourself time to grow in whatever space you want to be in and let the universe do the rest.

How popular was your small east coast college library?

I have a theory about this. Which is that the upper/upper-mid class in particular cares more about the image of a pristine library than they do the actual effectiveness/reach of that library. This theory shows itself quite a lot through how people talk about libraries: not in how many students find what they're looking for, how happy librarians are, how many grades or careers have been improved. It's bathrooms and walls.

They can transfer the information if they want, API changes don't go through for another couple of weeks and archives do exist.

>Sanitizing your inputs has been known about for literally almost half a century that should just be default for developers at this point.

Except if you're a "stupid programmer", in which such defaults are irrelevant to you. In such cases, one can only hope they're relying on tooling that sanitizes as much as possible for them.