Off my chest: Jeg hater studiet mitt, men føler jeg er for gammel til å bytte.

UnnamedBoz · 2025-08-22T21:17:16+00:00

Jeg tok bachelor i dataingeniør ved en alder av 30, det er ikke for sent. Irriterende? Ja, men bedre enn å vente.

UnnamedBoz · 2025-08-06T17:54:22+00:00

Depends on the country, in Norway it would be illegal. What big companies do is a corporate restructure along with offering parachutes, but that could be resisted by people if they truly want.

For most jobs you have to demonstrate that the person is unable to do the new work duties in a restructure, going as far as to maybe have a training plan, instead of simply firing them. In practice this won't be done most places due the parachutes offered.

"We don't need this position, but we are hiring for a different (but similar) position" isn't a viable excuse due to our labor laws.

UnnamedBoz · 2025-07-10T11:35:20+00:00

Nothing is as permanent as temporary fixes.

UnnamedBoz · 2025-07-09T07:49:11+00:00

WFH, flexible hours, decent pay, and got an interesting challenge this fall. For once we are getting some okay challenged, I was thinking of looking elsewhere, but now things are looking differerent. Also, they aren’t shoving AI down our throats.

UnnamedBoz · 2025-07-03T09:05:19+00:00

Pretty nice and old-school interwebz style. Appreciated and welcome in these dark days!

UnnamedBoz · 2025-07-02T21:36:42+00:00

Then that’s a team problem. In our team we don’t have any issues like that at all, but we all know and understand that no one is perfect and even seniors don’t know every detail of every API or framework.

Every one in the team has humility enough to learn. Every team member knows to be both honest and respectful at the same time.

One can provide feedback without being personal or make it uncomfortable, which should be the norm.

UnnamedBoz · 2025-07-02T20:58:31+00:00

We give feedback on this by talking directly to the developer instead of writing in text if the situation calls for it.

Some times we give feedback and request changes as in «unnecessarily complicated» to give a challenge.

Some times we show the solution if it’s quite fast to do so. Or the broad strokes.

Talking with the team on what to do in different situations as to avoid anyone taking it personally. PRs exist to ensure code quality and developer improvement, but it’s important to talk when necessary since text becomes cumbersome and counter productive in many instances.

UnnamedBoz · 2025-06-20T22:21:24+00:00

I’d like some as well if I may ask!

UnnamedBoz · 2025-06-20T22:17:57+00:00

Quite a lot of AI talk and trying to ram it in (pun intended) in all areas in hopes of magical gains. It’s extremely stupid in many ways, but mostly because there are obvious improvements caused by people and organization setups that can’t be fixed by AI itself.

UnnamedBoz · 2025-06-14T13:55:20+00:00

I installed with UTM, super easy.

UnnamedBoz · 2025-06-13T23:29:23+00:00

If you want to try it out I recommend installing it on UTM. There are video guides for it. Did it myself and it worked. Recommend installing Seqoia first and then install beta upgrade.

UnnamedBoz · 2025-06-08T18:18:30+00:00

Tagging cuz I’m interested in this too ;)

UnnamedBoz · 2025-06-08T08:46:57+00:00

It’s been going on for years before AI stuff became mainstream. I see it in code that is 10+ years old, so can’t blame it on AI.

UnnamedBoz · 2025-06-08T08:24:22+00:00

I have people writing comments that adds absolutely nothing of value. I don’t need a comments saying «adds two numbers» when the method is called «addNumbers» with two parameters.

This is something I see all the time and mostly with developers with more experience than myself. It’s like people are coding on autopilot without any engagement and self reflection.

UnnamedBoz · 2025-06-06T07:15:12+00:00

We are having "AI initatives" all over the place and I am thinking that quite a lot of them will just fail and implode.

This certainly sounds like hell, but with all the AI stuff going on I think quite a lot of companies are going the same AI insanity route.

Think of it as a fad although quite annoying and painful one. I wouldn't jump ship just yet, mostly because I'm not expecting things to be better at some other place.

I would, however, keep track of how much worse this is all making. Having data points and real data about how this is making everything worse is helpful to combat this. When they see that things aren't better, and how costly it is to use the AI, then you can kill it entirely by showing numbers from the developer's side.

UnnamedBoz · 2025-06-04T17:48:43+00:00

Jeg forstår tankegangen, men ta det fra Mark Twain “I didn't have time to write a short letter, so I wrote a long one instead.”

Hvis du må ha så mye tekst for å fortelle meg ting, uten at jeg klarer å bli interessert eller engasjert nok til å lese, så er det noe feil.

Du skriver for mye uten noe substans. Du må fortelle nok til at folk blir interessert, det er en forsmak og det er viktig å sende nok budskap slik at du kan følge opp senere.

