the other stuff isn’t too wild either.
the other stuff isn’t too wild either.
if you just want to make a simple program. It still needs to run in kubernetes.
“hello OPS-team. Here is my simple program. Have fun running it on your kubernetes”
It’s at most 40 years old technolog
the 60s were 60 years ago
. But it is trained well enough to correlate left and right together
eliza could do that 60 years ago
But only temporarily
but is it?
I thought the temporal improvement would be for everyone who already used the high way (because they will get to their destination a little bit faster). And for the few extra people, who start to use the highway but didn’t use it before, the improvment will stay.
When you add a new lane to a road, people think that the traffic will be easier there, so they take that route instead of their normal one
so for these people the new lane will create marginal improvement, right?
However you will now have rodent problems
chicken got you covered on that front too https://www.youtube.com/watch?v=iubf1oJdQQQ
soft failures add complexity and ambiguity to your system, as it creates many paths and states you have to consider. It’s generally a good idea to keep the exception handling simple, by failing fast and hard.
here is a nice paper, that highlights some exception handling issues in complex systems
https://www.usenix.org/system/files/conference/osdi14/osdi14-paper-yuan.pdf
============ Top 5: =============== HasThisTypePatternTriedToSneakInSomeGenericOrParameterizedTypePatternMatchingStuffAnywhereVisitor: 97
AbstractAnnotationConfigDispatcherServletInitializer: 52
AbstractInterruptibleBatchPreparedStatementSetter: 49
AbstractInterceptorDrivenBeanDefinitionDecorator: 48
GenericInterfaceDrivenDependencyInjectionAspect: 47
============ Factories: ===============
DefaultListableBeanFactory$DependencyObjectFactory
ObjectFactoryCreatingFactoryBean
SimpleBeanFactoryAwareAspectInstanceFactory
SingletonBeanFactoryLocator$BeanFactoryGroup
ConnectionFactoryUtils$ResourceFactory
DefaultListableBeanFactory$DependencyProviderFactory
ObjectFactoryCreatingFactoryBean$TargetBeanObjectFactory
JndiObjectFactoryBean$JndiObjectProxyFactory
DefaultListableBeanFactory$SerializedBeanFactoryReference
AbstractEntityManagerFactoryBean$SerializedEntityManagerFactoryBeanReference
BeanFactoryAspectInstanceFactory
SingletonBeanFactoryLocator$CountingBeanFactoryReference
TransactionAwarePersistenceManagerFactoryProxy$PersistenceManagerFactoryInvocationHandler
AbstractEntityManagerFactoryBean$ManagedEntityManagerFactoryInvocationHandler
the fact that a system eventually becomes complex and flawed is not due to engineering failures - it is inherent in the nature of changing systems
it is not. It’s just that there will be some point, where you need significant effort to keep the systems structure up to the new demands {1}. I find the debt-metaphor is quite apt [2]: In your scenario the debt accumulates until it’s easier to start fresh. But you can also manage your debt and keep going indefinitily. But in contrast to financial debt, paying of technical debt is much less obvious. First of all it is pretty much impossible to put any kind of exact number on it. On the other hand, it’s very hard to tell what you actually should do to pay it off. (tangent: This is why experienced engineers are worth so much: (among other things) they have seen how debt evolves over time, and may see the early signs).
[1] https://tidyfirst.substack.com/p/the-openclosedopen-principle
There are many “visual tropes” like this. When I am watching anime with friends, we like to call them out. We even made a bingo at one time for re-occuring tropes.
There’s another one of characters holding a sword with a super exaggerated perspective so the tip is close to camera and the character is farther away
That’s sunrise stance
some others are
There is also a big list at tvtropes (not all anime though) https://tvtropes.org/pmwiki/pmwiki.php/Main/StockPoses
“sudo MacOS” sounds like a legit way to describe “gnome+ubuntu”
KDE on steamdeck, because it came preinstalled
Gnome on work-pc, because it came preinstalled
also gnome on notebook, because the multi-workspace thing works very nice OOTB in gnome
One’s an active decision
There are not so many quality notebooks without any brand-logos on them.
Also wearing a brand-logo when you have the choice not to, is kinda cringe.
Because megacorps are at least “smart enough” to pretend they aren’t trying to take over the world.
there are enough examples for corps doing evil things. You hear about them less often, because they cover their tracks and the outcry is generally smaller than when governments do similar things.
Whereas governments have a tendency to justify a lot of horrible shit for righteous reasons.
corps justify a lot of horribble shit for financial reasons. Is that better?
who else should be a significant backer for an open source project? google? microsoft?
is it still owned by tencent?