311 karma · joined November 12, 2009
I personally find that if something goes wrong, the blame gang goes searching for developer that obviously broke it.
I was once publishing new web content via FTP to an IIS server when there was a disruption in mainframe connectivity to our data center. I was asked by more than one manager, in earnest, why and how I broke the 3270 connectivity. Note: I had no mainframe access at all, none, nada, zilch, zip.
IT's much easier to say "I don't have access to that machine, sorry."
A crowd funding request is a bank account that anybody can throw money into. Once the funding goal is reached, the money is released, and no more controls exist over it.
Have you spotted the risk?
It's quite simple: 1) Set up crowd funding request for some service. Make it a web service, so there's no expectation of a tangible good. 2) Evil people "crowdfund" your project, the funding goal is reached, the money is released. 3) You bugger off and do bad things to the geopolitical status quo.
It really is the same old money laundering scheme updated for the internet age.
Learning to code, means being able to write a o(n^2) sort, not necessarily being able to tell why that algorithm is bad, or what O(n^2) means.
Learning the fundamentals is important, but one must put the theories in to practice by learning a language, writing some code, making mistakes, correcting them, and learning how the fundamentals work in practice.
I always find it sad that the new data storage engines define themselves under a banner that says "We don't care that everybody who learned how to query a database since 1988 needs to learn a new way because our way is better." Which wouldn't be so bad if it was uniform across engines, but it isn't. It's a new API for each engine.
That's a lot of yaks to shave when you already know SQL.
Cubicles and desks are office furniture, and get written off at a rate that is much faster compared to how you write off office space (from the capital expenditures budget).
The "fostering communication" thing is the spin they put on it because they know you'd leave if they told you to your face that you aren't worth enough to them to spend the money on an office.
I went back and read the bottom of the article. The Design Pattern people might call that a decorator. The ruby folks would use a mixin to monkey patch the person class. You're in good company.
The trade-offs are still code complexity + programmer time vs. memory use + run time. The more general you make something, the more overhead at run time.
A tightly coupled data structure is more efficient in time and memory, but harder to reuse, and makes it harder modify the code. A more general data structure is easier to reuse and makes it easier to modify the code, at the expense of time and memory at run time.
We use a combination of Moore's Law, and the cost of a programmer to justify the less efficient general solution in the near term, and explain that we'll optimize hot spots later. This mostly works. The Author has found himself lamenting this choice in piece of high-performance software.
If he has few lists, then coding the doubly-linked list pointer directly in to his structs is the way to go. If he has many lists, I'd suggest using the cpp or m4 (or some other templating tool) to statically generate doubly-linked lists at complile time.
The idea is that Congress cannot criminalize speech. But the ramifications of your free expression, with respect to those people and institutions that you interact with, is not regulated by congress in so far as a crime is not committed in reaction.
Refute my premise that being a jerk to airport security is a bad idea.
Knowing that people are dumb as bricks, and that airport security has no sense of humor, he should have chosen a different shirt. Don't poke the bear and then complain when he bites you.
It lays out a superset of the techniques and principles of what eventually came to be called "Agile," in the wee early years of the eighties, and provides the rational for the principles, grounded in experience, and featuring data.
Despite having been through Scrummaster training, I still believe in the power of creating a "destination" and iterating analysis-design-build util the destination is reached. Using short iterations allows for course corrections, and destination shifts. The abilty to correct sooner rater than later is the key aspect I appreciate in "agile."
I've also found that while interations are good for short term planning and for scheduling sprint retrospectives (to borrow from scrum), I find that a kanban/funnel approach works better than strict iteration boundaries.
After you replied I remembered that TC is Michael Arington, arch-nemesis of Leo LaPorte.
However, CSS has, in the past, been extremely annoying to use if you want a simple tabular layout to your web site.
As other's have, or will point out, the table tags can end up being more data that you'll download each time the page contents are sent, whereas css, if you do it correctly - in a file external to the HTML - will only be downloaded one time, saving bandwidth and time.
If the site's author doesn't care about the SEO demerits of using a table, then she's not going to spend the time converting the site. This has the side effect of annoying semantic HTML purists, who believe that the HTML should only describe the content and only CSS should be used to apply styling.
While the semantic+CSS camp has a fair point, I will admit to being driven near raving mad trying to make CSS do things that were dead simple using a table. So I empathize with the people who don't want to spend large amounts of time figuring out how to make CSS do what they mean.
I'm saying (poorly) that I think that reason should dictate that if apple pays X per device for the tech that enable the device then samsung should pay Y < X if found to be infringing on round corners and colorful icons.
I don't value the design that much more highly than the enabling tech. I was pretty satisfied with my old compact nokia phone - I had a midi of run to the hills as my ringtone. Life was good.
Especially not unless I have HUD glasses that will tell me the cute barista's name.