The Insider News
The Insider News is for breaking IT and Software development news. Post your news, your alerts and
your inside scoops. This is an IT news-only forum - all off-topic, non-news posts will be
removed. If you wish to ask a programming question please post it
here.
Get The Daily Insider direct to your mailbox every day. Subscribe
now!
|
|
 |

|
This all seems a little pithy. Where are:
1. Not knowing how to actually architect and code. Maybe a little obvious but I think we've all seen code that shows the dev just doesn't get it.
2. Not knowing how to write good code. He mentioned Agile practices (which I will not get into a debate on here), but not SOLID. Poor Uncle Bob!
3. Not testing. No unit tests, integration tests, performance tests.
4. Not understanding what the software you're writing is actually meant to do. This, to me, is the 2nd biggest reason a dev is a bad dev (after #1: Being a bad dev). Once you understand programming it's a doddle, but being a good programmer means understanding what the app actually is meant to do (not what it does) which enables you to make decisions that focus on the app's experience, not on what makes you, the dev, happy that day.
Ugh. I could go on. (though I already have, I guess...)
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|

|
Maybe someone here should write an article on that. That article (or series) would get my ((5!)!) (= 6.6895029134491270575881180540904e+198)
Bob Dole The internet is a great way to get on the net.
 2.0.82.7292 SP6a
|
|
|
|

|
The statisticians behind the Popularity of Programming Languages (PYPL) index have named C# the language of the year for 2012. Their data shows that C# popularity grew by 2.3 percent in 2012, more than any other programming language during the same period. What accounts for the growth of C# in 2012? Well, the launch of Windows 8 has probably played a role — C# remains the dominant language of third-party application development on Windows devices. But we think there’s more to it than that. Between Windows, iOS and Android, your C# code can run on over 2.2 billion devices.
|
|
|
|

|
https://store.xamarin.com/[^]
If I was selling copies for android at $399 each and for ios at $399 each I would also be saying the same thing.
|
|
|
|

|
My thoughts exactly.
=====
\ | /
\|/
|
|-----|
| |
|_ |
_) | /
_) __/_
_) ____
| /|
| / |
| |
|-----|
|
=====
===
=
|
|
|
|

|
I'd rather stick with Android development using Eclipse and Java, can't beat the price of FREE I've checked out Xamarin and will not fork over $399-$999 for it, sorry.
"I've seen more information on a frickin' sticky note!" - Dave Kreskowiak
|
|
|
|

|
Paul Conrad wrote: can't beat the price of FREE
Sure you can; free stuff is often crap. I'd rather pay for a good tool than use a crappy free one.
Paul Conrad wrote: will not fork over $399-$999 for it,
Well, no, no tool is worth that.
|
|
|
|

|
PIEBALDconsult wrote: free stuff is often crap
I agree, there is crappy free stuff out there, but there is also good free stuff as well.
PIEBALDconsult wrote: no tool is worth that.
That's how I feel at the moment for Xamarian. It's very nice and all for doing Android dev in C#, but not worth the money (I certainly won't pay 400 bucks just for hobby projects with it). If I had a great app idea and wanted to implement it in C#, then maybe the commercial license, but why when there's Eclipse?
"I've seen more information on a frickin' sticky note!" - Dave Kreskowiak
|
|
|
|

|
At Velocity 2011, Nicole Sullivan and I introduced CSS Lint, the first code-quality tool for CSS. We had spent the previous two weeks coding like crazy, trying to create an application that was both useful for end users and easy to modify. Neither of us had any experience launching an open-source project like this, and we learned a lot through the process. There's more to open-sourcing a project than pushing the code to Github.
|
|
|
|

|
In this article I want to present a cool and little-known feature of assemblers called "relaxation". Relaxation is cool because it’s one of those things that are apparent in hindsight ("of course this should be done"), but is non-trivial to implement and has some interesting algorithms behind it. While relaxation is applicable to several CPU architectures and more than one kind of instructions, for this article I will focus on jumps for the Intel x86-64 architecture. An inside look at how the LLVM assembler works.
|
|
|
|
 |
|
|
General
News
Suggestion
Question
Bug
Answer
Joke
Rant
Admin