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.
Also it's a good chance to get used to HTML/CSS from a language/IDE you already know. In time it will become natural to migrate to TypeScript.
Is C# something I can realistically make cutting-edge applications with at this point?
Yes, but learning how to to write desktop apps now doesn't help your career any. Given your web background, I'd extend that to more platforms -- yes, Xamarin if you want to do C#.
Xamarin is out of the question for me right now because Im on Windows 7 and the emulator I can use is too slow
You have a little less than a month to upgrade to Windows 10 for free. Do it and then learn Xamarin. I just did that myself last week for that exact reason.
Are desktop apps dying or can I really still make some killer stuff with C#?
Yes. Why write something trapped to a specific platform when you can do it client/server and open up a whole host of potential or future functionality for the user? Even if you don't ship it client/server, architect it that way so you can break them apart later. You never know where you might want to take your desktop application in the future.
I'm a desktop C# guy whose starting to climb the learning curve on stack stuff. Don't head this direction, it leads to dinosaurs -- turn around and go back the way you came
We can program with only 1's, but if all you've got are zeros, you've got nothing.
Dumb question... if you are a DBA and I came up to you and said "Here's a physical beastly box... 24 cores, ~140GB of RAM, plenty of flash storage... I need you to set up SQL 2016 on it and migrate this 10TB database from SQL 2008 R2" Assuming of course proper security and best practices, etc. Let's even "complicate" it and assume this 10TB database includes spatial data. How long would it take you? I have ZERO SQL admin experience other then slamming a few SQLs onto local machines or VMs and I think I could realistically get it setup and running in a day or two with plenty of breathing room. Yet, our supposedly experienced DBAs claim its going to take them 3 months!!! LOL... Unbelievable.
The last time our DBA group quoted us 3 months, it took them 9 months. I'm still "waiting" for them to complete tasks from like 3 yrs ago LOL. The team lead is horrible. So easily distracted. You basically ask him "how's it going" as a courtesy before jumping into work and you have to listen to his stories for like 30 minutes at least. Then somebody comes up to his desk and interrupts and he is distracted again for another 30 minutes. Rinse, repeat.
Not a DBA, but the first question is whether this is for internal use or will be exposed externally. If the former, why not just do it yourself? If the latter, then it will take time, with the actual data import not taking much time at all, but security, configuration, etc. taking a while. Plus they are probably overloaded with work.
We are a B2B data provider, so the database is behind a firewall and the web services access it. We devs aren't allowed to touch the databases anymore. The DB team lead locked them all down. I agree on that, you shouldn't have people randomly do stuff to production databases. Due to the slowness of the database and ETL groups, most of us devs just sit around all day. Nothing to do while we wait on those groups.
What's sad is that even with all this time we give them, the databases still suck. They go down all the time, have lots of timeouts, etc.
Throwing hardware at the problem may speed things up, but rethinking how the data is organized is also a way to get a good boost. I still stay set it up on your own, show it works and then have it deployed into the data center.
We have 2 SQL devs that write the SPs.
One of them is fairly OK, but tbh, I think his skills are antiquated and he has no interest in learning new stuff. He only knows Microsoft SQL and tends to develop SPs using tons of temp tables and tends to "work around" issues rather then fix them.
The other dev is awful. Us devs suspect he is a former C/C++ developer who picked up a "SQL for dummies" book one weekend and decided to become a SQL developer. Just due to the way he writes SQL code. The first project they gave him, he released an SP that took 30 minutes to run!!! He actually released it like that. They've restructured everything many times over and have got it down to 5 to 10 seconds now which still doesn't meet the requirements LOL.
30 minutes to 5 to 10 seconds is a huge improvement obviously, but it just shows how bad the SQL is at my company.
Last Visit: 31-Dec-99 18:00 Last Update: 23-Oct-16 10:44