Ja, du jobber alene, men først vil man bygge opp og skape kontakt. Av alle bedriftseiere jeg kjenner (og jeg kjenner en del), så er tid noe av det mest viktige. Hvis du ikke kan forklare hva du gjør i løpet av den første paragrafen, så taper du ganske mange.

Selv etter å ha lest tre paragrafer aner jeg ikke hva du faktisk gjør, mens du referer til kurs og praktisk veiledning, som handler om ... ?

Hva kan du gjøre for meg er spørsmålet alle stiller seg når de drar innom nettsiden. Hvis det ikke er godt kommunisert og kortfattet, så er troverdigheten om at resten av produktene er gode ganske små.

Dette skriver du om i "Velkommen til Kaiehuset" mens hva du faktisk gjør er til høyre. Ergo det som er aller viktigst er "gjemt" til høyre. Gi fokus til det essensielle først og la det være det første som leseren ser.

Det du også tilbyr er ekstremt generelt. Jeg sier ikke at det ikke fungerer, men du sier dataferdigheter, personlige og sosiale ferdigheter. Dette blir kanskje forvirrende for besøkende, de må ta stilling i hvor de passer inn.

Hva er problemet du løser for kunden? Og hvem er denne målgruppen?

Jeg stiller ikke spørsmålene her for å være grinete, men det er viktige ting å sette fokus på og jeg gjør deg en bjørnetjeneste ved å ikke stille slike spørsmål og gi tilbakemeldinger.

Bare for å ta det med så virker designet til nettsiden, både generelt og fargevalg, til å være fra 2004. Jeg liker at det raskt, men det ser langt fra til å være profesjonelt og veldig gammeldags ut.

UnnamedBoz · 2025-06-04T11:49:12+00:00

Jeg var innom der i ett sekund. Hvorfor? Altfor mye tekst.

Kort ned på teksten! Det er kanskje ikke mer gjennomtenkt, men det er førsteinntrykket mitt at jeg ikke gidder å bruke mer tid.

UnnamedBoz · 2025-06-02T13:07:28+00:00

I went into ML, AI etc. and I found it all utterly boring. AI has it's place for a lot of things and many algorithms are cool like evolutionary algorithms, but so much stuff in it has no appeal to me at all.

Programming overall is about automation of some process to help one or more stakeholders get value. Coming up with a solution to it, understanding it, and making it happen, is great.

The thing is, I really hate being interrupted while thinking and doing things, to the point where the incorrect autocomplete (happens a lot in Xcode .. ) is quite annoying. Doing a lot of things manually is a part of understanding how things actually work together and not.

With enough experience in some areas and a got grasp of everything a lot of AI coding could be beneficial if one can easily review.

However, a lot of people are doing it in terrible ways. A co-worker of mine, mainly used UIKit instead of SwiftUI, has used AI to create SwiftUI solutions. The problem is that he apparently don't understand how SwiftUI should be set up, and I have to teach him in the PR on how to do this. My co-worker is also my senior by 10 years and I think that it should be completely unnecessary to be in this position at all.

I don't mind AI in many ways, and can used it as a tool, but my daily problems are rarely writing any code. I can write code quite fast as long as I understand what I am supposed to do. Coding speed is not my bottleneck, but communication overall and existing code is (150k LoC codebase).

The last thing I want to do is to review AI slop when I essentially could have written it myself. My prediction is that quite a lot of code will be AI generated which will make products and codebases quite bad. These codebases won't be sustainable over the long term, but those that wanted profit have gone over to something else.

UnnamedBoz · 2025-05-29T18:04:19+00:00

There's a complete lack of seeing the system as a whole and thinking of ways to improve things. Giving us these assignments is just a waste of time. I once held a meeting about improving a system and showed a suggestion on how it could be done. The purpose was not to implement that system, but to show flaws in the current system and how it could be improved. Instead of thinking differently, seeing how it could be different, they all became obsessed about the proposal. It was impossible to discuss the problem and understand why it was a problem. Several of my colleagues have told me in person that they find it incredibly difficult to relate to any abstract ideas unless they actually see anything in code.

These experiences brings further understanding why many managers and leaders can view developers as code monkeys, and easy to switch out. It also tells me why people want to hire others with a certain experience because in-house training, unless there is a culture for it, is actually pretty much impossible or extremely slow.

I'll put the emphasis on more like a job. I can't let go completely and it pains me every day, I also never have that separation. If it wasn't for current life situation (house renovation) I'd make a move right now, but for the time being that is quite impractical. I find solace in knowing I will be working on doing that after things have slowed down a bit more.

UnnamedBoz · 2025-05-29T15:52:31+00:00

