|
Like, imagine discussing your craft with your colleagues.
|
#
?
Apr 18, 2021 03:47
|
|
|
|
| # ? May 13, 2024 02:21 |
|
|
Bongo Bill posted:Like, imagine discussing your craft with your colleagues. Shocked that tech nerds don't welcome or consider different perspectives.
|
|
#
?
Apr 18, 2021 03:54
|
|
|
In my current team they feel strongly that pull requests are the wrong place to discuss craft, but I have been in teams where that is acceptable. I think doing so in pull requests requires more trust; it's more fraught than discussing something over coffee.
|
|
#
?
Apr 18, 2021 13:51
|
|
|
Nitpicks are great if they are presented as learning opportunities. I love to learn, I know I'm not a great (or even barely competent) developer, and anybody willing to impart some knowledge as feedback is appreciated. Again, only with the context of "this isn't required and feel free to not do it".
|
|
#
?
Apr 18, 2021 14:43
|
|
|
Writing simple code is super important, so I definitely flag anything that's fine but could be done cleaner or neater or simpler. I'll generally approve the pull request anyway, to be honest, because these things aren't bugs or mistakes. They're just things that'll help us keep a clean code base.
|
|
#
?
Apr 18, 2021 15:07
|
|
|
I see it as a good place to share suggestions for cleaner or more maintainable code styles. Some teams at my place use PRs as a place to document required code styles instead of you know, actually documenting them anywhere, which is pretty obnoxious.
|
|
#
?
Apr 18, 2021 21:19
|
|
|
Bongo Bill posted:Like, imagine discussing your craft with your colleagues. I, for one, stick to my principles and never reveal critical trade secrets to my competition. 
|
|
#
?
Apr 19, 2021 18:20
|
|
|
I know people who think something like that unironically.
|
|
#
?
Apr 19, 2021 19:28
|
|
|
Xarn posted:I know people who think something like that unironically. If they're your friends why are you still friends with them? If they're your coworkers why do you still work there?
|
|
#
?
Apr 19, 2021 19:46
|
|
|
Someone at work unironically added “PhD” at the end of their Slack full name. Of course they are in machine learning.
|
|
#
?
Apr 19, 2021 21:07
|
|
|
smackfu posted:Someone at work unironically added “PhD” at the end of their Slack full name. What a loving loser hahaha
|
|
#
?
Apr 19, 2021 22:51
|
|
|
smackfu posted:Someone at work unironically added “PhD” at the end of their Slack full name. I worked with someone who did that with MBA  Edit: I hadn't thought about him for a while and looked him up on LinkedIn and yup, his last name has MBA at the end Less Fat Luke fucked around with this message at 23:15 on Apr 19, 2021 |
|
#
?
Apr 19, 2021 23:09
|
|
|
Gonna rep my bachelor's degree in my title like it actually means something. Hi, I'm Protocol7, B.S. 
|
|
#
?
Apr 19, 2021 23:11
|
|
|
smackfu posted:Someone at work unironically added “PhD” at the end of their Slack full name. People who make a big deal about having PhDs are invariably up to no good.
|
|
#
?
Apr 19, 2021 23:21
|
|
|
Protocol7 posted:Gonna rep my bachelor's degree in my title like it actually means something. Pleased to meet you I'm prom candy, Some College
|
|
#
?
Apr 20, 2021 00:41
|
|
|
The B.S. stands for Barely Sentient
|
|
#
?
Apr 20, 2021 02:53
|
|
|
Slimy Hog posted:If they're your friends why are you still friends with them? Neither luckily
|
|
#
?
Apr 20, 2021 06:49
|
|
|
Protocol7 posted:Gonna rep my bachelor's degree in my title like it actually means something.
|
|
#
?
Apr 20, 2021 07:29
|
|
|
Carbon dioxide posted:
This except unironically. 
|
|
#
?
Apr 20, 2021 16:20
|
|
|
Hello ladies, I'm Volmarias, Bachelor Scientist 
|
|
#
?
Apr 20, 2021 17:05
|
|
|
Pollyanna, Professional Bullshitter.
|
|
#
?
Apr 20, 2021 20:05
|
|
|
Engineer, Xarn Engineer. 
|
|
#
?
Apr 21, 2021 07:21
|
|
|
HMS Queen Victorian, Bona Fide Artist
|
|
#
?
Apr 21, 2021 18:01
|
|
|
Woebin, almost B.A. (unfinished thesis still on an old laptop's drive)
|
|
#
?
Apr 21, 2021 22:06
|
|
|
bull poo poo more poo poo piled higher and deeper I dont have one for BA/MA. I guess PhD still works though
|
|
#
?
Apr 21, 2021 23:25
|
|
|
chglcu, four time community college dropout.
|
|
#
?
Apr 22, 2021 13:07
|
|
|
Achmed Jones posted:bull poo poo I thought 'bama was an insult as it is.
|
|
#
?
Apr 22, 2021 16:50
|
|
|
Sup goons. I'm pretty new to git and I'm struggling with understanding how to map its workflow to my own local workflows. At my company, I work in Matlab and Python and in internal tool development. Things like simulations and tool automation. So locally, I have a Matlab folder that contains subfolders for various projects -- SimCodeA, SimCodeB, etc. and similarly in Python, I have a top-level folder then subfolders for (eg) Automation1, Automation2, etc. If I want to put all this stuff up on github, do I make repositories for each project? Or a single Matlab repository and a single Python repository? Or something else? I'm not really sure how to think about this. As well, I get confused when banging this local approach against the branch concept: If I want to work on new project SimCodeC, do I make a new branch containing the folder SimCodeC, or, just add this folder in the "base" repository and work from there?
|
|
#
?
Apr 22, 2021 17:02
|
|
|
Cyril Sneer posted:Sup goons. I'm pretty new to git and I'm struggling with understanding how to map its workflow to my own local workflows. At my company, I work in Matlab and Python and in internal tool development. Things like simulations and tool automation. So locally, I have a Matlab folder that contains subfolders for various projects -- SimCodeA, SimCodeB, etc. and similarly in Python, I have a top-level folder then subfolders for (eg) Automation1, Automation2, etc. If I want to put all this stuff up on github, do I make repositories for each project? Or a single Matlab repository and a single Python repository? Or something else? I'm not really sure how to think about this. As well, I get confused when banging this local approach against the branch concept: If I want to work on new project SimCodeC, do I make a new branch containing the folder SimCodeC, or, just add this folder in the "base" repository and work from there? There's very rarely a single right way to organize repositories, and what you do should make sense for your own workflow. It's generally easiest to keep whatever you need to build and run a project in the same repository, but it might make sense to put multiple projects in the same repository. If you're the only contributor, you can do whatever works for you, and it's fairly easy to split and combine repositories as long as the split corresponds to the directory structure. You also don't need to worry about branches in that case unless you have some formal release process. How do you have projects organized? Do you have a release process?
|
|
#
?
Apr 22, 2021 17:21
|
|
|
How do you approach people who are never specific with what they want? For example, working on processing some data right now. I put together a script that checks a spreadsheet for some specific conditions, and writes down the affected row IDs into a separate text file. This is exactly what was asked. Verbatim, I was asked "Can we start with a list of Record IDs that [meet some criteria]?" So I produce a text file where each line is a Record ID that meets the specified criteria. They immediately pop back "Great, can we filter the original spreadsheet on these Record IDs now?" We could have skipped the whole churn cycle if they just said that's what they wanted from the start.
|
|
#
?
Apr 22, 2021 17:28
|
|
|
Cyril Sneer posted:Sup goons. I'm pretty new to git and I'm struggling with understanding how to map its workflow to my own local workflows. At my company, I work in Matlab and Python and in internal tool development. Things like simulations and tool automation. So locally, I have a Matlab folder that contains subfolders for various projects -- SimCodeA, SimCodeB, etc. and similarly in Python, I have a top-level folder then subfolders for (eg) Automation1, Automation2, etc. If I want to put all this stuff up on github, do I make repositories for each project? Or a single Matlab repository and a single Python repository? Or something else? I'm not really sure how to think about this. As well, I get confused when banging this local approach against the branch concept: If I want to work on new project SimCodeC, do I make a new branch containing the folder SimCodeC, or, just add this folder in the "base" repository and work from there? Easy path: slap everything into one repo, then you don’t have to change your workflow. You can separate things later. If you’re using GitHub essentially as a remote backup+change log then you don’t need branches either (though you might find them handy to keep changes clean).
|
|
#
?
Apr 22, 2021 17:30
|
|
|
I thought I knew better but I messed up when in the last interview stage they brought up "so what are you thinking compensation wise". I knew that I shouldn't say a number but I still said a number, even though it wasn't the specific number they wanted me to say. I should just not say any numbers at all. Dangit.
|
|
#
?
Apr 22, 2021 17:46
|
|
|
ultrafilter posted:There's very rarely a single right way to organize repositories, and what you do should make sense for your own workflow. It's generally easiest to keep whatever you need to build and run a project in the same repository, but it might make sense to put multiple projects in the same repository. If you're the only contributor, you can do whatever works for you, and it's fairly easy to split and combine repositories as long as the split corresponds to the directory structure. You also don't need to worry about branches in that case unless you have some formal release process. This is all uncontrolled so my stuff is not subject to any release process. Its mainly just internal tools for us engineers to dick around with.
|
|
#
?
Apr 22, 2021 17:46
|
|
|
In that case I'd be inclined to either do a single repository or a separate repository per tool. Your call as to which is better.
|
|
#
?
Apr 22, 2021 17:48
|
|
|
Really, git just gets you a history of changes. So would you like to see all the changes to all projects in the same list, or in different lists?
|
|
#
?
Apr 22, 2021 17:54
|
|
|
marumaru posted:I thought I knew better but I messed up when in the last interview stage they brought up "so what are you thinking compensation wise". Oh yeah that's the absolute worst question. There's really not a right answer. I got lucky that my current employer didn't take advantage of me since I answered super low.
|
|
#
?
Apr 22, 2021 17:58
|
|
|
smackfu posted:Really, git just gets you a history of changes. So would you like to see all the changes to all projects in the same list, or in different lists? It also depends on whether those projects interact with each other. If none of the projects actually interact, and they're involved enough that the commit history could get messy, you may want separate repos
|
|
#
?
Apr 22, 2021 18:10
|
|
|
Protocol7 posted:How do you approach people who are never specific with what they want? For me I would definitely say "next time could you let me know what you want the final product/outcome to be? it would have saved a lot of time" Also get in the habit of asking probing questions when people come to you with asks. If someone asks you to do something, make sure you understand why they want it.
|
|
#
?
Apr 22, 2021 18:11
|
|
|
prom candy posted:For me I would definitely say "next time could you let me know what you want the final product/outcome to be? it would have saved a lot of time" Forgot to chime in before, but definitely this. Even a simple "sure, what's this for?" can easily and innocently transition into them telling you what the gently caress they're trying to even do.
|
|
#
?
Apr 22, 2021 18:32
|
|
|
|
| # ? May 13, 2024 02:21 |
|
|
If they know enough about the problem to decide that this specific technical thing is the solution, why are they unable to do the specific technical thing themselves? I would try to answer that yourself first though, not every request needs to pass a court of inquiry before you start working on it. Since everything needs a crappy analogy, if I've written a letter and I want somebody else to send it for me (maybe I don't know the recipient's address but they do, or sending letters has to be done through their department), I give them the letter and I ask them to send it to whoever. I don't ask them to put it in an envelope.
|
|
#
?
Apr 22, 2021 20:05
|
|
