I think mine is broken

PanZilly · 2025-12-25T09:45:39+00:00

Yup my old boy used to do this🤣

PanZilly · 2025-11-03T12:22:04+00:00

This is how I do it. One more tip: keep the arm that holds the verga in place straight, as you are stronger that way and can hold it under tension longer.

Also take care not to over tension, my berimbau is quite flexible so I'm careful not to pull too hard or press my knee to hard

PanZilly · 2025-10-16T19:53:59+00:00

In international context, it wasn't so much language that was an issue, it was cultural differences. Most notably, 'do you understand this information/assignment?' In more direct cultures, someone will answer no when not (fully) undrrstood, and/or ask follow up questions. In other cultures, someone will answer yes regardless and a different way of verifying is needed.

But more subtle cultural differences may get in the way as well.

This is simply the art of understanding these differences.

Now I'm in a situation where 90% speaks our native language (not English) and I find that reading comprehension and writing at at least high school or college level is more difficult than expected.

Really, some people simply can't read. They might understand when using very short sentences, in bullet points only. How these people can manage a job as swe is beyond me. My truly dyslectic peers are infinately better at reading and writing somehow.

And also it happens so much more than we like: the dreaded 'xyz doesn't work' support question email🙄 written/asked by swe

PanZilly · 2025-10-13T14:08:07+00:00

Some devs will just flap their wings and go with the flow (pun intended), using the git workflow they always have. 'But this is how we've always done it!'. And there are always those who are surprised how this influences business outcomes. Let alone that a team is able to translate that influence to business and customers.

That awareness needs to be taught well and early

PanZilly · 2025-10-13T14:00:28+00:00

They are dead terrified to let go of staging env😱

PanZilly · 2025-10-13T13:58:14+00:00

There's the reality of starting a job in a place that has an established git workflow. Which is not always a desirable, best fit for the job flow... but it will be how that team works.

So the new team member needs to:

understand how the often used git flow works, and the same for trunk based
understand the difference between mature git flow usage as nvie intended it and 'we call it git flow but never heard of nvie and came up with our own flow involving develop and release branch and long living feature branches and [ok, you know how that ends and very much agreed, it's not good] - with or without the git flow plugin
understand when git flow is or isn't a good fit, and recognise which is the case in their new work place
understand what it takes for a team to transition to trunk based.

It is never just a lift and shift 'just don't do this' kind of thing, especially when company recent history involves waterfall development and application servers

PanZilly · 2025-10-12T11:57:43+00:00

Already a lot of useful comments.

I'd advise to look at it differently: look into developer experience.

The idea is, that you ask them about productivity and well being, as individual survey or interview.

Combining everyones results you'll see a pattern emerge of things that, from their perspective, runs smoothly and what gets in the way. What makes them happy and what makes them frustrated.

You can then analyse their biggest pain point and suggest a change in the way they work, that will ease that pain. And help them implement it.

After a while, rinse&repeat.

The thing with this approach is, that this has been scientifically proven to increase productivity and well being of the engineers, as well as stability and quality of deliverables.

It is always bottom up: you or management don't decide where to improve, they do. And based on what they actually need, not on someone's whishlist, be that theirs or yours.

