|
Developers are Authors
This is truly a concept that has only dawned on me recently - in fact, probably within the past day or two. The ironic part about this, I’ve actually considered myself an author for the past 3 years, since the release of my first book. And most developers I meet or work with seem to have the same reaction when I tell them, “Oh you’re an author, that’s pretty cool.” When in fact – as the title states – all developers are authors, including you! Now let me tell you why.
As I stated at the start of the article, this is really new information to me, but has had a really strong impact on the way I think. Firstly, I cannot take any credit for this statement as I read it in a book. If you follow me on Twitter, you will know that the name of the book is Clean Code by Robert C. Martin – the initiator of agile software development and extreme programming.
I love the comparison about the @author tag being always that as the creator versus its intent - the author.
|
|
|
|
|
Hi, I am Abhishek Sur from the City of Joy, India. I work for Buildfusion Inc. as a Technical Architect. I am addicted to code, you could say. I like to write code, even when I am sick or unwell. My mood improves simply by writing good code. I do a lot of code reviews, fix bugs, and even help fellow developers on how to write better, well structured code. We talk to Abhishek Sur, a herculian CodeProject author and two-time CodeProject MVP.
|
|
|
|
|
Windows Azure Infrastructure Services is a stepping stone that organizations can use to migrate some of their existing workloads to the cloud, as is with no changes, while at the same time taking advantage of more modern "Platform-as-a-Service" capabilities of Windows Azure in a hybrid fashion. We've seen organizations run everything from simple development and test SQL Server workloads to complex distributed mission critical workloads. Here's a few things we've learned from their experiences. Something I've noticed about TechEd 2013: Microsoft is all-in on Azure.
|
|
|
|
|
The first compiled language I used was the Assembler Editor cartridge for the Atari 8-bit computers. Really, it had the awful name "Assembler Editor." I expect some pedantic folks want to interject that an assembler is not a compiler. At one time I would have made that argument myself. But there was a very clear divide between editing 6502 code and running it, a divide that took time to cross, when the textual source was converted into machine-runnable form. Contrast that to Atari BASIC, the only language I knew previously, which didn't feature a human-initiated conversion step and the inevitable time it took. How much has compilation come along since 2009?
|
|
|
|
|
The Bayesian method is the natural approach to inference, yet it is hidden from readers behind chapters of slow, mathematical analysis. The typical text on Bayesian inference involves two to three chapters on probability theory, then enters what Bayesian inference is. Unfortunately, due to mathematical intractability of most Bayesian models, the reader is only shown simple, artificial examples. This can leave the user with a so-what feeling about Bayesian inference. In fact, this was the author's own prior opinion. Probabilistic programming with Python. Probably not for dummies.
|
|
|
|
|
In this episode, our identity wizard Vittorio Bertocci (you can identify true wizards by the long hair, even though most other wizards carry that hair under the chin) explains Windows Azure Active Directory and its role in the Windows Azure platform. Tending your forest in the cloud.
|
|
|
|
|
What developers see as iterative and flexible, users see as disorganized and never-ending. Here’s how some experienced developers have changed that perception. Eternal beta, continuous integration... and that's just Windows Update.
|
|
|
|
|
David Crane, designer of Pitfall for the Atari 2600 gave a talk at the 2011 Game Developer’s Conference. His 38-minute presentation rounds up to a full hour with the Q&A afterwards. It’s a bit dry to start, but he hits his stride about half way through and it’s chock-full of juicy morsels about the way things used to be. Pro tip: jumping on alligator heads is not advised in real life.
|
|
|
|
|
Armed with Kendo UI DataViz, I felt compelled to share information with folks in the developer community about a growing concern of mine; the weight of web pages or, what I like to call "webpage obesity". In terms of bytes-on-the-wire, the Internet is getting fat. Quite fat, in fact. For example, did you know that an average webpage is around 1.4 MB? Not surprised? You should be. "But, why should I care?" you may ask. The reason is simple: performance. I like big DOMs and I cannot lie, you other devs can't deny...
|
|
|
|
|
In the 1990ies, 14400 bps was a good speed - try to load such fat pages with such a line, and you'll have to wait some 10 minutes.
And by the way, the content of current web pages is often less than 1000 characters - i.e. a 1000 times more than the content is used for design purposes.
|
|
|
|
|
Microsoft will make available as part of its upcoming Windows 8.1 "Blue" release of Windows client the rumored Outlook 2013 RT mail client, company officials confirmed on June 5. Microsoft's Chief Financial Officer of Windows, Tami Reller, made the announcement during the Computex show in Taipei, claiming that Office RT is a top business and consumer feature request. You've got [touch, swipe, pinch] mail!
|
|
|
|
|
Ever wish you could talk to your dog? Understand what’s bothering him? How much of the time she paces around when you’re not home? Whistle, a startup that makes a wearable tracking device for dogs, wants to help. This summer, it plans to start shipping a $99.95 metal disc that affixes to a standard collar, and promises to go for 10 days on a single charge.... Owners can then chart their Whistle-wearing dogs’ daily minutes spent walking, playing and resting, as detected by an accelerometer and displayed on a free Whistle iPhone app. My master made me this collar. He is a good and smart master...
|
|
|
|
|
This paper concentrates on the development of the basic ideas and distinguishes two periods - Summer 1956 through Summer 1958 when most of the key ideas were developed (some of which were implemented in the FORTRAN based FLPL), and Fall 1958 through 1962 when the programming language was implemented and applied to problems of artificial intelligence. After 1962, the development of LISP became multi-stranded, and different ideas were pursued in different places. John McCarthy's classic 1979 (history (of (Lisp))).
|
|
|
|
|
I prefer the version from A brief, incomplete, and mostly wrong history of programming languages:[^]
"1958 - John McCarthy and Paul Graham invent LISP. Due to high costs caused by a post-war depletion of the strategic parentheses reserve LISP never becomes popular[1]. In spite of its lack of popularity, LISP (now "Lisp" or sometimes "Arc") remains an influential language in "key algorithmic techniques such as recursion and condescension"[2]."
|
|
|
|
|
Bad Developers Should NOT Use Frameworks
The sad part about this article is that the people that actually need to read this won’t. Why; because they simply don’t care about what they do. It really is the honest truth. Nonetheless, I will courageously continue writing in hopes that the good developers will magically convey this message to the people who need to learn it!
This totally hits the nail right on the head!
|
|
|
|
|
Bad developers shouldn't develop, regardless of whether they use a framework or not.
Marc
|
|
|
|
|
It depends on "why are they bad?". Someone who still learning will make some mistakes (everybody has done some poor and ugly coding).
The big problem is when things are bad and the developer don't care or don't review his (or her) work.
|
|
|
|
|
Diana NoWay wrote: It depends on "why are they bad?". Someone who still learning will make some mistakes (everybody has done some poor and ugly coding).
Exactly, a bad developer is one who doesn't care and doesn't learn from mistakes. We all make mistakes, you should see some of mine!
Marc
|
|
|
|
|
Mistakes do not make you bad. Everyone makes mistakes or even writes code that won't work as envisioned.
I've had to work with some really bad programmers, although mostly it seems I get to follow behind them and clean up their messes.
What's a bad programmer for me?
One that doesn't even understand what they are writing. I was given some code this programmer had written before he went on vacation, he swore up and down that he had tested it. Didn't come close to working. I gutted it down to 1/3rd of its original size and when he got back from vacation I showed it to him. He didn't even see where I had made any changes.
Another one thought if the program crashed, it was the user's fault.
But the worst for me have been the ones that convince management they are God's Gift to Programming ard produce something that barely works and then moves on, leaving me to seemingly whine to management about the crap code and how resistant it is to even simple changes without crashing the entire program. You know, writing a subroutine that does 10 things and then call it because you are only interested in 2 of the things it does and you hope the other 8 don't step on anything important.
Sorry, I'm getting off on to a rant that could go for pages.
To me, the only advantage of a bad programmer is that they teach what not to do.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
Seems like the argument is "bad developers shouldn't use frameworks, because bad developers don't use frameworks".
|
|
|
|
|
Good developers shouldn't use frameworks either.
|
|
|
|
|
Yes, good developers do not need Frameworks !!!
|
|
|
|
|
I'm sorry. This is an incoherent rant.
|
|
|
|
|
Bad developers should also never be allowed to BUILD frameworks. I've experienced the outcome from this first hand. It was horrifying.
|
|
|
|
|