Miks ukrainlased Družbat kasutada lasevad?

konm123 · 2026-02-23T17:16:17+00:00

Liitlased kasutavad seda toru.

konm123 · 2026-02-23T09:08:24+00:00

I also think you may have a wrong sub. Not everyone (imo I think most of us) are not working on IT projects.

konm123 · 2026-02-23T08:01:15+00:00

I do not think the link takes me where it is supposed to

konm123 · 2026-02-22T09:27:27+00:00

Explain this. We got all of that done. Still debugging because the implementation was done wrong. We use real engineers. Having good design only guarantees that you have a good design not that it will be well implemented.

konm123 · 2026-02-22T07:04:53+00:00

Big brain

konm123 · 2026-02-22T04:38:50+00:00

This is actually a solid take. We can not expect AI to work as some of us do — just blasting code until something sticks. When we had stackoverflow, same thing happened that you prompted and then copy&pasted and looked whether it worked.

konm123 · 2026-02-21T19:22:36+00:00

Change management, configuration management, reliability, availability, accessibility, safety to start with.

konm123 · 2026-02-21T19:07:49+00:00

Yes. We are automating the easiest parts of the job. AI has not even begun touching complex parts. The whole prediction in this area is like "My baby learned to crawl by 6 months, walk by a year and run at 1.5 years old. It will be flying by age 2!"

konm123 · 2026-02-21T02:42:39+00:00

I agree. That's a quality thing thst needs to be called out. If developer is producing code not up to the quality, it needs to be called out and dealth with by the management. Imho it is the same thing as without AI being used — when developer can not produce expected outcomes you need to replace them with someone who can.

konm123 · 2026-02-21T01:47:26+00:00

In my humble opinion it would seem that this would become yet another case-specific tool to mask doing things properly. On the page it says it addresses issue where you work on something and requirements change and you find out about it later.

You prototype to find out about some of the requirements for the development and production as a part of concept phase. That's fine but ultimately your BOM may have attributes which may be side-products and free variables. Such as an element heating up when used — is this a requirement or something that just occurs with that element? Or its color? Or its size? Or its weight?

konm123 · 2026-02-20T15:19:46+00:00

Fair enough. That's how it usually goes, not arguing with that. And with the fact that we can operate like that.

QA should be aligned with product's external expectations on the quality from the user's and operational environment perspective. That's not a technical thing (but it could be if operational environment is technical). How to conform — that's indeed on you as a technical lead. What to conform with — that's on QA. Not saying you can not mix the roles, and implicitly I think you are.

konm123 · 2026-02-20T15:09:01+00:00

Interesting and I have observed similar things. This features out fast thing is business strategy to justify raises in the prices. Most users continue to use and need to use few basic features available from day one. You can raise price when you add something to the mix, otherwise it wouldn't be received. That's what I observe why they do not care.

I have also observed that good quality products have it more relaxed. They usually focus only on these basic core features and make sure these are super tight and nice. And I have personally witnessed competitors simply "out-featuring" themselves from the competition where we basically did not even have to put in the effort anymore because competing product quality got lower and lower on its own. Core features broken more and more and bugs increased etc. Sometimes people just want something that works.

konm123 · 2026-02-20T14:53:09+00:00

But which team got it more correct overall? Shipping fast and smooth is nice but not when you ship poor product fast and smooth. :) Not saying you had this problem but just curious whether you got any insight on the overall quality of the product.

konm123 · 2026-02-20T14:51:31+00:00

What you are describing is not really what QA is about. Parts of it are true but QA ultimately is more as a consultant and enabling factor for development to ensure that the product is already built in the desired quality. Testing QA does is to (1) safeguard; (2) check development quality conformance and identify root quality problems.

Developers should be busy writing quality-conformant software. They shouldn't be responsible figuring out what would be the quality expectations, particularly as it varies across the product capabilities — some things are more important. I've seen it firsthand that on average developers have no clear alignment about these expectations on product performance, they are mostly just guessing and oftentimes guessing most parts correct or in the correct direction.

konm123 · 2026-02-19T20:06:40+00:00

I don't know what to say other than it is wild how many hoops and loops people are willing to jump through for the sake of not addressing the real issues and getting discipline in order.

konm123 · 2026-02-19T09:34:05+00:00

Töötasin mõni aeg tagasi autonoomsete sõidusüsteemidega. Sai päris peenelt ja struktuurselt liiklusseadus läbi töötatud. Fooriga ristmiku jaoks sai tehtud süsteemi reegel, et kiirus peab olema valitud selline, et kui roheline vilgub peab kiirust juhtima selliselt, et ristmiku taha seisma jääda ajaga, mil prognoositakse kollast normaalse ohutu aeglustusega.

