1. Condene a agressão ilegal ao Irão por parte de Israel e dos Estados Unidos da América;
2. Proíba o uso de infraestruturas e do espaço aéreo português para qualquer tipo de apoio aos ataques;
3. Aplique sanções ao Estado de Israel pelas suas consecutivas violações do Direito Internacional e pelo genocídio em curso na Palestina;
4. Reconheça de imediato o Estado da Palestina.
Assina-se aqui: https://actionnetwork.org/forms/parar-a-guerra/
#Portugal #Israel #petição
1. Condene a agressão ilegal ao Irão por parte de Israel e dos Estados Unidos da América;
2. Proíba o uso de infraestruturas e do espaço aéreo português para qualquer tipo de apoio aos ataques;
3. Aplique sanções ao Estado de Israel pelas suas consecutivas violações do Direito Internacional e pelo genocídio em curso na Palestina;
4. Reconheça de imediato o Estado da Palestina.
Assina-se aqui: https://actionnetwork.org/forms/parar-a-guerra/
#Portugal #Israel #petição
1. Condene a agressão ilegal ao Irão por parte de Israel e dos Estados Unidos da América;
2. Proíba o uso de infraestruturas e do espaço aéreo português para qualquer tipo de apoio aos ataques;
3. Aplique sanções ao Estado de Israel pelas suas consecutivas violações do Direito Internacional e pelo genocídio em curso na Palestina;
4. Reconheça de imediato o Estado da Palestina.
Assina-se aqui: https://actionnetwork.org/forms/parar-a-guerra/
#Portugal #Israel #petição
@EsquerdaNet@EsquerdaNet https://masto.pt/@EsquerdaNet/114733876416292593
@EsquerdaNet@EsquerdaNet https://masto.pt/@EsquerdaNet/114733876416292593
@EsquerdaNet@EsquerdaNet https://masto.pt/@EsquerdaNet/114733876416292593
Blackberries going from red to black
Blackberries going from red to black
Blackberries going from red to black
pledge(…)/unveil(…)/landlock/capabilities I came across the great EWONTFIX blog, in particular this article here: https://ewontfix.com/17/ Super interesting.
pledge(…)/unveil(…)/landlock/capabilities I came across the great EWONTFIX blog, in particular this article here: https://ewontfix.com/17/ Super interesting.
Brilliant, sure, let's ignore existing definitions and go with gut feeling (incidently, Meta has a gut feeling generator).
Source: https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/14625-Apply-AI-Strategy-strengthening-the-AI-continent/F3563576_en
#OpenSource
Brilliant, sure, let's ignore existing definitions and go with gut feeling (incidently, Meta has a gut feeling generator).
Source: https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/14625-Apply-AI-Strategy-strengthening-the-AI-continent/F3563576_en
#OpenSource
Brilliant, sure, let's ignore existing definitions and go with gut feeling (incidently, Meta has a gut feeling generator).
Source: https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/14625-Apply-AI-Strategy-strengthening-the-AI-continent/F3563576_en
#OpenSource
returns tell me that you're not a real Rust programmer. :-D Personally, I would never omit them either. They make code 100 times more readable.
returns tell me that you're not a real Rust programmer. :-D Personally, I would never omit them either. They make code 100 times more readable.
I upcycled decades old table football aluminium pipes to become my handles. The spacers are made from the inner tube. Two minutes of handsanding with 400 grit sandpaper polished it up nicely.
Drawers on the workbenchhttps://lyse.isobeef.org/tmp/hobelbankschubladen/
I upcycled decades old table football aluminium pipes to become my handles. The spacers are made from the inner tube. Two minutes of handsanding with 400 grit sandpaper polished it up nicely.
Drawers on the workbenchhttps://lyse.isobeef.org/tmp/hobelbankschubladen/
https://abav.lugaralgum.com/material-aulas/Processing-Python-py5/comprehension.html
(preciso dar uma melhoradinha na página, por umas imagens, arrumar links quebrados) ![lista = [ f(x) for x in iteravel if cond(x) ]](https://media.ciberlandia.pt/ciberlandia-media/media_attachments/files/114/721/626/957/717/462/original/c91ee40155f8e9fd.png)
@urlyman@urlyman https://mastodon.social/@urlyman/114720462376167356 
@urlyman@urlyman https://mastodon.social/@urlyman/114720462376167356 
@urlyman@urlyman https://mastodon.social/@urlyman/114720462376167356 
We’re talking about this pattern, right?
f, err := os.Open("filename.ext")
if err != nil {
log.Fatal(err)
}
Nothing stops you from leaving out the
if, right? 🤔
We’re talking about this pattern, right?
f, err := os.Open("filename.ext")
if err != nil {
log.Fatal(err)
}
Nothing stops you from leaving out the
if, right? 🤔
!! was a sudo argument and never used it out of that context! Thanks for the $(!!) tip 🤘
https://racingbunny.com/@mookie/114718466149264471
> 18 rules of Software Engineering
>
> 0. You will regret complexity when on-call
> 1. Stop falling in love with your own code
> 2. Everything is a trade-off. There's no "best" 3. Every line of code you write is a liability 4. Document your decisions and designs
> 5. Everyone hates code they didn’t write
> 6. Don't use unnecessary dependencies
> 7. Coding standards prevent arguments
> 8. Write meaningful commit messages
> 9. Don't ever stop learning new things
> 10. Code reviews spread knowledge
> 11. Always build for maintainability
> 12. Ask for help when you’re stuck
> 13. Fix root causes, not symptoms
> 14. Software is never completed
> 15. Estimates are not promises
> 16. Ship early, iterate often
> 17. Keep. It. Simple.
Solid list, even though 14 is up for debate in my opinion: Software can be completed. You have a use case / problem, you solve that problem, done. Your software is completed now. There might still be bugs and they should be fixed – but this doesn’t “add” to the program. Don’t use “software is never done” as an excuse to keep adding and adding stuff to your code.
https://racingbunny.com/@mookie/114718466149264471
> 18 rules of Software Engineering
>
> 0. You will regret complexity when on-call
> 1. Stop falling in love with your own code
> 2. Everything is a trade-off. There's no "best" 3. Every line of code you write is a liability 4. Document your decisions and designs
> 5. Everyone hates code they didn’t write
> 6. Don't use unnecessary dependencies
> 7. Coding standards prevent arguments
> 8. Write meaningful commit messages
> 9. Don't ever stop learning new things
> 10. Code reviews spread knowledge
> 11. Always build for maintainability
> 12. Ask for help when you’re stuck
> 13. Fix root causes, not symptoms
> 14. Software is never completed
> 15. Estimates are not promises
> 16. Ship early, iterate often
> 17. Keep. It. Simple.
Solid list, even though 14 is up for debate in my opinion: Software can be completed. You have a use case / problem, you solve that problem, done. Your software is completed now. There might still be bugs and they should be fixed – but this doesn’t “add” to the program. Don’t use “software is never done” as an excuse to keep adding and adding stuff to your code.