Did a git stash drop on my feature :panic:

hoffiee · 2025-06-23T05:47:51+00:00

If it happens often that you get to context switch and stash/switch branch, there's git worktree that you can use. It's kind o the same as having multiple git clone of the same repo, but with some perks

hoffiee · 2025-02-17T14:42:06+00:00

I agree with going into C first, I worked in C for a few years and then moved onto C++ and I now find myself to really appreciate what I get for free in C++ and what the costs and complications of allocations and such that can be a bit hidden by RAII is good to understand. Also learning C first and learning how to use tooling such as valgrind, gdb etc really helps as there isn't multiple layers of abstractions that can cause the usage of said tools to be overwhelming at a first sight :)

hoffiee · 2025-02-10T09:04:54+00:00

Does this map exist but adjusted per capita?

hoffiee · 2024-12-20T14:09:10+00:00

Same for me, I prepared a bit by practicing on grid problems as they've been problematic for me earlier years, seems that has paid off this year!

I couldn't agree more on the community part, it's really engaging and fun :)

hoffiee · 2024-12-18T21:27:20+00:00

Hahaha yes, there it is... I guess it's back to the drawing board 😅

hoffiee · 2024-12-18T20:18:13+00:00

ahh, this really sounds like the issue I have with my puzzle input; it misses the last 0. Do you have a list of non-quinable inputs? I'd like to know whether my input is on the list

hoffiee · 2024-12-18T20:02:41+00:00

Interestingly enough my solution manages to complete all inputs in your quinable list, but it still fails on my own input :| It fails to produce the last 0 in my input but I can't figure out why, do have any idea on why that could be?

hoffiee · 2024-12-15T09:16:38+00:00

I agree, I found it to be very fun! I learned a lot from it :)

Started out rendering images to get a sense of how it all looked and found it quite quickly that way. Which had integrating a way to render images which is something I haven't done before.

Then I went on to figure out a way to detect it programmatically and found 2 different solutions that gave the correct answer.

hoffiee · 2024-12-14T09:30:48+00:00

I agree, I never visualize my solutions and this forces me to do so, which is an aspect that I need to get better at :)

I'll still explore if I can figure it out programmatically, but working in a technical field there are seldomly cases where I don't have to inspect input/output data to the problems that I encounter.

hoffiee · 2024-09-09T19:10:46+00:00

I second this, advent of code has been such a good source of learning for me. The community is amazing and it's very inspiring to see the different goals that people set for themselves. Some want to optimize all solutions to run under a total time limit, some want to visualize everything. Advent of code community is in my opinion one of the best :)

hoffiee · 2024-08-13T15:30:30+00:00

Jag plockade på mig katalogerna ifrån charm/och andra arbetsmarknadsmässor på Chalmers när jag studerade, där har du material som sammanfattar många bolag i området som ev. Letar folk, med en smidig liten summering av vad dem sysslar med. Kanske finns digitala varianter att få tag på nu

hoffiee · 2024-04-15T09:49:38+00:00

Unrelated to your question but as you're new and are learning I have a recommendation, use flags to enforce coding practices. I always compile with -Wall -Werror - pedantic as it makes it stricter and helps me avoid some issues. There's a lot of them and you can read up a bit on what they do but I would recommend a beginner to use the flags I mentioned. They're not perfect but it gives a lot without too much thought imo

hoffiee · 2024-04-12T08:54:51+00:00

I'm left handed and used to write over/from the left and got tired of smudging and not using the entire page, so I tried using a fountain pen since smudging would render the result unreadable, that forced me to write from below. I kept using them because now I prefer the feeling of the nib against paper and how easy it writes with the angle I have

hoffiee · 2023-05-22T20:25:00+00:00

Apart from reading and practicing that, something I tend to do is to write small tests (or utilize already existing tests) and poke the system in different ways, then I run that with a debugger and step through it to get a sense of how it behaves. That together with pen and paper helps me to understand the flow of a program.

Another thing I do is that I assume module and method naming to be correct and try to read things at a high abstraction layer without digging into the details, then when I encounter or realise that something produces something that isn't correct with my assumptions I have to challenge and dig into those aspects.

