Got a job going at my work (South Melbourne) for a developer and figured I would use the ever resourceful AGN (even though QGL interface is where it's at) to spread the word to see if anybody is interested. I don't know more than the ad below so if you want to find out salary ranges then go through the apply process below.

Apply via Seek

Requirements
The successful candidate will require a MINIMUM of five years programming experience plus current professional experience and confidence in:

* Visual Studio (ASP.Net VB.Net C#)
* AJAX
* PHP
* SQL Server 2005 (T-SQL, Reporting Services, Analysis Services, Integration Services)
* Java
* MySQL

Additional attributes that would be seen as beneficial:

* Data warehousing
* Tertiary qualifications
* Flash/Silverlight

Additionally you get to work with me - HOW AWESOME!

Having worked with TicMan I can attest to it being awesome. At least once you tell him to keep his hands to himself, anyway.

Thanks trog, thankfully I was acquitted on all charges relating to 'that' incident.

thats a rather broad bunch of skillsets

Having worked with TicMan I can attest to it being awesome. At least once you tell him to keep his hands to himself, anyway.

Yeah seconded, get me a sysadmin job in Melb tics

agree with HyperJ, the person you hire will be an absolute douche at one of those things, and you will resent them for it.

Thirded.
asp.net, c#, sql server, silverlight AND php, java, mysql, flash...
Usually job ads have the first group or the second group but not both groups.
Sounds like you want Superman!
Reminds me of a stellar job ad the company I work for posted a while ago. The list of must haves:

10 years project management experience
Masters level or Ph.D tertiary qualifications
Software engineering experience
Salary: $90K (!!)

Strangely the position never got filled...

i always laughed when they wanted senior .net developers with 7 years experience when .net wasn't even 2 years old (including rc's)

any of you been working with c#3.5, linq and wcf ? makes life so much easier for the basic things.

We recently upgraded our main in-house LOB application to .net 3.5/vs2008 from .net 1.1/vs2003 (shudder).

Even just moving to the .Net framework 2.0 would have been a great improvement, but we thought we might as well keep going up for the C#3.0, Linq & WCF support (haven't tried WPF much yet, still WinForms).

We're using Linq and the Entity Framework (with mixed results for the latter).
Most of the developers have made it a decent way up the Linq to Entities learning curve so it's happy days now.

We recently upgraded our main in-house LOB application to .net 3.5/vs2008 from .net 1.1/vs2003 (shudder).

Even just moving to the .Net framework 2.0 would have been a great improvement, but we thought we might as well keep going up for the C#3.0, Linq & WCF support (haven't tried WPF much yet, still WinForms).

We're using Linq and the Entity Framework (with mixed results for the latter).
Most of the developers have made it a decent way up the Linq to Entities learning curve so it's happy days now.

another one worth looking at is windows workflow foundation

any of you been working with c#3.5, linq and wcf ?

I am finally comfortable using most of the stuff microsoft crammed into .net 3.0, and it has taken quite a while. And yeah, some of the improvements are great, but the learning curve for some of it is quite steep (I'm looking at you WPF) when you come from a winforms and asp.net background.

I have a noob programmer under me and I'm realising how much he has to learn since the .net framework has grown so much. I have to teach him so much s***.

Our software projects are generally:

WPF Front End
- XCeed DataGrid (maybe retiring this license)
- Actipro Navigation, Ribbon, Gauges etc
- Looking at charting and reporting solutions at the moment. Crystal is a pretty huge epic fail for our use case and MS reporting is clunky.

|
|

WCF / ASP.Net Web Service
- LINQ to SQL contexts

|
|

SQL Server 2005 / 2008

Everything just works for the most part (some gotchas that are easily solved). This allows us to produce a nice n-Tier system that is humongously etensible.

WPF was easy to get into but took a long time to master. A deep understanding of the way that bining works is imperative, thing like DependencyProperties seem arcane and bizarre but to make proper use of the environment you will need to learn them.

Microsoft released their own data grid, not sure if its any good. It's part of their wpf toolkit at http://www.codeplex.com/wpf

We tend to use stored procedures for all our SQL, and our middle tier is a business object layer which the bulk of is automatically generated. Of course the middle tier is extensible for when you need to write actual business logic that isn't basic CRUD. We also tend to use binary/TCP .NET remoting for with a stateless middle tier because we have to scale it out to multiple boxes for load and redundancy.

Our frontends at the moment are ASP.NET and winforms, with a move soon to start using WPF.

edit: we use microsoft reporting services, and its pretty crap

last edited by Thundercracker at 11:42:22 24/Apr/09

The MS grid is functional but a bit bollocks. It especially looks out of place when you have theme-based layout for the rest. 500 bucks or whatever we paid for Exceed's was well worth it, but we'll probably merge our licensing for the Navigation / UI and grid into a new product when they come up next time rather than maintain them seperately.

Until I started woring with Linq I was a SP nut for data access too. My first reaction to working with LINQ to SQL was deep aversion to working against the tables directly. Hiving it off to a middle tier service reinstated the contract-based data interaction that made me frown to start with.

Stored procedures via a linq datacontext are still available for operations that work best in an SP.

I don't really like the SQL syntax for LINQ queries in code, I think it looks out of place. Lambda syntax calls look more codey and concise I reckon:


foreach(Object thingy in dc.Objects.Where( r => r.ID == parameter ))
{
doSTuff(thingy);
}


Moving to WPF will feel clunky until you get used to it. WinForms works well designed via the GUI (its the only way really?) but WPF is all about working directly with markup, the gui is really bad and just produces s***ty XAML. Its purely a WYSIWG editor with all the associated yuck.

Once you work out how grids, stackpanels and data binding works though its probably more productive in total IMO, especially if you work with generated business objects that make use of the INotifyPropertyChanged intrface.

This is why the above works so well, svcutil manages the business objects for the front end based on the WSDL or WCF stuff when reading off the middle tier service.

last edited by Hogfather at 12:22:42 24/Apr/09

I would work with Ticman except the restraining order is still valid. And his goat gets jealous when there is more than one penis available at a time

the gui is really bad and just produces s***ty XAML

It's a conspiracy to get you to buy Expression Blend!

Hah I've looked into that a few times but refuse to buy it :p

Yeah it's a bit rude considering that Visual Studio is already $$
If they're serious about splitting the 'software developer' workflow from the 'graphic designer' workflow (whatever that means) then the two products need much better integration.

Yeh, I'd much rather spend 500-1000 a year on licensed controls that already look the goods rather than buy blend and still have to do the design work!