You launched a service catalog. Now no one’s using it.
The data’s stale. It’s “almost ready.”
And you’re wondering if this was all a mistake.
Good news is you’re not alone - and there is a better way.
Founding Engineer @LisaKC_ shares how: https://t.co/2qDdyvn8oh
A 2 hr flight is more like 6 hours and its always interrupted because you have to commute and pass control or whatever. 8 hr train ride is quite peaceful, gives you a big chunk of uninterrupted time and you depart/arrive in the city center. You can sleep and arrive refreshed or you can get work done, you even have proper internet.
Usually a big GCP stan but as of last week their traces have stopped showing log messages, just <blank>
Got a support ticket open for 1 week but apparently this is 'complicated' so no fix yet.
You bet this is a single line React typo, it cannot possibly be complex.
@umachingunde I know my father in law has mostly gone for a single letter abbreviation as a solution 😂
His mum also uses speech-to-text a lot as her vision isn't great, which is a whole new ball game
@ghaidar0 Ooh that's interesting, will definitely give that a go and see if it helps us (your memory is almost right - no next in our main app though just react)
Has anyone managed to get a storybook (or equivalent) that doesn't cause 'oh no 2 days of webpack pain' every quarter to keep it running?
We've got a great local dev setup for our react app but can't seem to get anywhere close with storybook.
What are we missing?
@ghaidar0 I also dislike how we have to effectively double maintain webpack configs, one for storybook and one for the actual app, when it feels like if you could share them it would make things like the updates half the effort
@ghaidar0 I just have a really strong 'are we holding this wrong' vibe as it causes so much toil, but all the alternatives seem to have the same webpack-shaped issues associated with them
@ghaidar0 General challenges:
* Every time we want to change something (upgrade a big dependency like TS or React, or upgrade storybook), it takes someone 1-2 days of webpack pain to get it back working
* It's incredibly slow to load, vs the hot reloading on our app which is super speedy
@Jack_Franklin This has crossed my mind, which is worrying given I'm usually incredibly anti this kind of thing. But it's really tempting to build something simple that we render in the same way as our app to save this pain...
If there was a library to do the 'wrapper' bit I'd be super keen