There are similarities in current WCMS rewrites like Typo3 and Day Communique. These common themes can be considered as state-of-the-art in designing WCMSs.
A popular discussion online these days is the decline in the number of Computer Science students these days. I am a Computer Science major and wittnessed one of the major reasons for this firsthand.
If there’s one thing we know for sure about the Internet, it is that by its very nature it is a transient medium. What was 10 years ago, is generally nothing like what is today, which will be nothing like what will be 10 years from now. Blogger Robert Scoble posted today that the recently released Search 2001 archived search engine from Google (our coverage) highlights well the web’s transient nature. Many of the sites that existed in the search results on Google in 2001, not only don’t appear in the results for those searches today, but don’t exist on the web at all.
It's time that developers and web-based businesses realize that the term Web2.0 is doing more harm than good. For years now, the meaning of Web2.0 has been derided and debated while all along it has quietly acquired a meaning that colors the efforts of countless entrepreneurs and developers as something unwelcome and harmful. Read the post if you'd like to know what the meaning is, and PLEASE consider the proposed alternative!
Bugs are an inevitable part of development that most people loath or at least generally dislike. If you take the time to examine this phase of a project you will find that it's not the bugs that really irk you, but the way they are presented or described.
It does seem unlikely that the bubble will burst in quite the same way as it did last time. After all, the hot money that went into dotcoms in the late 90s went into the housing market rather than technology this time around.
Discussion about writing Ruby code from scratch vs. using Rails Plugins. Talks about the pros and cons of each and why both can make you a better developer.
Is SaaS and Clould computing all hype and no substance? While there is certainly a lot of hype around these, there are good and bad reasons to adopt these technologies on a case-by-case basis, as long as you remember that there is no silver bullet!
It tends to be compared to other forms of engineering, especially architecture. I have to admit that when first being taught SE, I fully bought into that whole analogy. But, when one moves beyond the basic concepts, it falls apart. There are many problems with this comparison as well as many pitfalls one may fall into when making it.
If you’re a mobile application developer, where should you be playing your chips — on Apple’s side of the table or Google’s?
A few months ago there was a submission to DZone, a niche site that I visit almost daily, that questioned the site’s users as to how they felt about self submissions on the site.
I believe that the AJAX/DHTML model is broken...at least for widespread adoption. Here I explain why lack of standards and huge fragmentation is killing widespread adoption of browser based rich UIs.
Is natural language taking over, and are all attempts to improve URLs futile? Has the slow progress of the regulating bodies meant that we’ve had to find a better solution? Of course, some URLs are clever slogans themselves and add value to a product, but it seems that most are arbitrary identifiers, obfuscated by acronyms, abbreviations and dots, dashes and other de-humanised elements.
I’ve decided to take a 2 part stab at answering Jurgen’s question about what motivates me in the work place. To start with, I decided to meditate on a few things that tend to grab my motivation by the metaphorical gonads and squeeze.
Have you been wondering how to get your CEO's attention long enough to have a conversation about agile? Here are 8 questions, inspired by Rob Thomsett, long time Agile Evangelist and keynote speaker at this year's Agile Business Conference in London.
Development is hard, and getting harder all the time. For every new framework that comes out to simplifying the complexity of the code we write, another two technologies hit the market. For every practice and principle we get to grips with, two other will evolve. The better we make software, the more users expect.
Bjarne shares his perspective on everything from his favorite toy growing up, to his dream about the future of computing, to his greatest fears about how multicore technology might evolve.
At my current client I’ve got to do mainly maintenance on existing applications. This gives me the chance to look into codebases that have been created by other people and that don’t really reflect how I would write things. That is all good though it gives me a chance to learn new ways of doing things and when I think their way is better I’ll surely adopt.
What makes a professional developer? In an interview Robert Martin reveals that he thinks that some times it is professional to cheat your boss.
We have this rather large project at work, one that’s been in development for a few years now. This project has had many releases already, and from a business perspective, is quite successful. From a technical point of view, there were definitely some things that could’ve been better. The largest problem is that this project uses a very extensive code-generation process. This code generation process basically retrieves all of the database metadata and generates an entire Data Access Layer (based on basic ADO.NET), a shitload of automated tests to cover that entire DAL, a whole lot of extra classes which form a data-driven business layer (real business logic can still be added though), and again, a shitload of automated tests that cover the data-driven business layer.
Why do developers in India have to work 10-14 hours? Is it really needed? And can you stay focused working 10-14 hours a day? Do you still have the ability to concentrate after 8-9 hours of work? I don't know? I should try working for a month or so in India just to see how things are now, don't you think so?
Read on.....
I blogged about the illusive social facade of web 2.0 before, things seem to be getting worse still. In a long awaited sign of life update, Roger Johansson (456bereastreet.com) proclaims he will be closing the comment sections on his articles, referring to the following article on blog comments. Not a good thing. At all.
What does software look like? Wouldn’t it be helpful if we had a visualization of software that we could use while the software was being constructed or tested? With a single glance we could see that parts of it remain unfinished. Dependencies, interfaces and data would be easy to see and, one would hope, easier to test. At the very least we could watch the software grow and evolve as it was being built and watch it consume input and interact with its environment as it was being tested.
Having spent many years on different online communities and forums, not least JavaLobby, I've noticed some trends about how developers act from behind their monitor. To get a broad range of opinions, I've also asked some of the other Zone Leaders from DZone for their opinions on this. I don't mean to say all developers are the same - I've been one long enough myself - but I want to find why people hunt in their packs in communities and forums.
So far I haven't been disappointed my career move to freelancing except for one thing : I can't seem to find much freelancing Java opportunities. Now, I'm just starting out as a freelancer and it is way to soon to draw any conclusion but I'm beginning to doubt. Is java freelancing possible?
This article is a quick journey through the mind of a Scala newbie while learning the language. I work through a few Project Euler problems, refining solutions along the way so they use more idiomatic Scala. In the end are some general impressions of the language, the install and setup process, the Scala community, and support for Scala within different development tools.
This is not SEO bullshit, it's just my TOP 5 of Weirdest Google Searches to End Up in This (Development) Blog (gathered from google analytics)
Jeremy Miller is looking for a DSL that reads like natural language. My immediate response was that it is not practical, because I assumed he wanted very natural language, which is still not possible to do without extremely high budget. Limiting the problem to just reads like a natural language reduce the problem space significantly.
There’s a strange sort of social disease going around in technology circles today, and it all centers around this word “innovation.” Everybody wants to “innovate.” The news talks about “who’s being the most innovative.” Marketing for companies insists that they are “innovating.” Except actually, it’s not innovation that leads to success. It’s execution.
Shahzad Bhatti brings a balanced perspective and 20+ years of programming experience to this generally polarized topic. He likes working in a polyglot environment, he says, "where I can write performance-critical code in system language like Java and use Ruby/Python for high-level glue code or web tier." At the same time, he finds much criticism of Java dishonest: "people rave about metaprogramming in Ruby but forget to mention all the overhead that goes with it ..."
Everyone has memories of certain formative experiences that seemed to mark the end of naive adolescence and the beginning of cynical adulthood.
When I think back over my career as a software developer, I realize that I’ve had several experiences that taught me some hard and valuable lessons about the art and science of software development that seem like rites of passage in hindsight.