| bio | website | caffeineoncode.com |
|---|---|---|
| location | Denver, CO | |
| age | ||
| visits | member for | 2 years, 8 months |
| seen | yesterday | |
| stats | profile views | 204 |
|
Jun 5 |
awarded | Good Answer |
|
May 30 |
comment |
Is it worth moving from Microsoft tech to Linux, NodeJS & other open source frameworks to save money for a start-up? @gbjbaanb, you're reminding me of this wacko: denverpost.com/politics/ci_18598242?source=bb. Criticizing the effectiveness of code based on climate change is indefensibly stupid. The contribution mentioned in the article paid off .0000000013986% of the United States debt. I suspect that switching from C# to C++ would have an even smaller impact on global energy usage. Grow up. |
|
May 7 |
comment |
Decimal to 17-bit 2's Complement Signed Number I'm going to start with the most obvious problem: 2's complement is intended for use with integer types. With that in mind, what does 2's compliment have to do with numbers such as 0.05 and -0.28? |
|
Apr 25 |
comment |
Is a try and catch that does not throw an exception more efficient than a conditional? -1. Don't do this. If you're concerned about the performance overhead of checking if the key exists, then use TryGetValue() instead. msdn.microsoft.com/en-us/library/bb347013.aspx |
|
Apr 22 |
revised |
Is it possible to reach absolute zero bug state for large scale software? added 422 characters in body |
|
Apr 21 |
comment |
Is it possible to reach absolute zero bug state for large scale software? @JohnR.Strohm, it is obvious to anyone who has read the original question that the op was talking about a large scale programming project. Despite that, my points about the potential instability of the systems you are running on still holds, even with your example. |
|
Apr 21 |
awarded | Nice Answer |
|
Apr 20 |
answered | Is it possible to reach absolute zero bug state for large scale software? |
|
Apr 4 |
comment |
How do I take responsibility for my code when colleague makes unnecessary improvements without notice? No. If you check in incomplete code that needs a comment to label it as such, then you're already in hell. Comments just take you to a different corner of hell. |
|
Apr 4 |
comment |
How do I take responsibility for my code when colleague makes unnecessary improvements without notice? That is what shelfsets are for. Don't check in incomplete code. |
|
Apr 4 |
comment |
How do I take responsibility for my code when colleague makes unnecessary improvements without notice? Boy that could get confusing. Imagine--adding a comment stating, "This code is not complete," and then forgetting to remove it once you complete the code. |
|
Mar 29 |
comment |
How does understanding computer architecture help a programmer? @hanzolo, I stand by my original statement: You don't even know enough to know what you don't know. If you're not willing to learn it, then I'm not willing to make any efforts to describe it. |
|
Mar 28 |
comment |
How does understanding computer architecture help a programmer? @chrisaycock, if it is a linked list, then what stops each block from being at the beginning of the memory space devoted to each process? :) It doesn't really matter. You're probably right--everything is so abstracted that everyone can eventually be shown to be wrong. That was just the level of abstraction that was used to present the concept to me. |
|
Mar 28 |
comment |
How does understanding computer architecture help a programmer? @chrisaycock, it is a header that is at the beginning of each process's memory. In the sense that only the kernel directly touches the PCB, you could consider it part of the kernel (and who knows! Maybe everything I was taught was a high level abstraction and it is not stored anywhere close to the process!). But with that said, each process has its own unique PCB and can be considered a part of the process. Knowing of its existence is especially helpful if you ever try to use fork and exec. |
|
Mar 28 |
comment |
How does understanding computer architecture help a programmer? @chrisaycock, I think that you are mixed up somewhere. The segments article that you linked to refers to how the computer divides up the address space of RAM to avoid fragmentation. How the memory of a process is divided up is different (and there are usually 4--the Process Control Block, Code, Heap, and the Stack) |
|
Mar 27 |
comment |
How does understanding computer architecture help a programmer? @parsifal, Cache, RAM, and Disk. For more information: en.wikipedia.org/wiki/Memory_hierarchy. With that said, there are not necessarily 3. Many people consider registers and cache in a different teir. In addition, cache is usually divided up into the L1 and L2 cache (and sometimes an L3 cache). How complicated you want it to be depends on how deep you want to dig. |
|
Mar 27 |
comment |
How does understanding computer architecture help a programmer? @Carson63000, yes. Managed programming means, "Programming with the assistance of a garbage collector and a JIT compiler" It does not mean "Programming in a magical fairy tale land where all the problems of the world disappear." :) Too many people treat managed programming as though it is the second definition. |
|
Mar 27 |
comment |
How does understanding computer architecture help a programmer? @hanzolo, exactly. You're doing app development, and that's fine. But don't assume that every developer has the same level of aspiration as you do. |
|
Mar 27 |
comment |
How does understanding computer architecture help a programmer? I'm sorry, but assembly language != architecture. The two have some overlap, but on the whole, are completely different. The memory hierarchy, basic operating system design, and task scheduling are but a small number of categories that fall under "architecture" that have nothing to do with assembly. |
|
Mar 27 |
comment |
How does understanding computer architecture help a programmer? -1. You don't know what you don't know. Understanding cache performance, the memory hierarchy, operating systems, time sharing, and countless other things have made me a much better programmer. You're willfully ignorant (and that is fine), as long as you don't set your sights too high. If you want to truly become a "good" programmer, than you must make an effort understand the machines that you are commanding. |