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.
1. The lounge is for the CodeProject community to discuss things of interest to the community, and as a place for the whole community to participate. It is, first and foremost, a respectful meeting and discussion area for those wishing to discuss the life of a Software developer.
The #1 rule is: Be respectful of others, of the site, and of the community as a whole.
2. Technical discussions are welcome, but if you need specific programming question answered please use Quick Answers[^], or to discussion your programming problem in depth use the programming forums[^]. We encourage technical discussion, but this is a general discussion forum, not a programming Q&A forum. Posts will be moved or deleted if they fit better elsewhere.
4. No politics (including enviro-politics[^]), no sex, no religion. This is a community for software development. There are plenty of other sites that are far more appropriate for these discussions. Or if you must, use the Back Room[^] - but enter at your own risk.
5. Nothing Not Safe For Work, nothing you would not want your wife/husband, your girlfriend/boyfriend, your mother or your kid sister seeing on your screen. For those discussions where you wish to be a little more frank, use the Soapbox[^]
6. Any personal attacks, any spam, any advertising, any trolling, or any abuse of the rules will result in your account being removed.
7. Not everyone's first language is English. Be understanding.
Please respect the community and respect each other. We are of many cultures so remember that. Don't assume others understand you are joking, don't belittle anyone for taking offense or being thin skinned.
We are a community for software developers. Leave the egos at the door.
The 15 minute screen lock is driving me crazy. Take a call, finish, put in your password. Try to do a training session, locks partway through, put in password. Co-worker enters office, leaves, enter password. Seems I spend all day entering my password. Policy won't let me disable it! I bet the guy who came up with this, is the same guy who came up with the stupid password rules back in the 80's. Arghhh!!
I just need to add that trying to find and run an actual Xamarin example project for Visual Studio that works out of the box seems nigh impossible.
What has happened to development? We used to share code, throw it at a compiler and it would compile. That's simply not the case these days. Nuget packages disappearing or being updated so they provide conflicts with other libraries; the npn nightmare of downloads hundreds of Mb of packages; The mind boggling Android SDK hunt and seek (and make sure you have plenty of disk space); the soul destroying walled garden around iOS development. Not to mention the explosion of here-today-gone-tomorrow frameworks.
Something's gotta give. This space is ripe for an upheaval.
And people wonder why I still haven't moved onto mobile development. I'm still waiting for things to settle and a clear winner to be identified. Frankly at this rate I'm beginning to doubt I'm ever going to do any serious mobile development before I retire (and I'm in my 40s).
Wish me luck! (I seriously doubt the company, a global company) will go for it, as it will require them front-loading 50% of the payment for the staffing process, but I figure my proposal could at least serve as a baseline for vetting proposals from "real" companies that already have the existing staff to handle something like this.
Or possibly, your proposal will provide the method for them to do the project in house and the cost to justify not out sourcing.
It's happened to me on major difficu;lt engineering projects. They had the people and the resourcxes to do things in house, but didn't have anyone who knew what to do.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
I took on a side project a couple of months ago doing enhancements to an MS Access app. The guy I've been working with has quit. He told me that the company wants to continue using me. I think I'll be working one on one with the owner.
So, I see this as an opportunity to move them from Access to .Net. If they do it will most likely become a WPF app.
What I need is persuasive information. Just saying "Access sucks" won't do it. So, how would you approach this? What arguments can you give to help them decide to move to .Net?
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
4) Access is not intended to be used as an enterprise database solution.
5) Finding skilled Access developers is becoming more difficult as time goes by because the money is in SQL Server.
6) Access sucks.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
Finding skilled Access developers is becoming more difficult as time goes by because the money is in SQL Server.
That should be enough reason IMO. Finding people willing to work with Access is only going to get more and more difficult, which means the longer they wait to transition to something else, the more expensive that transition will get in the long run.
In addition to what John said.
Access is single user - MS has documentation stating the fact somewhere. This should be the single most compelling argument to change to an n# tiered solution.
Access is an OFFICE tool - that argument should kill all further discussions. I don't know the recent history of MS Office upgrades but in the 90s every upgrade would break the applications I had written in Access. Moving to SQL Server eliminated that horror.
Oh yeah and Access sucks!
Never underestimate the power of human stupidity
Apple has continued (IMO) down the path of releasing software that doesn't live up to the beauty of their hardware. I updated my iPhone 6 to iOS 11 and put up with the first week of slowness, and crashes, and poor battery life, but even after an acceptable period of burn in the phone is just awful to use now. Apps can take 5-10 seconds to load. The camera can take even longer to be ready to roll. It's a huge shame, really.
Even so I'm not willing to move to Android for a bunch of reasons and there's really no alternative, so I've been thinking about moving up to a (relatively) cheap 7. That means I'm going to lose my headphone jack. I'm getting the shakes thinking about that.
Lots of phones have now gone jackless so I was wondering if this has generally been a good thing or a bad thing or a meh thing.
I'd be getting airpods, and any bluetooth headphones will work.
I guess my question is: has anyone gone into this thinking it would be an utter PITA and come out wondering what all the fuss was about. Or, did they go into it thinking it would be OK but there were all these "ah, I didn't think about that" issues.
Yes, but not as well, sound quality over A2DP sucks. And while Apt-X is ok-ish, it's of course not supported by Apple. Since it wasn't invented by them.
Apple uses lowish bitrate AAC which is better than A2DP but still inferior to Apt-x.
Personally I'm having a pair of Sennheiser Momentum, which was a compromise on a few parameters. (comfort came out as the winner, had I gone for sound I would've chosen Bowers&Wilkins P7)
They support Apt-x but I'm actually using them with the cable most of the time, since the sound get's so much clearer and less compressed.
But if you're getting earpods this whole discussion on sound quality is moot.