Indexing multiple captured video streams with awarded action points and adding athlete/referee positions overlay. Stretch goal -- controlling PTZ camera for predictive capture of the high intensity actions.
No, action points I get either from parsing a video capture of a scoreboard or by pulling them over API, depending on which scoreboard/match management system is used.
I do plan to have a front-end for manual annotation of referee performance: correct relative position, timing, determining attacking/defending wrestler etc.
Perfection is not "perfectionism". Former is provable given set of constraint. Later is anxiety due to fear of criticism.
"We don't want to build the perfect solution." Can both mean "no need to cover use cases we don't care about" and "no need to deal with divizion by zero in a product, where a number is divided by the user entered number".
C1 can be achieved (I did it on 360 hours). C2 is academic level of language proficiency -- you have to either deliberately study for the difficult exam or get an university degree in German. Most of the Germans won't be able to pass a C2 test.
When a company sets C2 as a requirement, it can be interpreted as "must have a degree from German University".
That's not true, but it is a commonly shared myth. I've taken and passed C2 with the highest mark in every category (I moved here when I was a young teen, wanted to know if I would pass it after hearing years of people saying things like you're saying).
Most Germans would easily pass C2, although I think they'd have to be well-read/possibly university educated to get high scores (mostly need to be able to read quickly, give a semi-structured presentation and write a persuasive essay).
For what it's worth, I could run linguistic laps around all the other test takers there that day, and I assume at least some of them passed.
That's a really interesting experience. Lots of people in language learning communities have this argument back and forth for years. Have you ever written a longer piece about your education, preparation for the exam, abilities of other test takers?
For reference I scored ~C1 in German years ago (testdaf 4/4/5/4) and at that level there's no question at all about the vast gulf between me and an educated native speaker.
I've not written up anything, no. I think I'd have a hard time doing so without just feeling like I'm bragging about myself, which I don't like.
There's still a definite gap between me and native speakers, that shows itself primarily in the effort required, but I'm definitely near native (pass as German in all social settings, although an hour long conversation will usually tease it out due to my unfamiliar first name or small-talk topics, rarely but occasionally due to mistakes).
I prepared by doing two practice exams and about 5 filmed and timed practice presentations, and that was over preparing for me. Experiences vary, and I do think I'm a bit towards the outlier side, but it's left me convinced that the whole "native speakers might not pass C2" thing is overblown.
Hi, I am interested in language learning, and your first sentence caught my attention. I am currently learning german, do you have a blog post on your journey of learning a language in 360 hours? around 45 days if 8 hours per day. How were you able to achieve so much with so little time?
Cut the pace to 1 hour a week, than some bursts of two to four months of up to 4 hours a day two to three days a week -- that would be close to how I did it. 45 days 8 hours per day is beyond my brain ability to adapt.
I didn't interpret it as "automation bad". The invisible value, cancelled by automation, can also be negative.
Consider a doorman or a waiter in low-trust status based society: to get a service one must exaggerate status signaling and/or bribe the gatekeeper to be deemed worthy of a service. Kiosk doesn't accept bribes and you can trust "no vacancy" from kiosk more than from the doorman.
CTOs noticed it. When product pipeline is empty, because engineers finished all the outstanding tasks, the engineers are awarded with more work: "The new software engineer is a product leader. Someone thinking about what the product is, not just how it works", or, in other words, engineers are going to be tasked with putting more content "the what" into the product pipeline.
Nobody wants to hear anyone's opinion but their own, we have a poverty of effective communications.
Nobody wants to communicate because it is pointless to communicate: what you say will be misunderstood, it will be repeated incorrectly and attributed to you, people will play games with your messaging and with you for trying to communicate.
The management bully game activates, and they all participate in keeping the engineer down.
This is normal at every engineering organization, it is lord of the flies.
And this is how we educate people, This situation is created. All because we refuse to recognize that learning how to debate controversy and learning how to manage disagreement is completely unrecognized as a valued skill.
So we avoid controversy and any disagreement is an opportunity to bully and force one's way. Which is completely avoidable, with basic effective communications training. Debate to understand, disagree to learn.
I’ve worked at such organizations, you’re not wrong about them. They are not all that way. Many are, but the issue is the people not knowing how to or being comfortable with “disagree and commit” and other communication strategies.
This sounds like dysfunction. As engineers, we're not necessarily any more correct than anyone else. But we do have a seat at the table, and good organizations at least listen.
OK actually thinking about it I have worked at one organization where they did listen, other than startups of course, but even in those the people who had power to implement things tended to consider the ideas of non-programmers more important, which maybe they were.
Not sure how it is doing now about listening to programmers because it was sold off by the parent company and then became really successful and grew a lot, so it is essentially a different company.
I have a feeling it is less likely to listen to things now though.
Yup. This was a very useful precursor to the AI era: telling engineers they're worthless and they are there just to implement the specifications and ideas drawn up by more important people. Shutting them out of the earlier discussions and only informing of the project way down the road
Now they're just trying to reduce us to idiots shovelling coal (specs) into the furnace (LLMs)
Has that not been what a senior SWE is? You’re making it sound like engineers need to be asked to implement features rather than contribute to design. At my company, if you are not coming up with new features or applications, your days are numbered.
Depends on the organization and on the SWEs. I do share your understanding, which is making me unfit for organizations, where the authority over "what" is firmly held by POs and the whole vertical on top of them.
Your average mid to senior SWE is too far from the actual use of the product to actually do that well though.
There are some smaller businesses and selectively structured ones where that's not the case but for the most part organizations keep engineers from interacting with the customers enough to really know what the customers need and want.
There are some cases where a savvy engineer can say "well if I unify X then it'll be trivial to make Y self service and that'll make redundant an entire category of support tickets" or "we've been getting a lot of requests for X, maybe Y should be extensible so that those can be trivially accommodated" but by and large engineering teams are not positioned to have the knowledge to identify these things. And this is mostly an intentional organizational architecture decision.
Considering all the possible levels of abstraction software can represent, I'm imagining it as a fractal. The worst case - a mistake can be introduced by generative AI at any of the abstraction levels at any moment. Meaning, at worst case the whole thing has to be in the head of at least one person to validate the result against. The moment a project is growing beyond a single person capacity to hold it in one head possibility of plausibly looking error introduced at any abstraction level is added to the usual multi-engineer coordination costs.
Personal (as in, "for personal use, not a product") conversation partner -- I speak in German, one level is correcting the mistakes, allowing me to reformulate the statement, another level is responding to the intended idea. Rinse, repeat.
I did a project with Claude. With unit and integration tests, whole shebang. First in Python. Reached 25% of MVP and understood that I spend more time fixing subtle type mismatches (int/str, function signature vs call etc.), than adding new code. I've switched to Go (note: I've also made sure tests/frontend/backend code are built within the same context) and finished the MVP, without encountering the same problems even once.
Vacuuming working age population from Ukraine since 2014. Poland did everything right, while Ukrainian governments and businesses were smirking "What are you going to do?" during salary discussions.
Over the past 4 years, millions of Ukrainians have fled there because of the war — many of whom had businesses and money in Ukraine and are integrating seamlessly into the Polish economy. Almost the entire Ukrainian IT sector that used to operate on an outsourcing basis is now there. Before the war, Ukrainians were mainly a source of cheap labor there, while Poles were doing the same work in other European countries.
And since Ukraine is a bargaining chip in the current war, it is in the interest of all its neighbors for Poland to become strong, so that the Russians don’t cross the border.
"What are you going to do" was a phrase you could hear in Poland as well in 90ties and early 2000th. What differentiated PL w/ UA in my opinion is 2 things:
1. Lack of oligarchy - which in fact was not obvious outcome and little bit of luck on our part and little bit of cultural zeitgeist of 90ties and 00ths.
2. No east-west dithering - PL knew right away to which economic and cultural sphere wanted to belong
Not much I think. I had long discussions about it with my Ukrainian friends: we came to the conclusion that it was mostly the fact that Ukraine was part of the USSR (much harder crackdowns on opposition, actually including the church) - and that also built stronger ties with Russia. A lot of people forget that USSR really was a multicultural empire: you had families where in the 90s siblings abruptly woke up in different countries: Russia, Belarus, Ukraine.
Post-2022 some of those families stopped talking to each other, the propaganda is stronger than the family ties. Before the situation got clarified by falling bombs, the east/west choice was much harder.
> Post-2022 some of those families stopped talking to each other, the propaganda is stronger than the family ties.
I don't think it's a matter of propaganda. We're talking about totalitarian dictatorships on both sides of the barricades, where such communication with relatives on the other side have very real risks of decades in prison or even death.
Lack of oligarchy is starting to look like an absolutely critical ingredient, and it's lucky that Poland escaped from the PiS trying to turn it into an oligarchy.
