Når 2025 begynner - hvem tar på seg jobben med å summere hvor mange skoler, "gamlehjem", og barne- og ungdomstiltak som har blitt ofret til sparesablene i landets kommuner?
Vil ha antall, og summer - any takers?😅
#BudsjettNorge2025
INEOS publicly said it would take 2-3 years to get the conditions right for a manager to succeed.
It seems that some of you heard that as "we'll get 2-3 new signings in the summer and we'll suddenly be mint again"...
Adjust your expectations.
#MUFC 🔴🙏
PayPal is updating their ToS to let themselves give your data to merchants starting Nov & they're banking on people not knowing to opt out, SO to opt out before they start: go to Settings >Data & Privacy > Manage shared info >Personalized shopping, & toggle that shit off
Here's the truth about TDD (Test Driven Development).
It's a broken practice. It's always been broken. It's broken by the definition of it. Its biggest merit is the encouragement of testing but that's about where it ends.
TDD implies writing tests before writing the code. So, what's broken about this, Artem? You write tests to describe the intention behind the system—how you expect it to behave. TDD heavily implies that you should know how the system behaves before even implementing it. You should know what you're doing.
Most of the time you don't. All the developers I know don't know that ahead of time. I don't know that ahead of time. In fact, I can spend days experimenting, writing an MVP, until I even begin to grasp what parts of my system should be and what I expect from them.
I don't see TDD as a viable approach in fast-evolving systems, like the web. It may make significantly more sense when writing systematic software where very little changes from project to project. That's the complete opposite of what you write on the web.
The negative aspect of TDD is that I've seen teams discouraged if they fail to follow it. And so they give up on the whole idea of testing since TDD is so universally associated with it. Instead of encouraging people to test and showing them that testing software can be fun, the practice locks them in pedantic constraints that no engineer can follow.
I don't follow TDD. It doesn't mean I don't write tests. I write a lot of tests. What I do is Prototype-Iterate-Test development.
Prototype. I give my ideas some room and let them breathe without caring too much about testing at first. I experiment, move things, break things, put myself in my user's shoes and design the API, behaviors, and expectations. As I said, this can take some time.
Iterate. I take that time to make sure my system makes sense and satisfies the requirements toward it (which, by themselves, may evolve and change why I do this).
Test. Finally, I write the tests. It's become an inseparable part of my workflow. I cannot imagine not writing tests.
There are exceptions, of course. If I'm writing a simple I/O function, it doesn't need a day of work to understand what it does because that's all it will ever do. I may write some unit tests for it from the start. But the majority of my (and I'm sure yours too) work are not simple functions. It's complex logic that takes time to get right. If I follow TDD faithfully, I will be wasting my time writing tests that I will, eventually, throw away. Those are not useful and they'd help me not to gain confidence in what I'm building.
Don't be discouraged. Adopt the practices that work for you (even if it's TDD, as long as you are not lying to yourself!). The important thing is that testing matters. It always did. Developers have been testing software since the 80s, I believe. You should too! I will do my best to show you that testing can be accessible and fun.
Noen dager er jeg optimist og i godt humør og tenker at dataspill endelig er i ferd med å få sin fortjente status som en positiv og sunn aktivitet. Men hver gang dukker det opp noe som viser at det fortsatt er lang vei å gå.
Tråd.
🎉GIVEAWAY TIME 🎉
Together with Super Rare Games we give away a sealed copy of our freshly tested The Darkside Detective Duology for PS5, shipping worldwide.
To enter the giveaway,
follow us,
follow @SuperRareGames,
retweet this post.
We will pick a winner on Tuesday, March 12th. Entries close on 8 pm CET that day. Good luck!
#Giveaway
@Herrbrun Jeg hisset meg litt opp over hvorfor NAV ikke klarer å hente slik info fra arbeidsgiver selv.. Hvorfor må det skrives et brev som må signeres anno 1664
Det er helt utrolig at Schibsted fortsatt kjører opt-out på alt av annonsesporing og gjør det så tungvindt som mulig å skru av alt - en for en. Og vil så ha deg til å logge inn for å "huske innstillingene". Grotesk.
All ære til @OsloStudenten som avdekket klipp og lim i Sandra Borchs masteroppgave. Langt mindre ære til @E24 som ikke nevner ham med et ord i sin sak.