Jarkko Sakkinen
Posts
5063Following
330Followers
505OpenPGP: 3AB05486C7752FE1
Jarkko Sakkinen
jarkko
Edited 1 year ago
All my quantum knowledge is based on
1. Physics lab exercises while studying for my MSc (back in the day).
2. Applying numerical methods to cost functions while studying for my MSc.
3. Quantum Computing at https://brilliant.org/
I thought that since I'm ultimately stupid in this topic and want to get the gist of it, Brilliant was exactly in my level :-) It really helped me to get the gist of the topic by combining it to my knowledge of stuff that I learned while studying ages ago at a polytechnic university.
Can highly recommend that course!
And can highly also recommend studying topics that you suck at, not ones that you're good at. It is refreshing!
#brilliant #quantum #computing
1. Physics lab exercises while studying for my MSc (back in the day).
2. Applying numerical methods to cost functions while studying for my MSc.
3. Quantum Computing at https://brilliant.org/
I thought that since I'm ultimately stupid in this topic and want to get the gist of it, Brilliant was exactly in my level :-) It really helped me to get the gist of the topic by combining it to my knowledge of stuff that I learned while studying ages ago at a polytechnic university.
Can highly recommend that course!
And can highly also recommend studying topics that you suck at, not ones that you're good at. It is refreshing!
#brilliant #quantum #computing
0
0
0
Don't let the physics scare you away, it is irrelevant for a developer. Understanding the latest developments on how the circuit is cooled down near zero Kelvin plays no role on understanding how to program these bastards. Hardware construction is irrelevant.
0
0
0
Jarkko Sakkinen
jarkko
If you have gone through a basic lab course e.g. in a polytechnic university AND know how to re-formalize an algorithm as a cost function, and apply numerical methods for that, you already have the basic theoretical and practical experience on how to program quantum computers.
That's roughly all there is to it.
#quantum #computing
That's roughly all there is to it.
#quantum #computing
1
0
0
Jarkko Sakkinen
jarkko
Have some catching up to do with #LKML as I was going to job interviews last week and did not have energy to do much else. Also need to some bug fixes to Linus for 5.11.
Anyway I accepted an offer with all the usual suspect hype words except AI: Rust, RISC-V and blockchains ;-) More on that later...
Anyway I accepted an offer with all the usual suspect hype words except AI: Rust, RISC-V and blockchains ;-) More on that later...
0
0
2
Jarkko Sakkinen
jarkko
Edited 1 year ago
The upstream patch that fixes my recent mbsync issues in Fedora is ceb0fa980
[1] https://sourceforge.net/p/isync/patches/19/
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2302132
#fedora #bug #triage
[1] https://sourceforge.net/p/isync/patches/19/
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2302132
#fedora #bug #triage
0
0
2
This text is weird tho: "Verso is a web browser built on top of Servo web engine. It's still under development. We don't accept any feature request at the moment. But if you are interested, feel free to help test it."
Not going test it. I wait until it is finished ;-) I've never used a software in my life that was finished, so this would be the first time ever.
Not going test it. I wait until it is finished ;-) I've never used a software in my life that was finished, so this would be the first time ever.
1
0
0
Jarkko Sakkinen
jarkko
Looking at delays among different CPU and chip companies (not just Intel), maybe there's a CPU bubble coming too in the timeline (long projection)?
E.g. Spectre and its ancestors are so fundamentals flaws in the core design decisions of a CPU that I don't think they will be ever fully fixed in ARM and x86.
E.g. Spectre and its ancestors are so fundamentals flaws in the core design decisions of a CPU that I don't think they will be ever fully fixed in ARM and x86.
1
0
0
Jarkko Sakkinen
jarkko
@hcmh Also you have to seek a cli for running CI changes locally.
To make things worse, none of them are supported by the main project so you have to got to a treasure hunt in order find one.
Something like librunner-ci and runner-ci would be best I.e. runner services can call the API and runner-ci implement command -line application for running a CI job using librunner-ci, which has a dual function as a reference implemention for runner services adding heir adaptation.
To make things worse, none of them are supported by the main project so you have to got to a treasure hunt in order find one.
Something like librunner-ci and runner-ci would be best I.e. runner services can call the API and runner-ci implement command -line application for running a CI job using librunner-ci, which has a dual function as a reference implemention for runner services adding heir adaptation.
0
0
0
Jarkko Sakkinen
jarkko
@unfa @BrodieOnLinux Tapes are used also for enterprise long-term backup because of durability. Life-times span in the range of 30-50 years or similar figures (when stored in appropriate temperature range etc. conditions).
0
0
0
Jarkko Sakkinen
jarkko
zkVM is a cool project: https://dev.risczero.com/api/zkvm/
Requires quite selective use tho because it does not scale that well.
#riscv #zkvm
Requires quite selective use tho because it does not scale that well.
#riscv #zkvm
0
0
0
Jarkko Sakkinen
repeated
repeated
Signal
signalapp@mastodon.worldWe're aware of reports that access to Signal has been blocked in some countries. As a reminder, Signal's built-in censorship circumvention feature might be able to help if your connection is affected:
Signal Settings > Privacy > Advanced > Censorship circumvention (on)
1
21
1
Jarkko Sakkinen
jarkko
Act is different same as github-ci-local for Github: https://github.com/nektos/act
0
0
0
Jarkko Sakkinen
jarkko
Edited 1 year ago
Containers cross-talk in standards and even share sub-projects. CI's don't.
I think we as an industry could take the quantum leap and define standard for something like ".runner-ci.yml", and when split to multiple files ".runner-ci.d/*.yml". Then, just define stages and tasks.
That would also fix migration between hosts for Git repositories. Also, in a private company internal CI and external CI can sometimes be different. Only way to address is to support both, which is redundant work.
I think we as an industry could take the quantum leap and define standard for something like ".runner-ci.yml", and when split to multiple files ".runner-ci.d/*.yml". Then, just define stages and tasks.
That would also fix migration between hosts for Git repositories. Also, in a private company internal CI and external CI can sometimes be different. Only way to address is to support both, which is redundant work.
1
1
1
Jarkko Sakkinen
repeated
repeated
DCoder 🇱🇹❤🇺🇦
dcoderlt@ohai.social
Edited 1 year ago
Amazing work, @ryanc !
Edit: Direct link to Ryan’s write-up: https://rya.nc/vpp-hack.html
0
5
1