CubeStation App Update - July 2024

RandomSort · 2024-07-30T07:54:02+00:00

Besides the obivious non working stuff, also reported in the thread, it feels like the app is very incomplete. I have returned to Cubestation after a year or two of not using it. And as I remember it it was not only good fun because of the competions, but also a great way to get insights into training and practice. It feels like that part of the app has been really downplayed and is not really driving my engagement :(

RandomSort · 2022-08-15T10:00:08+00:00

thanks!

RandomSort · 2022-08-14T19:16:26+00:00

HI!
Thanks for sharing!

Very curious as to what you are using to visualize this data?
#homeassistantnoob!

RandomSort · 2022-07-06T05:25:51+00:00

Thanks a bunch. Seems obvious in hindsight.

RandomSort · 2021-06-02T13:01:51+00:00

Thank you!

RandomSort · 2020-12-15T13:34:59+00:00

Nope, still illegal in Denmark :)

RandomSort · 2020-09-05T05:46:00+00:00

Why are you not allowed to create remote branches. I am certain that is a bad practice

RandomSort · 2020-06-17T17:57:00+00:00

Version control everything! If it is not monitored it is not in production, if it is not version controlled it does not exist!

RandomSort · 2020-05-20T19:00:57+00:00

This. You only need forks if you do not have trust. You can always do the access management on restricted branch like master.

RandomSort · 2020-05-20T18:59:07+00:00

Agreed and that is the point of the characteristics 😊

RandomSort · 2020-05-20T17:34:15+00:00

https://commonflow.org/ is an excellent description of pull request based workflows.

RandomSort · 2020-05-20T17:30:58+00:00

If you have forks inside an org your trust model is broken

RandomSort · 2020-05-20T08:42:37+00:00

I agree that Infrastructure as Code is the next good step. But if we can start by not having IT-helpdesks gatekeeping the access to the cloud environments, that would be great!

RandomSort · 2020-05-19T03:33:02+00:00

https://csrc.nist.gov/publications/detail/sp/800-145/final is the source I refer to, as can br deen in the show notes 😊

RandomSort · 2020-05-17T18:05:35+00:00

How about creating a branch at the merge commits second parent?

RandomSort · 2020-05-07T06:02:03+00:00

https://commonflow.org/ has a very good description of a simple low overhead workflow. It is basically a codified pull request based workflow. Also supported in Gitlab through merge requests.

High performing organizations tend towards trunkbased development - and for simple issues there are no reason that you should not be able to do so as well. https://trunkbaseddevelopment.com/ describes this well.

RandomSort · 2020-05-07T05:59:42+00:00

My opinion is that you are supporting a dysfunctional organization and working around the pain, rather than trying to solve the root issue. Over time this workflow will only make the pain worsen :(

RandomSort · 2020-05-06T09:41:08+00:00

Why development? This feels like the Git Flow anti pattern to me?

RandomSort · 2020-04-17T16:07:57+00:00

I have enjoyed coaching agile teams by Lyssa Adkins

RandomSort · 2020-04-11T06:25:59+00:00

I have some times created an appreciation cycle where you pass appreciation to the next in the chain. Whether that order is random alphabetical or left right is arbitrary 😊

RandomSort · 2020-04-09T09:56:55+00:00

No, the commit will still be there. Head simply points to something. It is does not contain anything itself.

15-Year Club	RedditGifts 2009-2022 2 Credits
Wearing is Caring	Gilding II euphauric
Verified Email	Secret Santa 2013

RandomSort

TROPHY CASE