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”
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
the goldberg-steamcrack supports multiplayer. https://gitlab.com/Mr_Goldberg/goldberg_emulator
I only tested it in lan, and it works great. Not sure if it works online, too. You may need hamachi.
And of course: online multiplayer with randos is probably not worth it, as others have pointed out. On one hands it’s probably a bitch to set up. On the other cheating is probably rampant.
who does the gene therapie work?
Do they inject mrna (like with the covid vaccine) or is there more going on?
the article is a little light on the technical details.
talking to clients
you want him to define features and deadlines?
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
source:
- Careful citation practices will build your credibility as a scientist or scholar.
https://falconediting.com/en/blog/6-reasons-why-citation-of-sources-is-important-when-writing/
providing source is good form in every context
============ 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
“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
is stateless possible without kubernetes? (and without vendor lock in?)
GP said:
RE: Containers, even if you DO go that route, do you really need Kubernetes, which will come at an additional monetary and also maintenance cost? The likely answer at least initially is a big fat “no”.
I agree, that good cloud engineers can save costs in the cloud. But I also think good non-cloud engineers, can save much much more.
When you are rewriting your entire stack to leverage cloud performance, you could probably spend a similar effort for a rewrite that increases regular performance by a similar factor.
RE: Containers, even if you DO go that route…
I was under the impression, that stateless stuff without containers requires a strong vendor login (aws lambda, google functions, azure function). Are you saying, I could do stateless without vendor-lockin and without containers and without kubernetes? This is news to me. Please point me to some resources
what does “get surprised on their own call” mean?
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?
inkscape is on a level with illustrator (maybe even better)
for drawing: try krita
if you want to pay money (much much less than for adobe): Affinity is on a level with fotoshop