weird life

 yep again mentioned about c++ library challenges as usual.    its like blogging to other engineers hey this were this much challenging! (since this c++ coder is not knowledged in c++) that i blog alot every time.    (my blog has partial sectuons whihc i blog to other software engineers which is about all coding either spark/c++/flink whatever or category theory or sage whatever its coded. and its usually about something like, gosh come on, tjhis were utter hard! challenging!  alike blogging:S since i am usually solo developer i need to tell how hard it were to develop these projects i code. solo development challenges. so i need some technical blog time to mention come on this is utter hard! i mean coding challenges. either its sage or coq or nlp translation of a 100gb enclylopedia of ttl to parquets in a single computer :S) its always a quite challenge to do coding challenges and there is blog parts in my blog which i blog to software engineer people...

 yep time to study to projects then to resume ml algos and qft shield of lands project, yep. 

 yep i been working to complete code project to resume the ml algos project to implement develop the initial project (qft shield project)  asap.     so in today's coding task work, I been working to first complete the library then would switch to plugin tasks afterwards.  yep now coding time. 

 hmm i think quantum error correcting news i saw seems correct as because you can possibly reduce the measurment effect's side effect to equation with reducing its factor out.  i dont think there is something like decoherence at all i mean of course a qubit could decohere but its default existnece is actually in its universe thread superposition. its that when it decoheres its the moment its thread is on an alternate thread.  and but the original thread also exists.  so reason why alternate thread is because due to possibly entropy principles. but again, you can assure that does happen very low frequently with setting up additional bits around   qubits thats strengthen its thread condition that you compute in such thread version still. so error correction means making the compute happening thread stay in same thread. and thats possible to strengthen it mathematically (aka error correction by design of thread stability of compute universe) yep as soon as...

 and some example from webrtc dll library: bool WebRTCMain::init() {     // Using Google's STUN server.     webrtc::PeerConnectionInterface::IceServer ice_server;     ice_server.uri = "stun:stun.l.google.com:19302";     configuration.servers.push_back(ice_server);     network_thread = rtc::Thread::CreateWithSocketServer();     network_thread->Start();     worker_thread = rtc::Thread::Create();     worker_thread->Start();     signaling_thread = rtc::Thread::Create();     signaling_thread->Start();     webrtc::PeerConnectionFactoryDependencies dependencies;     dependencies.network_thread = network_thread.get();     dependencies.worker_thread = worker_thread.get();     dependencies.signaling_thread = signaling_thread.get();     peer_connection_factory = webrtc::CreateModularPeerConnectionFactory(std::move(dependencies));  ...

 and some example from python http server side implementing deltalake db service:         @retry(Exception, tries= 5 , delay= 1 , backoff= 2 )     def retrieve_ongoing_game_data(self, username,  game_version):         dt = DeltaTable( self .basecreatedb.usersdbpathforgame, storage_options=GameDB.so)         uid = str(mmh3.hash128(username))                 ds = dt.to_pyarrow_dataset()                   tables = []         condition = (dspy.field( "userid" ) == uid) & (         dspy.field( "cur_game_version" ) == game_version)           batch_iter = ds.to_batches(filter=condition, batch_size= 1 )         for batch in batch_iter:             tables.append(batch.to_pandas())         ...