|
f) And of course working on 'mission critical' applications presents challenges that provide you with a sense of greater achievemnt when you finally conquer them!
|
|
|
|
|
den2k88 wrote: a) Making something move has ALWAYS as sense of "oooh, magic!" and is kind of addictive.
den2k88 wrote: Functionality and stability still beats looks.
FTFY
6 Years automating industry... I miss the job content, but I don't miss the job conditions. Now I have better quality of life.
A customer I still have contact after 18 months answered my "how is it going?" last weekend with "At work quite bad, we miss you badly at shopfloor. New suppliers just deliver crap" afterwards started the private stuff.
Wow... was that a pride boost
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
...because that's what pays the bills.
But...I've started learning Xamarin Forms with the aim of moving towards a mobile capable capacity.
It needs a visual designer of some form through - hand cranking XAML is a PITA...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I much prefer to hand crank XAML
|
|
|
|
|
Why?
I'm not against hand tweaking, that's fine - but when you have to hand crank it all, the only way you can tell if it looks even vaguely right is to run the app: and that's just silly as it wastes time.
OK, I don't expect it to look perfect, but something to give you an outline, and let you drop components into others and adjust the properties would make the stack a lot easier to build.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
The designer in VS (for WPF at least, don't know about Xamarin) will reflect any changes you makes to the XAML code - although personally I don't show the designers at all - I don't mind running the app to see if the changes are ok - I don't have anything with, for example, dialogs which take an age to navigate to.
|
|
|
|
|
Hobby mostly see what I can get my hand on but if for work I will do whatever paid me
|
|
|
|
|
... so I put server, but database and data warehouse work too.
|
|
|
|
|
Work with a lot of data demands a huge work of data mining algorithms
|
|
|
|
|
Until recently, my development preference was:
#1 Desktop
#2 Server
Thanks to the free availability of Xamarin, it's now:
#1 Mobile
#2 Desktop
#3 Server
/ravi
|
|
|
|