This is a status meeting, not a standup.

Standup isn't a meeting. If it's a meeting, you're doing it wrong.

yea my "standup" today was just popping into the devs office and asking one of them why he added another card to the sprint.

had kind of a surreal moment where he asked me if that was ok, and i realized ****, they'll actually listen to what I say. I just wanted to understand what it was about, and told him as long as it's related to this current release it's fine and as long as they're not overloading themselves.

they're kind of quick to close issues with 'fixes' that may break other things but I'm just keeping an eye on those for now. they've already done a lot.

i didnt make much progress on the bug i set out to conquer, but that was mostly because i can't figure out how the **** to make gdb work on a mac.

we had a company lunch outing today and my boss told me i'm doing a really good job so that's good.

Huh? It's literally a bunch of people getting together to talk about a specific topic.

It seems to only differ from any other meeting by being extremely short and to the point

My feeling is basically that if you think spending 10 (or even 20) minutes/day to get on the same page as your team and do basic communication then something is seriously wrong. Might be your attitude or how the team is structured/managed or co-workers or who knows.

My juniorness is probably showing here, but I like standups because they're fun. I like hearing what other people are working on, how they're progressing and so on,

This is obviously my subjective experience, but when I hear the word "meeting" I immediately think of moving away from my workstation to a different room where we sit down and talk about a topic for at least half an hour, usually more, and then after the meeting people often walk together to the coffee machine and continue talking.

A standup is more like when someone walks up to your table and asks you about a work related topic, you have a 5-10 min chat about it and then he leaves. It's an order of magnitude less disruptive to your workflow.

Ideally standups should happen in the team room and have almost no windup/winddown. It's 9:30, everybody stands up from their desk, forms a circle, takes turns to say: "Yesterday I did a, today I'm going to do b." and then sits down. If you need to move to another room, I think the concept falls apart.

I’ve always liked them too. It’s not a significant amount of time and it adds a lot to actually being a team.

We're in the middle. Never more than 15 mins.

I guess my team is small and our stories are more isolated cause I have no idea what I would say in 1min and how it would be of value to anyone else. I will review their pull requests and them mine anyways.

So do I. I also like to talk about what I'm working on. It motivates me.

Speaking of liking to talk what you're working about for motivation, I picked up a project this weekend that I kind of abandoned a couple years ago:



I dropped it due to technical difficulties, which I think arose from attacking the problem in the wrong way - I became too concerned early on with specific technical details, like using vector tiling to minimize bandwidth, and those were hard problems so I grew frustrated with using my spare time to do complicated ****. This time, I'm just starting with bad naive solutions and can improve them over time, which I think will be easier when I actually have something that's working to build on top of. I think eventually merging this with other data (i.e. presidential election results?) could produce some cool interactive maps.

An endgame sort of use for this I'd love to do would be "map of the world from X B.C. to now," but I doubt a comprehensive data set like that even exists right now, would prob have to be crowdsourced in a Wikipedia sort of way.

Yeah this is my approach in everything. Make it work, then make it work well.

I need to work on that as well. I find the most interest in over architecting everything but it basically means I get nothing accomplished

I went to a Maker Faire thing today and I was looking at one of the exhibits my son and I both liked, and thought, they did a good job on the idea and the electronics and it's fun and everything works, but, the workmanship is crude. If it was me, I'd have taken more time constructing the thing.

But, they actually did it/finished it/took it to a maker faire/etc. I never do.

Same deal. They optimized for making something that worked and as a result actually produced a working model.

nvm i'm an idiot and hate JS with a passion

Humble Bumdle has a devops bundle that may or may not be interesting... a lot of books for 15$, don't really know if the quality is equal to the quantity though. https://www.humblebundle.com/books/d...ent=cta_button

thanks for the hw help in the other thread guys.

thing i learned:

PHP has the most absolutely infuriating syntax of any language I have ever seen, ever. I'd rather program in LISP.

for instance, string concat is done with a dot instead of a plus sign like every other language ever. it caused me so many problems debugging because it's just so unreadable especially when you're throwing HTML in there.

Pfft I'd rather program in LISP than almost anything else, though

that leads me to a question I've been wondering the last day and a half,

at some point are we gonna just stop making new languages? should we? i mean it's just absurd and there are more of them every day. do we need any more of them?

some newer ones do some cool stuff. The Java VM is fascinating to me. But do we need more languages that build off the JVM, etc.? at some point it's just all syntactic sugar and most of it is all built on C anyway.

Um, hell yes. Programming language design is an extremely complex topic and we're evolving greatly and learning new things all the time. Learning new syntax is also not a big deal at all for most reasonable programmers, so the cost of learning time is well worth the reward when we put together well thought out and interesting concepts like the ones in Rust, or in functional languages, or even just simple QoL features in many/most modern languages at this point.

Also, no one likes the JVM.

you can accomplish a lot of those things without creating an entirely new language.

the jvm is interesting i never said I liked it.

Why stop before we've got it right?

i don't think new languages are bad. i think new javascript frameworks are ****ing annoying. like, who wants to learn Angular/Vue/React when they all do the same thing and it is basically just a power struggle where the creators gain fame/fortune and we get to learn new syntax.

XSLT FTMFW - most elegant programming I’ve ever done.