Readit Newshttps://en.m.wikipedia.org/wiki/Ball_Aerospace_%26_Technolog...
The F-14's AI RIO "Jester" can actually guide you through startup, which is very cool
(It's been Janes-90s since I sim'd)
I think areas like that will see an uptick in interest from people who weren’t keen on an hour+ daily commute into a major city but are far more willing to consider it if you’re talking a few times a month.
Before we bought we looked around in a few cities and were really struck by the quality of life difference it makes when you drive occasionally but not by necessity. Even the younger residents in newer, pricier suburbs tend to pack on weight and health problems unless they’re absolutely rigorous about going to the gym and have the schedule to support it. The white-flight suburbs built in the decades after Brown v. Board are often actively hostile to a healthy lifestyle (no sidewalks, winding roads, transit happens in other zip codes).
Don't get me started on the folly of single-path, non-grid road planning. It's literally encoding the assumption "There will never be more than X people living here" into the city fabric.
And then in 10 years people wonder why traffic is so bad...
Deleted Comment
The most interesting idea is that its native data types are time series of integers, doubles, distributions of doubles, booleans, and tuples of the above. This means that the data you operate on intrinsically consist of many timestamped data points. It's easy to apply an operation to each point of the data, and it's also easy to apply operations on a rolling window, or on successive points. This makes the language have the feel of an array-based language, but even better because the elements are timestamped and the array can be sparse.
Furthermore the presence of fields in each data point adds more dimensions to the level of aggregation (not just the inherent time-based). Now the language has the feel of a native multi-dimensional array language. It feels amazing to program in it. You can easily do sophisticated queries like figuring out how many standard deviations each task's RPC latency for a specific call is above or below all tasks' mean, for outlier detection.
But I've found the previous to be right, more often than not.
Hope the inspiration helps you get out of your own way. :)
With the caveat that you should abandon things you've realized you don't value. I've seen far too many people spend too much time to "finish what they started" as a principle, even when they no longer valued the goal. Time is a zero sum game. All that time you spent on it is time you could have been spending on the other goals you have.
People like me have more goals than time. Gotta pick wisely.
> Any action is greater than no action. It doesn't matter how much you suck at something. Do it. Congrats, you've beaten everyone who never started.
Similar comment :-) Too many times in my life I was glad I didn't act (where all choices involving action would have led to negative consequences).
> That's not who you're competing against. You're competing against the pool of real people a company / project could afford to hire, who are available to hire.
Depends on your goals. For most of my projects, I'm competing with myself, not with others.
Effect of Exercise-Related Factors on the Perception of Time (frontiersin.org) 65 points, 9 days ago | 9 comments
Because if not, while walks are nice, my goal isn't exactly to have twice as long of a subjective experience but 60% of it is parks.
Spending time in nature essentially jumped your brain out of the loop, even after you returned from nature.
Think it might have been a summary of this: "Awe Expands People’s Perception of Time, Alters Decision Making, and Enhances Well-Being" (2012)
The real issue is that the engineering team who maintains the internal app checking system 1. needs to have infrastructure to detect abnormal amount of a given error and 2. need to notify the QA team so the QA team can communicate it with the devs, rather than just blaming the apps.
One of which should maybe be "Don't strictly isolate teams, with unowned space between their output and the next team's input, and no method by which post-delivery failure reflects back on them."