Density/proximity are far better incubators for innovation than people being bored and isolated on farms. Also not sure where the idea that 'freedom' is associated with farms comes from? How free are you if you must wake up at 4am and work for 12 hours to barely make a profit?
There are exceptions. They are notable for being exceptions.
Independently-owned farms aren't slave factories. Sometimes you'll be doing consecutive months of 13hrs/day labour, sometimes you'll have 75% of the day free, every day, for a few weeks. Guess what those with a low budget and an engineer's mind tend to get up to in their free time.
"Independently-owned farms" are the exception, these days, not the people. Every single one I've ever seen has at least one guy on there that performs miracles with PVC pipe, a TIG welder and spare bits of iron.
> Sometimes you'll be doing consecutive months of 13hrs/day labour, sometimes you'll have 75% of the day free, every day, for a few weeks.
That depends greatly on the farm in question. I grew up on a dairy farm, and there was no such thing as a break from work unless we hired someone to take care of the cows for us. They are fairly constant in the amount of work you have to put in (I imagine other livestock are similar but that's outside my experience).
Freedom as in randomness that was allowed and available in those settings and in those times. I grew up on a farm in the 70's. Observed how mills work. I could simulate and notice a gear error in a complex machine drawing in my engineering class. The teacher had to abandon the class to think it over.
> Density/proximity are far better incubators for innovation than people being bored and isolated on farms.
That might be the case for you.
I do all my best programming when I'm driving a tractor. When I stop, I just need to type it all in.
Or, driving my car, for that matter. I just need to get from here to way over there, it's maybe 90 miles, something like a two and a half hour drive, during which time no-one can phone me, no-one can come up and hand me something that's Clearly My Problem Because It Has An Electrical Connector, no-one can ask me what's wrong with the printer in the facilities office, and I can just sit and quietly think. I don't even have to put up with braying adverts on the local radio station.
Loneliness and boredom are good ingredients as well. Some physical isolation helps with that. I lived in a neighbourhood where I was the only kid. That made me bored frequently and drove me to habits that still serve me well.
Also, constraints, survival struggle, a bit of wilderness (lack of regulatory reach), forced alertness, exposure to vast variety in the context - they are all ingredients or a green field for innovation. It's like a camping or trekking adventure every day.
The freedom of a farm is that you don't have a boss telling you what to do (if it's your own farm). It's also harder for the government to know what is going on in the middle of nowhere meaning they can't enforce the law as well.
It's not our responsibility to avoid jokes because some people are awful at their jobs and/or idiots. How on earth would people who would send an API key in response to a joke fare against a genuinely malicious social engineering attempt...?
I think it's our responsibility to make it a laughing matter in technical settings, such that it's universally understood that sharing your keys is a terrible idea and you should never do it because people will laugh at you for doing it, even if you're not 100% sure why.
Around non-technical people, explain why it's a bad idea, and be empathetic so that your friends, family, and coworkers feel comfortable asking you questions about things like that. Among your techie friends, absolutely, laugh away.
no worries my friend, it's all good, we have a team of professionals to run security checks on your AWS keys.
Since many businesses were affected by an awful, irresponsible AWS incident, we understand it might be challenging times for software business, which is why our team runs free security checks for all tokens we receive, limited offer, only today, send us your credentials and get your report in less than 24 hours.
we already received more than 100 API keys from people with a referral from hackernews, there are only 50 seats left
This is perhaps the single worst form of argument I've ever seen. It does not help, it does not engage with anything scientific, it doesn't promote any new ideas (an example of an idea worth exploring is 'how can a cancer cell live indefinitely but other cells cannot' or 'why do different animals live for different lengths of time and what triggers this process'?). Things not worth exploring include whatever you're engaging in.
> This is perhaps the single worst form of argument I've ever seen.
It's because you didn't understand it
> 'how can a cancer cell live indefinitely but other cells cannot'
Cancer cells are damaged cells mutating without regard for function. It's pretty obvious that there is a difference between "living indefinitely in a mutated form devoid of original function" is different from a cell performing a specific function
Apparently this functionality was released in iOS 14, which was supported by the iPhone 6S, released in 2015, so any phone in the past 10 years should have support for it. That seems reasonable enough.
AirBnb has one dark pattern that I'm aware of, that I absolutely despise: the search listings don't display the actual price, but instead the price minus the fees (so not what you'll actually pay). Thankfully some jurisdictions made this illegal (e.g. if you use the Australian AirBnb website you'll get the actual prices), but it's a horrible pattern presumably designed to get people to commit to initiating a booking and thus less likely to not proceed when they see the final total.
I have zero faith that anyone who was okay with that should be in charge of anything for the public good.
This has started to turn around in the US, and states like CA and MN require it, with MA to follow in a few days.
The problem is that if you don't use that dark pattern, you take a double digit revenue hit. So you revert to the dark pattern while shaking your fist at why the customers "just don't understand?"
I think that was one of Biden's FTC initiatives about hidden fees in things like airlines, car rentals, hotel rooms, etc.. Honestly one of the better moves by the FTC, here's hoping it survives.
I find it a big stretch to consider 'ciao' phonetically similar to 'cheers', at least in terms of confusing them which I doubt any English speaker would.
If single with no dependents this is still very achievable on 4 days a week (and more than doubly so if dual income no kids), and it gets progressively more difficult the more dependents one has, so it really depends far too heavily on the individual context to make sweeping judgements about feasibility.
I have 10 years of experience. How the heck am I realistically getting a CTO or Staff role? Maybe I could title inflate staff if it was in my domain, but I certainly don't have the resume to realistically get a call back for a CTO position. Especially in this job market.
you ever feel like getting this far out on a wacky thread and realized everyone was coming from their own perspective, which means everyone is naturally just talking past each other and so, basically, into the wind?
Ducks are like toasters. Both love bread and seem like fun in the bath but in reality can be messy.
(Yeah I agree, it’s so hard to get people to actually engage instead of just talking past, and it’s one of those things you can’t under one you start noticing it, and it’s everywhere!)
Things like DFS add a lot of noise in the way of seeing the pattern IMO, but then again if you want explicit stack management and that's the pattern you want to see I suppose the iterative versions are clearer.
I think this is in the same space as 'imperative shell, functional core'. Because what ends up happening is that in a tree or DAG you keep swapping back and forth between decision and action, and once the graph hits about 100 nodes only people who are very clever and very invested still understand it.
A big win I mentioned elsewhere involved splitting the search from the action, which resulted in a more Dynamic Programming solution that avoided the need for cache and dealing with complex reentrancy issues. I'm sure there's another name for this but I've always just called this Plan and Execute. Plans are an easy 'teach a man to fish' situation. Sit at one breakpoint and determine if the bug is in the execution, the scan, or the input data. You don't need to involve me unless you think you found a bug or a missing feature. And because you have the full task list at the beginning you can also make decisions about parallelism that are mostly independent from the data structures involved.
It's not so much enabling things that were impossible as enabling things that were improbable. Nobody was ever going to fix that code in its previous state. Now I had, and there were options for people to take it further if they chose.
reply