@js@x0r.be

Experienced with #openbsd, #freebsd and #linux. Love to program in #elixir, #rust and #c. Developed distributed systems and led a security department (red _and_ blue).

Disclaimer: EU/Ger based, remote preferred

#fedihire

x0r.be

6

0

25

0

Jan @js@x0r.be

· 5mo ago

Net negative commits (in lines if code) are pure enjoyment.

#programming

x0r.be

4

1

0

Jan @js@x0r.be

· 6mo ago

Replying to

@einbeispiel Du siehst da das Herstellerlogo und die Seriennummer wenn ich mich nicht komplett täusche. Juweliere koennen weiterhelfen. (Eheringe von z.B. Niessing enthalten Nummern dieser Art.)

2

0

Jan @js@x0r.be

· 5mo ago

It’s really impressive for how long leg muscles can stay sore.

1

0

Jan @js@x0r.be

· 6mo ago

Replying to

@lw Exactly, do not push to main from dev and merge the branches when they are ready to be released. When everything is upstream switch back to the main branch on dev and update.

create a new branch (the feature branch and do your work)
test
push the branch to your private repo
pull it wherever you want and merge it into the official repo (or pull directly from another source e.g. your private repo)
update your devs main branch and do the next thing

1

0

Jan @js@x0r.be

· 6mo ago

After reading a lot of C code again and sending out patches I'm happy to not have to worry about memory leaks while programming in #elixir right now.

x0r.be

1

0

Jan @js@x0r.be

· 6mo ago

Replying to

@lw I'm not sure how experienced you are with git. I recommend reading upon the differences between merging and rebasing, branches and possibly cherry-pick. I think you want to work with feature branches in this scenario and not on the main/master branch on your dev machines. I _hope_ I understood your scenario.

0

3

0

Jan @js@x0r.be

· 6mo ago

@floberrez@mastodon.social Is there a reason for you posting your last toot 21 times?

0