The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
That's what I've said before: We should be able to move posts between forums ourselves!
Anything that is unrelated to elephants is irrelephant Anonymous - The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 - I'd just like a chance to prove that money can't make me happy. Me, all the time
We used to have a table (SQL) to store forum members - active or inactive...
Now we added the ability to define a group of members (mostly on role base) with a single line...
The next step was to declare a view that expands those lines with group on them to be back to the one-line-one-member situation...
Why in the elephanting elephant the view has a filter for active members only!!!
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
So for us British, European, maybe even US folks at least, we have something called the Data Protection Act, which ultimately means we "should" be careful with other peoples data and not retain it longer than we need. The thing is, as a software developer, do we know who is responsible for the data contained within the database driven apps we release?
I would say it's whoever owns the app?
What about building apps in-house? The Chief Exec?
Each organisation is obliged to appoint a DP officer who is responsible for policing the systems and procedures in use. But ultimately if there is any breach of the law the organisation as a whole tends to be held responsible. For corporate bodies that means the directors/management, and for charitable bodies it is the trustees.
This general concept is discovered frequently in the group I work in.
We collect operating data, not necessarily personal data, from various pieces of equipment, sensors, meters, etc. And we keep that data... seemingly forever.
We do have some regulatory requirements to hold certain data for 'X' number of years; after that time period, we can LEGALLY dispose/delete the data.
If we delete the data as we are allowed to do, then, in the event of a legal action, we cannot provide data we don't have - which may benefit the company.
However, from the perspective of seeing how something performed over time, we may need more than 'X' number of years of data to see a long term trend... think of very large turbines for example. They may have a service life of 20 to 30 years.
So... it is an interesting topic to say the least.
Where I work its in house development of Insurance back office system. We hold regular audit reviews by each department team leader(s).
Our parent company then on top of that have Yearly company audits and then Group Internal Audits every 2 years repeating depending on how you fair with the audit.
We also have security audits on top of that which look at the access of property / systems etc.
Every day, thousands of innocent plants are killed by vegetarians.
Last year we were tasked with reverse engineering a legacy app, we could not find anyone willing to admit they owned the data and that was from the POV of we want to fix this for you, not you f***ed up and we want to put your ass in a sling.
So I guess DP was low on their priority list (there was no personal data involved).
Never underestimate the power of human stupidity
This may (or may not) have been said already. As a database administrator, we were always told that WE were the custodians of the data, but the Application team OWNED the data. Meaning, we were responsible for the routine maintenance, consistency, and availability of the data while the Application team was responsible for the Content
I like the concept of Xamarin.Forms and see where I will probably use it in a couple of versions time. Right now, however, I will stick to Xamarin.Android and Xamarin.IOS to produce the relevant applications. The beauty is, of course, that you can still accomplish a lot with a shared back end and then just concentrate on the UI with the relevant platform specific part.
Well Peter.. I never was where you are now.. Started directly with XForm!
And learning about Android / iOS on the way right now, as one can't escape the native platform, even with XForms!
The great thing about XForm is XAML, Binding, DataTemplate, etc ... all those things we love from WPF!
(and hey, a Button is a Button, be it on Android or iOS!)
But being proficient with the platform is still quite relevant... (at least for quality apps) so you are still using your time well!
But giving it a go at home... Now that it is free... you might be pleasantly surprised!
I've tried Xamarin Forms. I just don't feel it's quite there yet - it's like Silverlight 2 was, plenty of potential but not quite ready for the mainstream. The biggest problem I have is that the Layout system is still too heavyweight. if you want to add child containers, and then remove them, you're going to trigger lots of layout passes - and event bubbling goes well beyond the scope it needs to. It will get there, but there are some niggles that just need to be sorted.
My project is being taken away from me and rewritten in Python by a couple kids.
Windows 8 delayed a demo by doing >100 updates, then trashing the PC.
I accidentally installed the wrong Ingenico drivers, not realizing that I had two different versions on my computer, and I uploaded the older one to the demo box.
The demo was scheduled before we even tested the system.
The Ingenico pinpad went into "tamper" mode, and refused to accept card swipes.
In the meantime, one of the kids is asking me to update the receipt printer so it also prints a customer copy, for his hot off the press (actually, still on the press) demo, which just so happens to be a competing product to the one I'm developing (don't ask how that happens.)
But at the very last hour, we got a PC working, the right Ingenico drivers, a working Ingenico, and voila, the software, pinpad, ESeek ID scanner, and thermal printer all did the right thing in front of the CEO.
So now my mood is more back to neutral.
I'm really looking forward to next week. The CTO that "manages" all this, basically an ADHD personality that is either usually sleep deprived or seems to be on crack, and has no concept of how to manage a project, is going on vacation for a couple weeks.
It's a paycheck, but that's about it. Which rubs me the wrong way, because my work ethic is such that I want to be interested, involved, and above all, happy, to do the work. I've done pro bono work and felt much more "job satisfaction."