I think I like database stuff. Normalization even for our small projects is hard, though. I assume (hope) you get better with time.
I don't know if it's any better in Android Studio or w/e, but the emulator for Xamarin is slow as fuck. It took like 2 minutes to spool up our app that had nothing but a login page. Luckily you can run that stuff on an actual phone and it's way faster.
Not sure about Xamarin, but when I was messing with NativeScript, this was my go-to Android emulator. https://www.genymotion.com/
Yeah that completely depends on the emulator. If you have Windows and Hyper-V with a decent system, it doesn't take too long to build.
Project managers literally don't Do shit in any company I've seen besides trying to take notes a d tell ppl what to do. Most don't even understand the task/process flow
Mastering bitcoin came in the mail today, I'm excited. Went with a non-technical book first for more background but finishing that up tonight
update: my team attempted our first significant merge tonight. it sucked. bad. i think we spent 6 hours troubleshooting before we figured out that the problem was our master had not been cleaned in visual studio before it had been committed.
i wish i had screenshotted the problem, but basically visual studio was telling us that we were missing some file that was like 6 layers deep into our local repos. iirc it was something called system.run i also wish someone had taken a picture of my face when we figured out what the problem was we have no idea what we're doing
On a team you generally follow a pattern like this, https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow Create a main Dev branch, when you work on a feature then create a branch off that. If the Dev branch is updated by pull requests before you're finished with your work, then pull the Dev branch into your local branch. You may have to resolve conflicts, but they'll be significantly smaller and won't affect development for others.
i had been but visual studio's team explorer allows you to do stupid things. the other part of the problem is that everyone on my team has full control over the repository.
Sourcetree for me, I don't trust myself to use command line. I've also worked with a few too many developers (well only a couple) who want to act like they're command line/scripting gurus (and who use Macs), but in reality just simply, Code: git add . git commit -m "hurr durr I R cmd line mastr!" and wind up fucking up the repository because they overwrote a file they shouldn't have or add something sensitive.
i may regret saying this in a week or in a year, but "pull" is a bad name for "fetch and merge" in the context of the other git commands
We use forks Before pr: Code: git pull upstream master --rebase -Fix any conflicts -Push to the forked origin -Make the actual pr using the github UI, which shows all the diffs. We also have our code base split into ~15 different repos which makes things a lot easier. (Except versioning)
it's a year-long team project for school, so no boss. everyone gets to take turns as the project owner or w/e because we're supposed to be learning agile .
That sounds much slower. Can you at least filter on stuff in Xamarin, or better yet, test iOS apps in it?
the project is a mobile app and we're using xamarin because we all had done at least a little bit of c# stuff.
the app loads more or less instantly after being deployed on my galaxy s8 when plugged into usb. the emulator takes significantly more time. i can't really say why. i think the general idea with xamarin is multi-platform development but we chose it so we could use c#
honestly it might have been smarter to just use android studio because solving some problems has been kind of annoying if the fix isn't obvious on developer.xamarin a lot of the xamarin guides on youtube have people manually messing with xml files so i'm guessing they pre-date some kind of merging with windows forms
we did our second merge tonight, which was really like Merge 1.5. using this model helped a lot. thank you. in hindsight it seems obvious that having just a master and then branches for new stuff is a bad idea, but the four of us are trying to learn Agile, source control, and the quirks of mobile development all at the same time.
fwiw i like Agile a lot (so far) but it seems like you need some kind of manager to make it work. in only 6 weeks my group has partitioned itself off into our own little kingdoms and no one wants to do the process/testing stuff. we're supposed to be doing "test-driven development" but any outside observer would have a good laugh if they saw our process
i think i may want this job. in doing our little group project, it seems like i'm kind of good at the process stuff. i like writing code more but i'm basically average among my peers at that.
Using splunk for alerts. Took me a while to get going as I'm not great with the sql-ish style but once you start to get the hang of it it's pretty awesome.
I used to but I like it now. Makes me feel better about if my code actually works and I can get more creative with tests than I can w/ production code
anyone ever work with big data tools, like top hat or cufflinks? http://ccb.jhu.edu/software/tophat/index.shtml
i can't remember who was saying that xamarin wasn't all that polished yet, but my group stumbled upon a fairly annoying bug, although apparently it's technically an intellisense problem. intellisense just does not recognize some basic xml attributes, no matter what. in our case, "layout" is the problem, but apparently there are a handful of others. anyway, this means that none of our app's activities will render correctly in the "designer," and the only real way view any UI stuff is to emulate or deploy onto a physical device. not clear yet but it also may mean that we'll have to manually position UI elements in the xml code
i'm glad my problems aren't complicated enough to need Microsoft stuff like visual studio and xamarin that world just sounds so awful. I tried it once and I was severely triggered by all the XML files
This is not really the case anymore with .NET core, which is what we use fairly regularly at my company, and it's pretty awesome.
well we didn't need to go this way. but our thought process was basically that we're learning mobile development, database stuff, source control, and general software project stuff from point zero. we've at least used c# somewhat, so we don't also need to learn java as well.
i actually really liked using microsoft stuff for my GUI class (forms) and then for our little app up until we hit this bug. the only reason i'm even down in the xml is that intellisense maybe/probably needs to be patched.
ESRI has ruined me on the idea of "all in one solutions" i just get freaked out whenever i get locked in to some huge proprietary system like that. YOU CANT TRUST THESE FUCKERS.
i probably haven't gotten deep enough into it to see the problems but windows forms seems awesome. we built a primitive version of spyhunter with it.