![](https://lemmy.world/pictrs/image/fe974612-63e6-41bc-af1d-3f636932448b.jpeg)
![](https://lemmy.ml/pictrs/image/c0ed0a36-2496-4b4d-ac77-7d2fd7f2b5b7.png)
It me
Some say that giant Koreans don’t exist.
It me
Yes. Tuesday is the superior day.
You’ve gotten over the jarring shock of Monday, and nothing is happening in your life on a Tuesday night after COB.
could be a fun project for someone with a severe lack of sanity
Does this actually even work any more? I figured most things protected against it nowadays.
Vim is like the Hotel California.
Same. I was a Perl dev back in the day. It’s excellent for massaging data.
And you avoid making an app that you show to the customer for the first time only for them to say, “What the hell is this?” My company used waterfall for the longest time, and this happened several times. It was really frustrating.
Thanks for the link! I’m really close to pulling the trigger on this.
Absolutely. Touch would just be a nice extra feature to me.
This was another route I was thinking about. Any idea how hard it is to do now?
Yep, just learned that!
Intelligence is knowing that tomatoes are a fruit. Wisdom is knowing that they don’t go into a fruit salad.
They make sense.
I wonder how you’d even implement that. Like maybe {! At the beginning.
That’s interesting!
The fact that it allows comments is really, really handy. I used to be a JSON advocate until I realized this one useful piece of info.
I just had to go look that up. Yet Another just seems to make more sense, which is why I think a lot of people think that’s what it stands for.
Someone would look at our process and say “that’s not agile!” and they might be correct, technically speaking. I don’t personally care what it’s called as long as it works.
We agree to requirements up front with our customer; we might change stuff as we go along if our customer realizes that what they asked for won’t work (this happens occasionally), which is fine, but otherwise we don’t let them change stuff around on a whim, and we don’t allow scope creep. If they want a new feature, that’s version 2 (or 3, or 4).
We don’t meet very frequently. We do check in to make sure we’re on target, and deliver features incrementally when it makes sense to do so. We do sprints. We talk about when things are working and when they aren’t, but only when we think it’s a good time to do so.
At the end of the day, you need to tailor the process to your needs and what makes sense to you and your team.