Whatch'ya readin'?
-
This article makes yet another compelling case for the value of reading other people's code. So, for those of you who agree with the sentiment (as I do -- at least in theory), found anything good lately that you'd like to share? I'll go first: I've been spelunking through some of the CSharp portions of .NET Core (formerly on CodePlex, but now on GitHub.)
-
This article makes yet another compelling case for the value of reading other people's code. So, for those of you who agree with the sentiment (as I do -- at least in theory), found anything good lately that you'd like to share? I'll go first: I've been spelunking through some of the CSharp portions of .NET Core (formerly on CodePlex, but now on GitHub.)
I'm reading a combination of Other People's Rubbish and Personal Perfect Projects. :laugh:
veni bibi saltavi
-
This article makes yet another compelling case for the value of reading other people's code. So, for those of you who agree with the sentiment (as I do -- at least in theory), found anything good lately that you'd like to share? I'll go first: I've been spelunking through some of the CSharp portions of .NET Core (formerly on CodePlex, but now on GitHub.)
The instructions on a packet of toothpicks.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
This article makes yet another compelling case for the value of reading other people's code. So, for those of you who agree with the sentiment (as I do -- at least in theory), found anything good lately that you'd like to share? I'll go first: I've been spelunking through some of the CSharp portions of .NET Core (formerly on CodePlex, but now on GitHub.)
-
This article makes yet another compelling case for the value of reading other people's code. So, for those of you who agree with the sentiment (as I do -- at least in theory), found anything good lately that you'd like to share? I'll go first: I've been spelunking through some of the CSharp portions of .NET Core (formerly on CodePlex, but now on GitHub.)
I am reading... this: :(
// Make REALLY sure we have a TRUE singleton
ContentHandlerPtr ContentHandler::GetInstance(const char* pContentRoot)
{
if(!ContentHandler::m_pContentHandler.get())
{
m_pContentHandler = ContentHandlerPtr(new ContentHandler(pContentRoot));
}return ContentHandler::m\_pContentHandler;}
... such stuff as dreams are made on
-
My predecessors' code. Good example of how not to do multi-threading :sigh: To be fair, it was a C program (I think) that was ported to C++ and optimized for low memory systems.
-
This article makes yet another compelling case for the value of reading other people's code. So, for those of you who agree with the sentiment (as I do -- at least in theory), found anything good lately that you'd like to share? I'll go first: I've been spelunking through some of the CSharp portions of .NET Core (formerly on CodePlex, but now on GitHub.)
I'm reading an article... small book... not really sure what's it's classified as by Paul McKenney on CPU/Memory architecture and memory barriers. Asked myself a question while writing an article I realized I couldn't answer to my liking - so I'm rectifying that today :thumbsup:
-
I am reading... this: :(
// Make REALLY sure we have a TRUE singleton
ContentHandlerPtr ContentHandler::GetInstance(const char* pContentRoot)
{
if(!ContentHandler::m_pContentHandler.get())
{
m_pContentHandler = ContentHandlerPtr(new ContentHandler(pContentRoot));
}return ContentHandler::m\_pContentHandler;}
... such stuff as dreams are made on
-
I am reading... this: :(
// Make REALLY sure we have a TRUE singleton
ContentHandlerPtr ContentHandler::GetInstance(const char* pContentRoot)
{
if(!ContentHandler::m_pContentHandler.get())
{
m_pContentHandler = ContentHandlerPtr(new ContentHandler(pContentRoot));
}return ContentHandler::m\_pContentHandler;}
... such stuff as dreams are made on
He must have come up from the ranks of early c users, and want to only use single characters for variables, etc. (but suffers longer words as prefixes and suffixes).
I wanna be a eunuchs developer! Pass me a bread knife!
-
This article makes yet another compelling case for the value of reading other people's code. So, for those of you who agree with the sentiment (as I do -- at least in theory), found anything good lately that you'd like to share? I'll go first: I've been spelunking through some of the CSharp portions of .NET Core (formerly on CodePlex, but now on GitHub.)
The Lounge at Code Project :-D I'll get my coat. :(
Mongo: Mongo only pawn... in game of life.
-
This article makes yet another compelling case for the value of reading other people's code. So, for those of you who agree with the sentiment (as I do -- at least in theory), found anything good lately that you'd like to share? I'll go first: I've been spelunking through some of the CSharp portions of .NET Core (formerly on CodePlex, but now on GitHub.)
Lucky Dog - a narrative about the Lucky Dog vendors In New Orleans by the General manager of the company for the last 40 years. Great read if you've ever been to New Orleans and had one... and even if you have not.
-
This article makes yet another compelling case for the value of reading other people's code. So, for those of you who agree with the sentiment (as I do -- at least in theory), found anything good lately that you'd like to share? I'll go first: I've been spelunking through some of the CSharp portions of .NET Core (formerly on CodePlex, but now on GitHub.)
-
This article makes yet another compelling case for the value of reading other people's code. So, for those of you who agree with the sentiment (as I do -- at least in theory), found anything good lately that you'd like to share? I'll go first: I've been spelunking through some of the CSharp portions of .NET Core (formerly on CodePlex, but now on GitHub.)
Over Xmas vacation I'm reading a manual from NXP on a new multi-core embedded controller, Cortex A7 and M4 in one package. Something for the C++ Linux guys on the A7 end, and something for the C "bare iron" guys on the M4 end. Lot of programming challenges to manage power and how to best partition the design to split the requirements between a real-time front end and lots of store and forward data routing on the back end to multiple radios. Then there's the problem of a C# production tester at the assembly line. And on top of all that the security hypervisor to secure against IoT attacks.