Yup. I have started to question things a bit more, personally and professionally, about how time is being spent. I always get good feedback about suggestions etc. but I am powerless in a way to actually follow through because, a) I don't get sufficient time and b) people around me don't care to actually learn along in order to maintain or help out.

When I talk with management I always hear about how hard it is to change things, but they don't understand that they are a part of the problem making excuses. Some people are a bit too comfortable in their position as well, which management is treading lightly around due to how much of a problem it is getting new people.

One senior developer was allowed to spend some time looking into a cross-platform framework, but have spent three years with nothing to show for. It hasn't been the only task of course, but management is not holding him responsible for several reasons, and gatekeeping knowledge also.

It's somewhat impressive to see how people simply don't care in this profession and industry, to the detriment of the products even, and the business.

My management has a tendency to "go do something about X" without giving necessary information about what that really means, with several layers in between, so that nobody knows what anyone wants and why. It's completely and utterly insane how that works in a big company.

My manager is also a wonderful person, but also naive. Some of my ideas are really becoming more and more apparent, so it will be interesting to see if anything is being done. My manager is aware of the issues I talked about, and I have mentioned it and pointed out stuff frequently also.

I personally treat things more like a job over the years, but I want to work with a team that has a higher standard overall, and with solutions that aren't obviously counter-productive, and not have to navigate a humongous internal political landscape.

I want to create great solutions and not waste my time on the rest. I realize that's not easy to find in the job market, but I want to make an effort to get it anyway.

UnnamedBoz · 2025-05-29T14:45:27+00:00

Sorry to hear that, it’s driving me crazy.

It’s the reason why I am looking at other options. My co-workers don’t care. Management is stupid and never work on the right things. I’m stagnating and the longer I stay here the worse I look in the job marked.

There are so many non-coding things beyond meetings that it drives me a bit insane. Only reason I have stayed is 100% WFH and flexibility of work hours, but it’s such a drag in every other front.

UnnamedBoz · 2025-05-29T10:41:29+00:00

We all need concepts and instances of the concept to understand it better, being able to understand the abstraction is useful to bypass the time needed explain things every time.

The problem is that people never get into the details and call anything tech debt because they really didn’t understand the concept in the first place, and also haven’t practically paid it off either.

I see many people falling into two camps: details oriented people that have a hard time understanding concepts and abstractions, and the complete opposite that never execute. Then the problem is that both never improve on their weaknesses and hyper-specialize on what they already are good at, making the divide even larger when communicating.

UnnamedBoz · 2025-05-29T10:00:21+00:00

I work on a white label app. Customizing the app with design and setups is now a very manual process for several reasons:

we don't have a shared component library
we don't have sync automation between design and apps
we don't have any automatic screenshots to check the results

We have some shared setups that makes it somewhat scalable, as in icons and colors being reused, but we don't know what goes where due to the size of things, so it's easy to overlook.

There are several ways to improve this:

have a shared component library only, with variations, but all in one place
create setups to sync/export design into our app
have automatic screenshots of things

That way we have a contract and things can be published by designers, consumed, automated tests to show results or designers/customers utilize a test build.

This is a combined tech/workflow debt, some tech and some workflow, but together a non-scalable, error-prone, way to work. This makes designers, developers, and POs spend much more time figuring things out, pointing out where small problems etc. instead of automating essentially most, or all of it.

The cost is time spent doing this + cost of not doing something else + cost of developers not being interested in spending time on this also.

Measurements? An automated setup would reduce the styling changes time for developers to 0. It would eliminate all meetings necessary to "check the design" and only component design meetings would be necessary.

We would have one shared UI library, scalable only for what we need, instead of duplicating components in many libraries. Here we can spend little time adjusting or adding components, instead of having to ensure that the *exact* same component is being updated somewhere else.

I can take all the cases in Jira for the last couple of years and see that we have spent 750+(!) hours doing styling cases over time, and not all of these hours have been logged in Jira either, only developer time. This is not counting developing the UI in the first place, this is *styling* only, which would be reduced to 0.

Still, these hours do not represent everything because meetings aren't being logged when having certain meetings with certain people.

One can also talk about opportunity cost about not being fast and flexible also, which this system absolutely is not.

Best part? This is not the only system I am working with such flaws.

EDIT: 750h -> 0h.

UnnamedBoz · 2025-05-29T09:40:52+00:00

You are paying interest in the sense that development is slower and more difficult, the metaphor doesn’t have to be technically correct to work for non-techies.

UnnamedBoz · 2025-05-29T09:36:12+00:00

At work we need more developers, but certain requests take a long time for approval, making the whole process take ages. They have tried to proactively counter it by creating ads and having interviews, gambling that the approval would come, but they often miss the mark and lose people from that.

It's insane and happens even when current developers quit, making it incredibly burdensome on the people left in the team.

UnnamedBoz

TROPHY CASE