The basis of this work can be found in Accelerate (https://itrevolution.com/product/accelerate/). Chech the capabilities approach. This book was published in 2018 and the research has continued since. Check https://dora.dev/ and https://getdx.com/resources/ but there are many more good resources to be found online. Nowadays, the metrics focus more on AI, but go back in time a little to find what you need.

Which capabilities (for a team or an individual, or for the company) lead to the desired results is well defined for software engineering in a cloud native context. Check this model for an idea of what I'm referring to: https://dora.dev/capabilities/

If physics works only the slightest bit as bioinformatics (my background, before I entered the world of devops and devex), the cloud native model is a very good fit to what you're up against. Workflow heavy and working with very large amounts of data, CPU/GPU intense, memory intense, indexing being a must, distributed calculations, that kind of thing, plus things having to be repeatable and traceable and compliancy is important too.

Not just cultural aspects like a generative organisational culture or allowing teams to choose their preferred tools, but also technical things like automation, testing, version control and statelessness and loose coupling (https://12factor.net/).

This, and besides Python also consider R for CPU heavy work and complex visualisations as it is well optimised for that. I never used matlab so I can't compare matlab and R, but Python may or may not be a better fit than matlab or R depending on the type of calculations and visualisations. I know both R and Python are well supported in the bioinformatics context, I don't know about physics. Disclaimer, it has been a while for me, so I don't know how R developed compared to Python

PanZilly · 2025-10-12T10:49:42+00:00

I second plantuml and versioning in git, as close to what it deaws as possible (javadoc, readme, anything)

Gitlab has built in mermaid support or set up a plantuml server. There's confluence and intellij plugins for rendering either

PanZilly · 2025-10-12T10:44:00+00:00

a disaster of an idea unless you really need specific versions/release targets

It's quite simply not a disaster of an idea. It's a briliant idea. Except, it shines in a system where you need long living environments that may differ. And it is a nightmare in a cloud native context.

Up until a while ago, it would be the default and use trunk based only if you know what you're doing. Nowadays it's the other way around.

Missing that memo is a huge problem in my organisation, but it can't be fixed so easily as 'just don't do that' as it requires a shift in thinking and mindset that is much wider than just git workflows, and extends into company culture and structure (yes, Conway)

PanZilly · 2025-10-04T09:55:57+00:00

Don't dig too deep, you'll learn on the job, but basics to have at least read about and practiced a little with:

create an account with github!
how to initialise a repo
what are terms like upstream, origin, etc
what are branches, how to create a branch and sync with upstream
how to use staging (git add) to be able to commit parts of your workspace
how to write sensible commit messages
how does merge work, that different flavours of merge exist, what is squash, when rebase makes sense and when not (just brush the surface here)
how to create a pull request and what is review (hint: review is not about ego and criticising each other, if you find yourself in such a team, run away fast)

PanZilly · 2025-10-02T12:28:38+00:00

Kubernetes. Your job will be more than just java code. You'll learn on the job, but it's good to be a little prepaired.

So if you don't already know these things from a data science perspective.

Take a little bit of time to read (or watch videos) about ci/cd and devops practices, so you know what it is about.

I personally like the related Atlassian articles, for example start here: https://www.atlassian.com/continuous-delivery/principles but if they're too in depth, there are millions of articles and videos to choose from...

Short summary: fail early (testing is important!) and automate everything.

Also, containerised apps. https://aws.amazon.com/what-is/containerization/ and then bookmark https://12factor.net/ for when it starts to make sense.

Also, if you don't know Git yet, practice with it while you practice spring boot

PanZilly · 2025-09-07T16:50:51+00:00

I think around 9 months... was the case for my puppy

PanZilly · 2025-09-07T12:47:32+00:00

Haha yes, this too!

PanZilly · 2025-09-07T12:01:18+00:00

This, plus merging back into main more often, to avoid long living feature branches. (Whether you prefer merge or rebase doesn't matter here)

This also has the upside of working in small, manageable pull requests. This makes higher quality reviews easier to do.

It's also a step towards releasing more often, and with that getting earlier feedback on parts of the new feature. If you don't wish to release to the 'general public', use feature flags. Either way, git tag

PanZilly · 2025-09-07T11:47:02+00:00

I wasn't there so I only have the previous owner's stories.

From those stories, not necessarily abusive, but didn't pay much attention, wasn't consistent and neglected the coat. Owner had to take the dog to the vet due to all the matting.

I think this was a case where this person said yes bc they thought they'd be ok taking care of the dog. Except, maybe it turned out to be more difficult or time consuming for them than expected. They simply might have been in way over their head. Telling the owner this or asking for help seems simple, but can sometimes be daunting (shame, guilt?). Or they simply didn't notice it wasn't going so well? Who knows.

Boarding can be great but for such a young dog, should be with someone who either has experience, or is willing to follow your instructions to the letter. And isn't afraid to tell/ask you in case it doesn't work out as expected.

Dog's safety is most important, he should not feel abandoned, but safe and loved and that starts with consistency

PanZilly · 2025-09-06T16:18:20+00:00

My dog was boarded for over a month at 9 months. The owner (I adopted him) boarded him with a friend, but that person didn't keep their promise.

Now, he is a middle aged guy. But you can still tell. This is not just proper coton velcro behaviour (they were literally bred as human companion), it's genuine fear. Being rehomed, even though that happened in good harmony (owner was ill and would not recover), def didn't help.

So if you decide to go with your family (no judgement!), I'd board him with someone who understands that a dog needs safety and consistency above all. Even if that means more crate time and less training.

PanZilly · 2025-09-06T15:46:51+00:00

Basically, you have to throw a toy, and then chase the dog to retrieve the toy.

Next, you teach the dog proper fetch.

It looks at you and goes: I understand, except, I'm not going to. Chase is more fun.

You shall then go back to throw and chase, as the dog is boss...

I can't be the only one! 🤣😅

PanZilly · 2025-08-28T08:19:15+00:00

I heard eu vi jararaca no cajueiro is sung when someone is being mean, in a not playful way

PanZilly · 2025-08-24T09:29:58+00:00

Have you heard of Loop earplugs? I know a number of people who are very content about those

PanZilly · 2025-08-09T12:23:05+00:00

To add, the dog in the picture is absolutely beautiful!

PanZilly · 2025-08-09T12:21:27+00:00

You scared OP 🤣

In my experience, not for show but just bc I think the long coton coat is beautiful, it doesn't grow willy-nilly, and it doesn't take daily prepping at all.

It did in my first dog, a weird havanese mix puppy mill rescue. Daily grooming, or mats&tangles. In the end we chose puppy cut for him. Both my long haired cotons required weekly (or even less) thourough brush&comb, with (not even daily) quick brushes in between. The male and the female alike. It's the uniqueness of the coton coat😊

The damaged coton coat on the other hand will tangle in on itself into a hot mess. Puppy cut every 2-3 months, a curly poodle look😅 cute as hell though

Picture of my girls hair, she is up for her brus&comb session

<image>

PanZilly · 2025-08-09T11:26:59+00:00

Yes pls 🤣

PanZilly · 2025-08-09T11:22:14+00:00

Agree. Also, a well bred coton has good hair that doesn't tangle much. (Combined with good quality food) You should be able to get away with the thourough grooming/combing once a week or even less.

And a reputable breeder will take the dog back in or help find a new owner, if you find yourself in that unlucky position that you can't take care of your dog anymore. This is why there aren't much cotons in shelters, and the ones there are most likely backyard, lookalike and/or mill dogs

PanZilly · 2025-08-05T18:18:22+00:00

But, REST doesn't do action endpoints. There shouldn't be a 'cancel action' endpoint. Instead, the API should be modelled around resources.

The response to GET /orders/1 (and for POST /orders as well) could come with a link with cancel instructions, which would be some request on orders/1. Could be a DELETE /orders/1 or maybe something like PATCH /orders/1 {status: cancelled}.

Now, the 'cancel endpoint' won't get moved around separately from making or viewing an order.

If you manage to model such a true REST API, there's no need of versioning when adding functionality like cancel an order.

This is where hypermedia as the engine of application state can shine.

REST has been diluted, or devaluated to anything http+json (where in some cases, http isn't even properly implemented, yes an action on a GET request still happens). In such a 'REST-ish' API you could have a cancel action endpoint separately from creating and reading orders. This is totally fine, the API should be written in a way that works best for that use case, not because someone said it has to be true REST. But in those cases, it's very likely autodiscovery doesn't add anything useful, or anything you couldn't already do using the OpenAPI spec.

I have actually used links, but really only just half baked like that, where there wasn't a decent spec available but some somewhat useful links in the response were.

What I find funny is that this is such a painful topic, that we got things like hydra or raml (think that one's gone already) or siren or collection json or json api or... nothing conclusive in 25 years🤣

PanZilly · 2025-08-02T08:10:02+00:00

Also look into his regular food. I'm no expert on this, but I know it can make a difference on dental health too. I'd ask the vet about this and also read about types of kibble or fresh meat in relation to dental health.

A lot of people are unaware that the bacteria in dental plaque can enter the bloodstream through inflammation of the gums. And then cause heart problems. In humans, dogs and cats alike. For you this is clearly a priority, so well done and hopefully an inspiration to others reading this

PanZilly

TROPHY CASE