is it still owned by tencent?

why not have a single global timezone and people change their local numbers.

e.g. if you life in hawaii you stand up at 11pm and if people in russia work until 8am.

because of two bodies can not occupy the same space, the feather and the ball will be in different position when you drop them. And therefor gravitation will pull the earth slightly more toward the ball and slightly less toward the feather.

I like the explanation that devious spirits cannot say this phrase and that’s why it’s used

Evil spirits can not say the same word twice in a row. Foxes can not say “moshi”. With “moshi moshi” you get a 2-for-1 special.

what are you going to do when there’s night

sleep

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

Only reason to include 2 full bridge rectifiers

they look like runes.

. 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.

However you will now have rodent problems

chicken got you covered on that front too https://www.youtube.com/watch?v=iubf1oJdQQQ

============ 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

https://gist.github.com/thom-nic/2c74ed4075569da0f80b

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

[2] https://blog.pragmaticengineer.com/tech-debt/

deleted by creator

https://www.youtube.com/watch?v=ne6nj9AgY7M

I use like 3 of the git-feature from intellij (out of 100 or so). But these 3 features save me a lot of time.

(the other 2 being the 3-way-merge-view and the commit-view where I can select changes for staging)

why would rebasing a feature branch change main?

the image does not update the feature branch. It merges the featurebranch into main with a regular old merge-commit on the main branch.

Another advice …quick way to squash all your commits

in your IDE select the commits you want to squash. Then rightclick. Then “squash”. All done.