|
Kent,
I have no idea how you would know about Crokinole [^]. I mean, there is no way anyone would ever speak about this unless you've played it.
Best Wishes,
-David Delaune
|
|
|
|
|
I’ve been stuck at the lake on rainy weekends.
TTFN - Kent
|
|
|
|
|
Well,
Just let me know when the boredom of retirement has reached it's peak. I would love to drive up to your island and have a drink with you.
Since I know you have so much interest about the Fish Shop, I can reveal some of that over a few bottles of wine. You do drink wine right?
|
|
|
|
|
I definitely drink...wine.
Let's see what happens with this Omicron Variant, but the idea sounds great.
TTFN - Kent
|
|
|
|
|
More than a third of losses came from rug pulls, where developers rolled out crypto projects before vanishing with investor money. Is it redundant to say 'crypto scammer'?
|
|
|
|
|
In this post, I’ll share how our team at GitHub adopted Codespaces to streamline the interview process. Where do you see your Codespaces in five years?
|
|
|
|
|
EF Core 7 is the next release after EF Core 6 and is currently scheduled for release in November 2022 at the same time as .NET 7. In case your applications need access to data
Unless you're still on .NET classic: "EF7 will not run on .NET Framework."
|
|
|
|
|
Yesterday I added a configuration table and an endpoint (a one line Dapper call) to return the data to the front-end. My peer (we were doing a pair programming Teams session) asked "don't you need a data model?" Um, no....
Just sayin.
|
|
|
|
|
Bait attacks are on the rise, and it appears that actors who distribute this special kind of phishing emails prefer to use Gmail accounts to conduct their attacks. So, we just have to block all GMail addresses?
|
|
|
|
|
As the POH and LOH are treated in similar ways, the .NET team coined a new term to encapsulate them both, User Old Heap (UOH). A heaping pile of info on the heap
|
|
|
|
|
Not to be confused with the OUH, which a lot of us here occupy.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
The months-long project demonstrates the physics behind the CPUs we take for granted Sorry, no DOOM
|
|
|
|
|
Words (like absolutely amazing incredible awesome) fail me.
|
|
|
|
|
According to a blogpost by former EA developer Adam Berg, different teams take very different approaches to development with one team in particular being especially slow to progress. But are they the *right* 3 lines of code?
|
|
|
|
|
@Super-Lloyd, what say you?
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
jeron1 wrote: @Super-Lloyd, what say you?
He can't answer until tomorrow, he's busy changing 3 lines of code.
|
|
|
|
|
Probably!
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Nah.. this is gamejam week! Where we (tool developers, as opposed to game developer) make (and most importantly, learn how to make) a game! Yeah!
|
|
|
|
|
well it's true, it can take even more, but I don't see the relationship with agile...
here are the multiple factor at work:
1. the codebase is huge and sometimes convoluted, those 3 lines might seem mysterious (unfortunately)
2. you might need to have your code reviewed (in fact, almost all the time) and approved by the other side of the world or nobody rush to the review
3. we don't submit the code directly (or do pull request), instead we go though a checking pipeline which runs some 10,000+ automated test on every query (there are thousands+ developer) it sometimes takes many hours
4. there might be other teams (not even part of the huge code repositories I work with) that have modified the codebase, and we must not break them... ouch, this is the real pain point. I make everything private or internal now, if I can..
Yeah, this is driving me crazy. But there is a sort of reason for that. At any rate there are benefit to working there. Just got 2 weeks of Christmas holiday for free (didn't use any vacation days), yeeha! And work culture is considerate (of life work balance), at least in Australia!
modified 16-Dec-21 17:55pm.
|
|
|
|
|
Super Lloyd wrote: Just got 2 weeks of Christmas holiday for free (didn't use any vacation days), yeeha! Nice!
How do you keep yourself busy during those times when you are waiting for a response?
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Well I am new at this and still working it out....
- work on a totally unrelated ticket, or at least a ticket that touches different files.
- just not push the review, but keep adding to it (and solving other ticket) while begging from oversea reviewer attentions
I don't like it. But I can live with it, at least I learned too. Plus everyone is in the same boat, and nobody is surprised or asking you to go faster, so I learn to unpressure myself!
|
|
|
|
|
Super Lloyd wrote: nobody is surprised or asking you to go faster, You liar you!
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
well... at least there is a good excuse not too!
|
|
|
|
|
If I worked at a place like that, I hope I'd have the sense to quit before going postal.
|
|
|
|
|
It was claimed that during VAX 780 development, the average productivity of the microcoders was to program one microinstruction a day.
This was long before the web, so unfortunately I cannot back up the claim with a URL. I read it on dead trees, way back in my student days, long ago.
(We did have a VAX 780 at my university that was starved to death on RAM, even for the day: VAX VMS could not handle page faults in page tables. One program that was regularly run on the VAX required a huge virtual address space, so out of 1 Mbyte (!) of RAM, more than half was page tables!)
|
|
|
|