#softwareverification — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #softwareverification, aggregated by home.social.
-
"Can we prove that Signal's cryptography is secure — not just on paper, but in actual code?"
Signal Shot, launched today at the Software Verification in Lean workshop in Paris, is a public moonshot to formally verify the Signal protocol and its Rust implementation using Lean. A joint effort of Signal, the Beneficial AI Foundation, and the Lean FRO.
Open to contributions from anyone working on software verification, cryptography, protocol design, Rust, or Lean.
-
"Can we prove that Signal's cryptography is secure — not just on paper, but in actual code?"
Signal Shot, launched today at the Software Verification in Lean workshop in Paris, is a public moonshot to formally verify the Signal protocol and its Rust implementation using Lean. A joint effort of Signal, the Beneficial AI Foundation, and the Lean FRO.
Open to contributions from anyone working on software verification, cryptography, protocol design, Rust, or Lean.
-
"Can we prove that Signal's cryptography is secure — not just on paper, but in actual code?"
Signal Shot, launched today at the Software Verification in Lean workshop in Paris, is a public moonshot to formally verify the Signal protocol and its Rust implementation using Lean. A joint effort of Signal, the Beneficial AI Foundation, and the Lean FRO.
Open to contributions from anyone working on software verification, cryptography, protocol design, Rust, or Lean.
-
"Can we prove that Signal's cryptography is secure — not just on paper, but in actual code?"
Signal Shot, launched today at the Software Verification in Lean workshop in Paris, is a public moonshot to formally verify the Signal protocol and its Rust implementation using Lean. A joint effort of Signal, the Beneficial AI Foundation, and the Lean FRO.
Open to contributions from anyone working on software verification, cryptography, protocol design, Rust, or Lean.
-
"Can we prove that Signal's cryptography is secure — not just on paper, but in actual code?"
Signal Shot, launched today at the Software Verification in Lean workshop in Paris, is a public moonshot to formally verify the Signal protocol and its Rust implementation using Lean. A joint effort of Signal, the Beneficial AI Foundation, and the Lean FRO.
Open to contributions from anyone working on software verification, cryptography, protocol design, Rust, or Lean.
-
Our department is hiring an assistant professor in computer science (including programming languages). If you would like to join our small but diverse PL group in beautiful little Delft, please don't hesitate to apply! Also feel free to reach out to me if you want to know anything about our department or academic life in the Netherlands.
Deadline for applications: 11th of May
academictransfer.com/en/jobs/360114/assistant-professor-in-computer-science/
#TUDelft #AssistantProfessor #Hiring #ComputerScience #SoftwareTechnology #ProgrammingLanguages #TypeTheory #SoftwareVerification #Agda #Rocq -
Our department is hiring an assistant professor in computer science (including programming languages). If you would like to join our small but diverse PL group in beautiful little Delft, please don't hesitate to apply! Also feel free to reach out to me if you want to know anything about our department or academic life in the Netherlands.
Deadline for applications: 11th of May
academictransfer.com/en/jobs/360114/assistant-professor-in-computer-science/
#TUDelft #AssistantProfessor #Hiring #ComputerScience #SoftwareTechnology #ProgrammingLanguages #TypeTheory #SoftwareVerification #Agda #Rocq -
Our department is hiring an assistant professor in computer science (including programming languages). If you would like to join our small but diverse PL group in beautiful little Delft, please don't hesitate to apply! Also feel free to reach out to me if you want to know anything about our department or academic life in the Netherlands.
Deadline for applications: 11th of May
academictransfer.com/en/jobs/360114/assistant-professor-in-computer-science/
#TUDelft #AssistantProfessor #Hiring #ComputerScience #SoftwareTechnology #ProgrammingLanguages #TypeTheory #SoftwareVerification #Agda #Rocq -
Our department is hiring an assistant professor in computer science (including programming languages). If you would like to join our small but diverse PL group in beautiful little Delft, please don't hesitate to apply! Also feel free to reach out to me if you want to know anything about our department or academic life in the Netherlands.
Deadline for applications: 11th of May
academictransfer.com/en/jobs/360114/assistant-professor-in-computer-science/
#TUDelft #AssistantProfessor #Hiring #ComputerScience #SoftwareTechnology #ProgrammingLanguages #TypeTheory #SoftwareVerification #Agda #Rocq -
Our department is hiring an assistant professor in computer science (including programming languages). If you would like to join our small but diverse PL group in beautiful little Delft, please don't hesitate to apply! Also feel free to reach out to me if you want to know anything about our department or academic life in the Netherlands.
Deadline for applications: 11th of May
academictransfer.com/en/jobs/360114/assistant-professor-in-computer-science/
#TUDelft #AssistantProfessor #Hiring #ComputerScience #SoftwareTechnology #ProgrammingLanguages #TypeTheory #SoftwareVerification #Agda #Rocq -
Third up: the experience report "Teaching Software Specification" by Cameron Moy and Daniel Patterson. This paper makes the provocative but very good point that (at least) some courses on software verification could actually benefit by teaching formal *specification* instead. I found section 7 (interviews with students who took two very different versions of their course) particularly interesting. I just might have to make some changes to my FP course based on this.
(Also I was glad to see the work of @sarantja on teaching theorem provers getting a mention here!)
dl.acm.org/doi/10.1145/3747533
#SoftwareVerification #SoftwareSpecification #Education -
Third up: the experience report "Teaching Software Specification" by Cameron Moy and Daniel Patterson. This paper makes the provocative but very good point that (at least) some courses on software verification could actually benefit by teaching formal *specification* instead. I found section 7 (interviews with students who took two very different versions of their course) particularly interesting. I just might have to make some changes to my FP course based on this.
(Also I was glad to see the work of @sarantja on teaching theorem provers getting a mention here!)
dl.acm.org/doi/10.1145/3747533
#SoftwareVerification #SoftwareSpecification #Education -
Third up: the experience report "Teaching Software Specification" by Cameron Moy and Daniel Patterson. This paper makes the provocative but very good point that (at least) some courses on software verification could actually benefit by teaching formal *specification* instead. I found section 7 (interviews with students who took two very different versions of their course) particularly interesting. I just might have to make some changes to my FP course based on this.
(Also I was glad to see the work of @sarantja on teaching theorem provers getting a mention here!)
dl.acm.org/doi/10.1145/3747533
#SoftwareVerification #SoftwareSpecification #Education -
Third up: the experience report "Teaching Software Specification" by Cameron Moy and Daniel Patterson. This paper makes the provocative but very good point that (at least) some courses on software verification could actually benefit by teaching formal *specification* instead. I found section 7 (interviews with students who took two very different versions of their course) particularly interesting. I just might have to make some changes to my FP course based on this.
(Also I was glad to see the work of @sarantja on teaching theorem provers getting a mention here!)
dl.acm.org/doi/10.1145/3747533
#SoftwareVerification #SoftwareSpecification #Education -
Third up: the experience report "Teaching Software Specification" by Cameron Moy and Daniel Patterson. This paper makes the provocative but very good point that (at least) some courses on software verification could actually benefit by teaching formal *specification* instead. I found section 7 (interviews with students who took two very different versions of their course) particularly interesting. I just might have to make some changes to my FP course based on this.
(Also I was glad to see the work of @sarantja on teaching theorem provers getting a mention here!)
dl.acm.org/doi/10.1145/3747533
#SoftwareVerification #SoftwareSpecification #Education -
I cannot get enough of our shared Vulgar Technobabble that we #ComputerScientists speak. Even #ACM #TuringAward winning blokes speak this way.🤣
Interviewer—What is a good way to understand what #ModelChecking is and what it does?
#AllenEmerson—[staring intently at his toes] Well, uh, in "layman's terms", model checking is an algorithmic method of verifying correctness of nominally finite state systems, uh, against a specification that's typically given in temporal logic. Uh, if the model checker, the model checking tool that's been implemented, uh, returns "yes", then the system is correct. If it, uh, returns "no", the specification is violated, and a counterexample is produced.
Sure, we get it; it is but #SoftwareVerification in so many words. But does a "layman" get it?
-
I cannot get enough of our shared Vulgar Technobabble that we #ComputerScientists speak. Even #ACM #TuringAward winning blokes speak this way.🤣
Interviewer—What is a good way to understand what #ModelChecking is and what it does?
#AllenEmerson—[staring intently at his toes] Well, uh, in "layman's terms", model checking is an algorithmic method of verifying correctness of nominally finite state systems, uh, against a specification that's typically given in temporal logic. Uh, if the model checker, the model checking tool that's been implemented, uh, returns "yes", then the system is correct. If it, uh, returns "no", the specification is violated, and a counterexample is produced.
Sure, we get it; it is but #SoftwareVerification in so many words. But does a "layman" get it?
-
I cannot get enough of our shared Vulgar Technobabble that we #ComputerScientists speak. Even #ACM #TuringAward winning blokes speak this way.🤣
Interviewer—What is a good way to understand what #ModelChecking is and what it does?
#AllenEmerson—[staring intently at his toes] Well, uh, in "layman's terms", model checking is an algorithmic method of verifying correctness of nominally finite state systems, uh, against a specification that's typically given in temporal logic. Uh, if the model checker, the model checking tool that's been implemented, uh, returns "yes", then the system is correct. If it, uh, returns "no", the specification is violated, and a counterexample is produced.
Sure, we get it; it is but #SoftwareVerification in so many words. But does a "layman" get it?
-
I cannot get enough of our shared Vulgar Technobabble that we #ComputerScientists speak. Even #ACM #TuringAward winning blokes speak this way.🤣
Interviewer—What is a good way to understand what #ModelChecking is and what it does?
#AllenEmerson—[staring intently at his toes] Well, uh, in "layman's terms", model checking is an algorithmic method of verifying correctness of nominally finite state systems, uh, against a specification that's typically given in temporal logic. Uh, if the model checker, the model checking tool that's been implemented, uh, returns "yes", then the system is correct. If it, uh, returns "no", the specification is violated, and a counterexample is produced.
Sure, we get it; it is but #SoftwareVerification in so many words. But does a "layman" get it?
-
I cannot get enough of our shared Vulgar Technobabble that we #ComputerScientists speak. Even #ACM #TuringAward winning blokes speak this way.🤣
Interviewer—What is a good way to understand what #ModelChecking is and what it does?
#AllenEmerson—[staring intently at his toes] Well, uh, in "layman's terms", model checking is an algorithmic method of verifying correctness of nominally finite state systems, uh, against a specification that's typically given in temporal logic. Uh, if the model checker, the model checking tool that's been implemented, uh, returns "yes", then the system is correct. If it, uh, returns "no", the specification is violated, and a counterexample is produced.
Sure, we get it; it is but #SoftwareVerification in so many words. But does a "layman" get it?
-
Creating a new #introduction, since life changes. For 12 years I was a #SoftwareEngineer at Google, working predominantly on #EngineeringProductivity. Now I’m at smaller startup doing smaller-startup things. My Ph.D. is in #SoftwareVerification.
I stopped really posting on Twitter eight years before moving to Mastodon, so I’m a little rusty and tend to fall out of it from time to time.
I continue to forecast that my posts will soon be all #beagle, all the time.
-
Creating a new #introduction, since life changes. For 12 years I was a #SoftwareEngineer at Google, working predominantly on #EngineeringProductivity. Now I’m at smaller startup doing smaller-startup things. My Ph.D. is in #SoftwareVerification.
I stopped really posting on Twitter eight years before moving to Mastodon, so I’m a little rusty and tend to fall out of it from time to time.
I continue to forecast that my posts will soon be all #beagle, all the time.
-
Creating a new #introduction, since life changes. For 12 years I was a #SoftwareEngineer at Google, working predominantly on #EngineeringProductivity. Now I’m at smaller startup doing smaller-startup things. My Ph.D. is in #SoftwareVerification.
I stopped really posting on Twitter eight years before moving to Mastodon, so I’m a little rusty and tend to fall out of it from time to time.
I continue to forecast that my posts will soon be all #beagle, all the time.
-
Creating a new #introduction, since life changes. For 12 years I was a #SoftwareEngineer at Google, working predominantly on #EngineeringProductivity. Now I’m at smaller startup doing smaller-startup things. My Ph.D. is in #SoftwareVerification.
I stopped really posting on Twitter eight years before moving to Mastodon, so I’m a little rusty and tend to fall out of it from time to time.
I continue to forecast that my posts will soon be all #beagle, all the time.
-
Creating a new #introduction, since life changes. For 12 years I was a #SoftwareEngineer at Google, working predominantly on #EngineeringProductivity. Now I’m at smaller startup doing smaller-startup things. My Ph.D. is in #SoftwareVerification.
I stopped really posting on Twitter eight years before moving to Mastodon, so I’m a little rusty and tend to fall out of it from time to time.
I continue to forecast that my posts will soon be all #beagle, all the time.
-
@modulux Based on our conversation above, you might be interested in this:
An experimental programming language for ergonomic software verification
-
@modulux Based on our conversation above, you might be interested in this:
An experimental programming language for ergonomic software verification
-
@modulux Based on our conversation above, you might be interested in this:
An experimental programming language for ergonomic software verification
-
@modulux Based on our conversation above, you might be interested in this:
An experimental programming language for ergonomic software verification
-
@modulux Based on our conversation above, you might be interested in this:
An experimental programming language for ergonomic software verification