https://youtube.com/watch/...

Oh no no no....

Our JIRA is basically: Triage, grooming, ready for dev, doing, ready for qa, ready for pm review, ready for deployment, done.

We all triage together on standup the whole 14 person team. We all groom together on zoom (remotely). We grab cards from ready for dev and move them to doing as we see fit (the devs grab them) we typically grab what we're most comfortable with, but we all do everything.

When done, the same devs cross QA it (a different dev than the one that did the work), and when QA Approved, it goes to ready for PM etc then PM reviewed.

There's an agile back and forth process the whole way, changes can happen in QA review or PM Review.

Zero Micro Managing.

Edge is better now anyways, and VS Code now has the Microsoft Edge Dev Tools so you can run edge dev tools directly inside of VS Code, super handy.

We just wrote a fetch wrapper in typescript so we can do things like

const getThing = (): Promise<Thing> => {....

return Promise...

.....http(endPoint).get<IThing>()

-------------------

//called from inside TS Generators.

const thing = yield getThing();

And we used react-promise-tracker in our service layer so we wrote our own <Suspense thing where it's like

<Suspense tag={serviceTags.getThing} waitingElement={<p>Loading...</p>}>

{ store.thing }

</Suspense>

It's a money problem.

One code base can be deployed on all platforms this way, saving mountains of money. And if done right can be very usable (but has an extremely high learning curve on building performant SPA's).

If done wrong you end up eventually paying for 3+ apps anyways.

yeah nah,

const date = DateTime.fromISO(isoDateString);

const formattedDate = date.toFormat('MMddYYYY');

done

You all still look for jobs? I haven't looked for a job in 8 years, there's 56 of them in my linked in inbox begging me to change jobs. When I get burnt out or tired of where I work I just open it up and pick one that sounds fun.

Yeah I've got better things to do than create a social media site for equestrians.

this didn't age well, it's 2022 now :)

*updates contracts to have a line that says "not accountable or responsible for side effects resulting from code that is commented out or not understood without having consulted the author*

That's good management right there, the kind of company developers want to work for.

Joke doesn't logically compute. If I am putting something down I am exerting force to do so, as such, gravity is not necessary.

10/10, wrote a fishing bot for FFXI online in 2003 and caused the company to completely rewrite fishing in the game. Would recommend.

What country do you live in?

I've been in this boat and just never found a good place to work, but I've found them now and am super happy.

Additionally, I got into some active hobbies, like mountain biking, four wheeling, hiking etc and endorphins really helped me!

I'm working on a pretty massive project now, haven't really run into anything typescript can't do. If you leverage the full power if it's utility types, unions, and intersects, you can define a type for anything and I have a hard time finding something I can't define in TS, and if I did I'd probably just "any" it.

You can even define interfaces and implement them via keyof T so you can implement them as any type..

It's extremely powerful.

Entertain us with an example of the problem? Maybe someone else knows how to do that in typescript?

My biggest TS rant is that most of it is design time semantics and useless at runtime, and it's confusing to a lot of developers... I'm tired of explaining that "interfaces" don't exist in JS, and that if you http deserialize a thing to an IThing that doesn't mean IThing will adhere to that contract...

Typescript doesn't stop you from having to write types defensively. Like having a class constructor drop off invalid fields. etc.