@erlendaasland hvis du har en arbeidsflyt der du kjører alle endringer via PR så har du ikke kontinuerlig integrasjon. Koden blir ikke integrert i main før du har gått gjennom en manuell prosess. Det er det motsatte av kontinuerlig integrasjon.
@glenjamin yes, everything goes directly to production. Since this happens many times per day it becomes less scary, and mostly problems are easily correlated with very few commits. Highly recommended!
Hvorfor har det blitt så populært å jobbe med pull requester når vi vet at kontinuerlig integrasjon gir økt kvalitet? Jeg har skrevet litt om hvorfor jeg mener PRs er en dårlig match for teamarbeid https://parenteser.mattilsynet.io/pull-requests/
@lettosprey @forteller for noe rør. Jeg kjører fra sone 2S. Selv med 4 dager på kontoret i uka (vanlig uke, av og til færre) er månedskort dyrere enn reis...
@forteller hva, skal de kutte ut rabatten? 🤬
A very Norwegian defn #clojure episode with @magnars and @christian is out
You don't have to rewrite your apps every 3-5 years. You just need to design it with some care. I recently gave a presentation about the architecture that helped our frontend codebase stay in kick ass shape, even after 9 years of continuous work: https://vimeo.com/861600197
@headius it was very interesting and well presented, thanks!
In response to Google's monopolistic implementation of Web Environment Integrity, I have a modest proposal:
Open source JavaScript libraries should add bugs which only occur when they find "navigator.getEnvironmentIntegrity" is being used.
Go into a "while(true)" loop. Start throwing exceptions randomly. Just fuck up the page. Make the lives of every developer who is in the origin trial who uses your library completely miserable.
If they want to fork, they have the freedom to do so. But then they're taking on the maintenance that they would prefer to outsource to their community.
If you have enough big libraries doing this, it might make a dent.
@arnemart venner? Altså, ølet?
Twitter is now paying people to spread hate
Reminder: if you’re still on Twitter—your presence and your interactions generate revenue. You’re literally funding the alt right.
🏳️⚧️🏳️🌈🇺🇸
Hvis du lurte på hvordan du kan lage din egen lille logg-løsning uten å bryte GDPR så har @christian fortalt litt om hvordan det kan gjøres for web https://www.kodemaker.no/blogg/2023-07-send-beacon/
Hiring a software engineer in their late 40s:
Pros:
* Understands your stack better than you do after glancing through the repo for five minutes.
* Will rewrite said stack 2x as fast, and half as buggy if you let them.
Cons:
* Gives zero fucks.
* Knows we're not *really* like family here.
* No, seriously, absolutely zero fucks given.
Do not cite the deep magic to me, product manager, I was there when it was written.
@bitbear Yes, someone within the team needs to have the overview - the more the better. I agree with this. Sounds like you agree with me: architecture is a development consideration - a role, not a position.
@craignicol I strongly disagree that someone who only knows Terraform and OpenAPI can make meaningful decisions about software architecture.
I et helt år har @christian og jeg kodet et spill for åpen skjerm på https://www.zombieclj.no. Det endte opp med 53 episoder av ca 15 minutter, og et lite spill som faktisk funker. Veldig artig! 😄 Hvis du ikke er så opptatt av kodingen, men har lyst til å se hvordan spillet ble, så lenker jeg direkte til den avsluttende spillrunden her: https://youtu.be/T6ISsje30vQ?t=714
I play guitar and board games, I write Clojure for work and fun, and I bake bread, cook and occasionally brew beer.