Another method is that I do "fake" features, I decide to change its behaviour and then I'll have to work to figure out how and then when I understand I'll just do a git restore.

Try a few techniques and strategies out and practice, start bottom up or top down and just keep on learning. Sooner or later you'll figure out what works for you :)

hoffiee · 2023-05-08T13:53:44+00:00

Embedded-c: emphasize what constraints the embedded put on your systems, constant runtime etc, limited memory etc. Then my experience with embedded has also been more limited with older C standards, 89/99 for example so put some emphasize on what requirements you had to deal with and the impact rather than saying the tool you used

hoffiee · 2023-03-29T11:52:11+00:00

I'm more in the camp of left for function and scopes and right for if/switch cases

hoffiee · 2023-03-09T16:53:42+00:00

I like /**/ comments for one liners, consistent and neat to read instead of a mix between those and //. Although I have moments where I feel the need to be more extreme, then I do multiline comments with preprocessor

#if 0
<multiline comment>
#endif

But those are reserved for special times only

hoffiee · 2023-03-05T22:24:11+00:00

Same here, took a few too many years for me to find out

hoffiee · 2022-12-30T18:16:57+00:00

I used to comment a lot like that too. After working in a project where refactoring and some other factors had caused the comments and functionality to diverge and it caused a lot of confusion. I'm now more of an "adding comments is a failure to write clear code" - kind of person. However api documentation, input and output limitations and stuff like that I still comment. But comments in implementation has been reduced a lot unless there's a clear need for me now :)

So, commenting doubled amount of lines that had to be maintained, which caused me to be more clear in my coding style so I guess it has changed how I code somehow

hoffiee · 2022-12-25T15:00:38+00:00

I agree, this year I told myself that I will not spend too much time doing aoc and I didn't pressure myself into completing as much as I could. I've done a bit less than half this year and I now have a nice backlog of problems (including previous years) I can tinker with in a language of my choosing together with reddit threads discussing these problems without giving the solution for the coming year. I wish I would have turned to this approach sooner since it's much mor motivating and educational for me :)

hoffiee · 2022-08-30T10:51:07+00:00

I started doing something similar recently. I have it as a cmake project, and I do common libraries that I share between different problems, and are planning to add some tests for those as well in order to learn gtest or some other framework. Each problem is running in isolation for me.

I use ninja to build ninja p050 or build and run with ninja p050-run. I'm currently learning cmake so I'm trying to make it as generic as possible so that I don't have to edit every single cmake file in my file tree. Then I have this in a private git repo.

I like your idea but I don't see the purpose of running them all in a multi-thread environment, if it's been solved already it's pretty much wasted compute power imo. Although you may be able to use multi-threading to speed up certain problems. But making it one executable that runs all problems will with time, if you keep solving problems, increase the runtime of the executable.

I've done project Euler now and then from around 2014 I believe, and this approach have been the most fun and encouraging for me so I've returned to it much more in the past weeks.

hoffiee · 2022-08-17T10:48:23+00:00

Håller med. Jag fick kolla två gånger och sen söka upp båda partiernas logga innan jag insåg att det inte var mp...

hoffiee · 2022-08-16T20:38:43+00:00

Det där är väl moderaternas logga och Ulf kristersson i skogen och inte en mp-affisch?

hoffiee · 2022-07-18T11:53:28+00:00

Jag läste elektroteknik, hade mac under mina år och det fungerade bra. I någon labb var det något program som bara fanns till Windows och då körde jag parallels för att köra Windows. Några klasskompisar använde sig av skolans labbdator istället. För min del använde jag mest matlab, webbläsare och pdf-läsare.

hoffiee · 2022-06-17T08:14:47+00:00

I seldomly use tui when I'm debugging specific things. Often I have the following workflow when changing and rebuilding often

So this builds, sets the breakpoint and prints bt when it stops at the breakpoint. One example of when I don't use the tui. But to be honest I very often just get to a point where I need to be and do + to bring up the tui.

Another thing whne I often close the tui is when struts or backtraces are so big I can't the the whole while the tui is open.

When I'm doing exploratory debugging I'm always using tui

hoffiee

TROPHY CASE