sarcasm?

Github*********

more like nithub

Fancy UI? Nothing much imo. If you need that stuff, use Gitlab. Gitlab and Bitbucket throw in free private repos for small teams.

Sent from my SAMSUNG-SM-G925A using Tapatalk

Which do you consider more readable over time, for a team of differing exp? And how much so?

vs non-curried
Appreciate the feedback, my thoughts in spoilers

does anyone have a recommendation for note taking? for example, when i make a pull request and other devs comment on it (fix 'x', do this instead, etc) these comments end up being destroyed once the branch/commits change or get merged.

i want to preserve them somehow. not sure what is the best way.

i've been taking screenshots of stuff i want to reflect back on.

I think curried/partially applied functions can be handy but it's hard to find appropriate use cases for them.

There tend to be a lot of n00bs in JS. There is one person on my team that has been at the company for almost a year and he still seems to have trouble with anything beyond basic JS. I helped him w/ something a while back that ended up being a good use case for partially applied function. You could tell he was a bit googley-eyed wondering how it worked.

With all that said, I would base my decision on the capability of the rest of th team. If your team is not very capable, I would tend to avoid them. If they are capable I would lean towards using them.

I would almost always write it the 2nd way myself, wouldn't be slowed down by seeing it the first, and have worked with people who would consider the first one fancy play syndrome.

After reading this, I did find myself considering using it in some code I wrote today but was worried it might look like the fps I mentioned.

^^

just use multiple args unless it somehow makes testing or config easier imo

we had a department meeting today to discuss a new product that a potential client has only seen POC for. so now we need to make it production quality.

so, the CTO was laying out what he wants done, etc. I understood everything discussed in the meeting, what the problems were, and what needed to get done. Then when we got to talking about scheduling, my boss chimed in and said "<myname> has been doing 1 week sprints and they've been really successful" so I got a nod there.

Initially, I posted in here that when I initially recommended a 1 week schedule he really didn't like my 1 week vs 2 weeks idea but let me do it anyway. I had a lot of good reasons for it and it seems like it's working. The backlog on the project I was on has been more than halved since I started this.

I guess he's on board with it now so that felt good to get the nod too. I think I can do this. My boss is gonna be gone for the entire month of july so I'm not really sure what's going to happen then but I've decided to forsake my schoolwork and throw myself entirely into this job, which seems to be paying off. My grades are gonna suck badly though, but meh. I have such a high GPA anyway, I already have a job, and I only need D's this quarter to graduate, and I've got at least 2 B's locked in already so barring some major catastrophe I think I pulled it off

To paraphrase - A POC takes 90% of the development time. Commercialization takes the the other 90%.

Do some research on 1 week vs 2 week sprints. If I remember right you were doing 1 week sprints to minimize the impact of meteorites from the CTO, you may want to revisit the decision if you have a clear objective in place. You should gain velocity on a 2 week sprint because you are halving the amount of ceremonies for the sprint without doubling the amount of time the ceremonies take.

The main reason now is that two of our main devs have severe procrastination issues. I told my boss that if they’re going to wait until the last two days to do things, we may as well halve the time. He laughed and agreed

I think one week wont work for some of these larger stories though unless i can figure out a way to decompose them

That's what standups are for. Asking them if they are blocked and letting them say what they have finished since the start of the sprint. This becomes more evident if you are tasking stories to get a sense of progress for the sprint. Basically, if everyone knows these guys procrastinate someone's not managing them very well and designing your production process around them seems like enabling...

yea probably. They’re just likely to say “oh havent gotten to that yet” or “it was more involved than i realized” which i suspect is BS but until i know the project better i wont know what the issue is

How many projects are they working on? If you've got guys on multiple teams that's going to make everything more complicated. If they aren't on another team and are working on something else, have them write a story for it and add it to the sprint as discovered work. If something is "more involved" have them re-task the story or re-point it and adjust the schedule.

One of the benefits of Agile is that it is super transparent into what developers are doing day to day and should encourage them to not try and do in 2 days what the rest of the team has been doing for the last 2 weeks. But for that to work whoever is running the standups has to be asking those questions. A couple of days of essentially being told they did nothing yesterday should trigger re-evaluating the sprint, there shouldn't be that much slack in it.

you dont decompose. you "slice" them. lol. actually, its "vertically slice".

anyway, thats a pretty serious accusation about those devs straight up not doing their work.

Meh, not really. I find it's a pretty common thing. The good devs can get work done very quickly and don't get rewarded for doing more so many of them procrastinate.

Fair points but i dont think it’s a good look for me to go busting down any doors right now. I mean they’ll freely admit they procrastinate - like i said it was a major reason we all agreed to one week sprints. I had the convo in the meeting with them and with my boss privately.

If things weren’t getting done, ok, but i mean it seems velocity has yuugely increased in the last month.

Now that i’m gonna be on a real development project this summer with a larger team, i‘ll try to nail down some of these things a little better

One positive thing that came up last retrospective was my boss admitted that the interruptions Imposed by him and the higher ups are bad for overall progress

If they can get more work done in a sprint they should have more points to do.

I created a super basic script to get my vim config up and running, say I was going to do an interview at a place and they gave me a machine to use, or I was in a situation where I needed to use another person's machine, would this script be rude to run on their system?

Yes, you're changing their environment without permission. If someone changed your environment without asking how happy would you be.

I would be fine with this because I made a copy of everything I changed, and could get everything back in 5 secs.

I do think though I should probably make another script that takes whats in .copyVim, and puts it back how it was, removes the sym link and leaves it as was.