chunkyfunky

7 ms·

1.
by chunkyfunky 5y ago
I would have thought the tags on the question make it pretty clear it isn't dealing with languages like Rust.
2.
by chunkyfunky 5y ago
>Heat it. Squirt it. Serve Hey, that highly technical process is valuable Intellectual Property owned by the McDonald's corporation, careful they don't come after you!
3.
by chunkyfunky 5y ago
Normally I'd be opposed to censorship in general, but in this case I'm kind of glad, but only because shit like this is actually happening even now: https://www.rte.ie/news/ireland/2021/0927/124
4.
by chunkyfunky 5y ago
Well I understood it perfectly as in I read it as "modularity, type-safety, and maintainability"...then again I am familiar with DDD and thus understand the ubiquitous language from the original comment...which is kind of one of t
5.
by chunkyfunky 5y ago
Yep, keeping ur kids in the fridge is a great way to keep them fresh for weeks :)
6.
by chunkyfunky 5y ago
I can't say I disagree with many of the points made in the article, but I am getting just a little tired of what I perceive to be the current trend of generalised manager-bashing these days...I transitioned from dev to manager a few
7.
by chunkyfunky 5y ago
I think that is a fair point and anecdotally at least it gels with what I have observed. I've worked in quite a few food service settings when I was younger and the margins (in general of course; Soup du Jour is like 5/600% margin
8.
by chunkyfunky 5y ago
+1 - super achievment!
9.
by chunkyfunky 5y ago
Was very disappointed too, I fully expected her to pull off a mask at the end and it would be Tom Cruise underneath :(
10.
by chunkyfunky 5y ago
I'm not normally one to nitpick but Robert Boyle was Anglo-Irish, not English :)
11.
by chunkyfunky 5y ago
If you look at the map on this page: http://raisedbogs.ie/what-is-a-raised-bog/ you will see how much of Ireland had quite a few natural - and very old - raised bogs up until the 1800s. And we've lost many of the
12.
by chunkyfunky 5y ago
>This is precisely waterfall I'm not sure I fully agree, unless we want to define waterfall as "anything where a bit of time is spent up-front to decide how a part of the system should work" :) For me, waterfall is where e
13.
by chunkyfunky 6y ago
That's a great point. And here is a real example that happened recently at work. One of my teams needs to create the ability for their low-level code to be able to respond to HTTP requests for command and control. So they have all imme
14.
by chunkyfunky 6y ago
As someone who came from a fairly poor background (not half as as bad as the OP to be fair) and who has managed to "break out" I can say for sure that looking back I had a ton of lucky breaks - but, and this to me is crucial, only
15.
by chunkyfunky 6y ago
Scrutor looks great, I must take it for a spin! And that is a great point about DI - being able to extend code/behaviour by injecting a different implementation of a dependency
16.
by chunkyfunky 6y ago
Neither, I'm a fully paid up and card-carrying DI-club member :) I was kind of making the same point as you did, that you don't need to use any kind of DI library to achieve the DIP, but that in something like ASP.Net it is there
17.
by chunkyfunky 6y ago
Page 150 of "Clean Code" says this about the DIP: "In essence, the DIP says that our classes should depend upon abstractions, not concrete details". This is very similar to pretty much any canonical definition you can fi
18.
by chunkyfunky 6y ago
Some fair points but I would disagree on the fundamental definition of the DIP. In my book it absolutely does not mean that low-level modules depend on high-level modules. That's just high coupling turned upside down. You have to have
19.
by chunkyfunky 6y ago
Not sure how Spring does it, but for example in ASP.Net Core, it's really simple. In the app startup class there is a method that's automatically called by the framework whereby it supplies a services container. In this method you
20.
by chunkyfunky 6y ago
"The only reason was to inject mocks". Must disagree...the reason for DI is to support the Dependency Inversion Principle : "High-level modules should not depend on low-level modules. Both should depend on abstractions (e.g.
21.
by chunkyfunky 6y ago
"On the one hand, I'd love to be able to (for instance) outsource all CoC engagement and enforcement to a specialized body, that could manage a whole investigation / accuser / defense / jury system for a number of d
22.
by chunkyfunky 6y ago
Agree that these are table stakes, and I speak as someone whose day job is managing a team that works on a fairly large open source project which is bound by the Linux Foundation CoC. And yes you are right, it is all about the money at the
23.
by chunkyfunky 6y ago
"After they told me of the reports and their finding that I had violated the code of conduct, they asked if I had anything to say." There really is only ever one thing to say in a situation like this, and it is "Yes, I refuse
24.
by chunkyfunky 6y ago
This is an excellent point. I don't get the polarised nature of the debate to be honest - there is room for all approaches in a "best tool for the job" way. I use EF Core a lot in my work, and it's the first tool I reach
25.
by chunkyfunky 6y ago
Somewhat tangential to the conversation at hand, but I feel part of the problem here is having two methods i.e. ReadOne/ReadAll. Why not just embrace OOP and go with one method (Read) that takes a specification which itself encapsulate
26.
by chunkyfunky 6y ago
"effectively illegal to see other people as a consequence of your government's abject failure to manage an epidemic" Surely though the current situation is as bad as it is because of other people's inability to manage th