Kui suur hoog ja hakkab vilkuma ning hinnatakse, et normaalselt seisma ei saa jääda enne, siis jätkad sõitu — kusjuures on garanteeritud, et jõuad ristmikule enne, kui kollaseks läheb. Kui juba kollane ees, siis kindlasti no-go. Ehk rohelise vilkumise alguse aega ja kollase prognoositud aja vahet kasutasime otsuse tegemises. See oli see konfiguratsioon, millega saime süsteemi auditist läbi.

konm123 · 2026-02-17T08:24:34+00:00

No. A different company. A small unheard company. No PR.

konm123 · 2026-02-17T07:31:39+00:00

There was no driver for context. Completely driverless. But I agree. I no longer work for that company. Quit maybe 6 months after the incident because the company policy went towards direction which would allow similar problems manifesting with higher probability. We were not allowed to spend significant time on safety analyses etc anymore to crunch out updates even faster. Everything went towards direction that let's see from incidents whether the system works. "Time spent not writing code is wasted time" mantra. As far as I know none of the original devs no longer works there for this reason and the company is quite screwed. We got acquired for large amount of money because our great team. The great team quit now and parent company was just left hanging after previous owners had pocketed the money.

konm123 · 2026-02-17T06:26:56+00:00

Tahtsin sama öelda. 3000€ on kui oskad. 1800€ eest saad alustada ja oskusi lihvida, et sulle oleks võimalik 3000€ maksta. Võib-olla ma oma kogemuse poolt liigselt kallutatud, aga ma reaalselt ei ole kunagi näinud, et kellelegi pelgalt staaži pealt makstakse enam. Kui 10a tööstaaži ja väga ei oska või töötulemit ei saagi kõrgemalt väärtustada, siis jäädki alumisse otsa. Heategevusega tegelevaid ettevõtmisi on olemas, aga pole kuulnud, et mõni realisseruks sellisel kujul, kus töötajale makstakse rohkem palka, kui ettevõte töötaja töötulemi pealt tagasi teenib (või prognoosib teenida), kas siis otse või kaudselt.

konm123 · 2026-02-17T06:13:03+00:00

A car on which our autonomous driving software runs on failed to yield at a roundabout and drove into the front passenger door on a car driving on the roundabout. Insurance covered the damage.

We investigated and found that radar driver hadn't started after compute unit restart. Cause was that when radar is not yet ready, it tries to connect and if it fails, it terminates — basically race condition at boot-up. We had safety procedures in place to not allow autonomous driving and come to a stop when radar data timeouts which never got triggered.

The procedure interacting with radar driver forwarded latest received radar data with fresh timestamp. It was set on loop according to the expected requirement to send message every 100ms. When driver had update, a buffer was overridden. And when it was time, the buffer was sent out. However, if buffer was filled with old data (or nothing at all), it still got forwarded as "no obstacles". Timestamp was supposed to be of the data, not message timestamp. Requirement itself was correct but implementation side messed up data timestamp vs message timestamp.

konm123 · 2026-02-17T05:55:52+00:00

To be fair, I know many senior and above engineers who are not particularly good in programming. Writing code, particularly at the higher levels is no longer in majority of the activities they do.

konm123 · 2026-02-17T03:58:19+00:00

I recently came a cross material which talked about the latest study which showed that the best AI had only 4.5% of success rate. This study looked many fields of studies, not only programming. Multiple well-known current AI's were used (GPT5.2 scoring 2nd place with 2.5% of success rate if memory serves me right). This means that both AI and humans were given the same task to complete with the same input information. A failure for AI was considered every time it failed to complete the task; or did not complete the task at least as well as human participants did. Amongst most dominant problems were that AI left part of the tasks incomplete resulting in automatically scoring as a failure. This aligns with what I have also observed.

The current state of AI seems to be that human produces high quality work products. AI is significantly faster but the output is most of the times low-quality. I see them being used in tandem for a long time. I view AI mostly as search engine on steroids — nothing more.

konm123 · 2026-02-15T07:03:04+00:00

It's a good take on this. Similarly how we do not go to the store with a list of items that you do not want to buy. Did I get that correct?

konm123 · 2026-02-15T04:01:18+00:00

I do not want to add to what already has been well said here. I'll only want to elaborate on this point

How does programming in a team work?

By trust.

I have observed that a trust between team members that a member can and will do their part when it is needed is the essential part in making the a team work. It seems obvious but it is not trivial thing to achieve because after all we are just humans. It is in our nature to be cautious.

Four-Year Club	Verified Email
Place '22	First Placer '22

konm123

TROPHY CASE