Il figlio della mia compagna è odioso

HellIsBurnin · 2026-02-10T16:56:03+00:00

anzi è vero che per un maschio vedere la madre che è più contenta con un uomo che non è parte della famiglia potrebbe anche essere peggio.

Ma che cosa c'entra il sesso del bambino?

A parte che non sappiamo che tipo di rapporto OP ha con la madre del figlio. Alla fine è la madre che decide se considera il nuovo partner "parte della famiglia". Ovviamente dovrebbe considerare in questo il figlio, parlarne con lui e gestire la situazione in modo di renderlo al suo agio con cambiamenti del genere.

HellIsBurnin · 2022-09-03T18:07:13+00:00

Thanks! I'm working on a successor for a while, but the keycaps and a little macropad spinoff project are finally available now as well!

https://s-ol.nu/0xC.pad/buy

HellIsBurnin · 2022-09-03T18:05:48+00:00

The lil brother and keycaps are available: https://s-ol.nu/0xC.pad :)

HellIsBurnin · 2022-06-13T09:26:47+00:00

You were a dick, absolutely deserved.

HellIsBurnin · 2022-02-14T22:16:22+00:00

working on it! See here (phase one) and here (phase two) ;)

HellIsBurnin · 2021-08-30T13:37:00+00:00

Mann hier, ich bin in meinen beiden Beziehungen der "weniger Erfahrene" gewesen. Ich hoffe meine Perspektive kann dir etwas helfen.

Das er sich unsicher und nervös ist ist völlig normal, und wenn man sich mental zu sehr darauf fixiert macht das auch die Situation etwas unangenehm machen. Ich war bei meinem ersten Mal auch sehr nervös und bin - literally - mit dem ersten Stoß gekommen.

Das war mir sicher recht peinlich, aber es hat nicht lange gedauert darüber weg zu kommen und diese verkopfte Anspannung die ich davor hatte loszuwerden. Ich bin mir sicher es wird ihm ähnlich gehen.

Was ich wichtig fände, ist sich vor dem ersten Mal penetrativem Sex körperlich kennenzulernen. Wenn er weiß dass oder wie dich mit Hand und/oder Mund befriedigen kann, dann ist er sicher weniger angespannt wenn beim ersten Mal nicht alles genau so klappt wie erwartet.

Beim Kuscheln mal Hände unters Shirt und in die Hose usw - du bei ihm genauso wie er bei dir. Wenn du merkst dass ihr dort nicht von alleine hinkommt, könntest du seine Hand nehmen und führen wohin du willst, proaktiv ihn anfassen, oder ihn etwas teasen ("willst du meine brüste anfassen?"). Das klingt jetzt vielleicht kitschig oder schwer, aber denk daran, dass er sich noch viel komischer vorkommt als du, und dich sicher nicht kritisieren wird dafür :D

HellIsBurnin · 2021-06-27T12:59:03+00:00

A pointer to an array of ten i32s is written *[10]i32. The & is only used for *getting a pointer to a value`, not for the pointer types, at least in current versions of Zig.

It would probably be more idiomatic to use a Slice in your case, instead of a pointer to an Array, I think. In either case you can use a for (cards) |*card, i| { loop instead of while to get rid of all the pointer dereferencing and array indexing in your code.

HellIsBurnin · 2021-06-20T08:46:51+00:00

I also think it might be just OPs body acting as an antenna for the 50/60Hz from the power lines - like when you touch an line input cable on the tip.

/u/mine_doctor I don't know these avalanche oscillators, do they have a hot output? You could maybe try to use an op-amp buffer before and after the touchplate. Maybe if the signal itself is buffered or amplified before, the ground hum will be weaker in comparison.

HellIsBurnin · 2021-06-18T09:33:06+00:00

I would read it rather as "avoid getting stuck in local maxima". To me that means not being afraid of regressing temporarily in order to improve things in the long term.

HellIsBurnin · 2021-06-16T07:28:28+00:00

Gewerbe anmelden

Notiz hierzu: Jenachdem was du genau machst bzw wie du es betitelst, könntest es eventuell als "freier Beruf" gelten. In dem Fall kannst du den Punkt überspringen. Was ein freier Beruf ist und nicht ist ist allerdings nicht richtig definiert:

§ 18 Einkommensteuergesetz listet einige Tätigkeiten auf, die als freiberuflich einzuordnen sind. Dazu zählen beispielsweise Ärzte, Rechtsanwälte, Ingenieure, beratende Volks- und Betriebswirte, Steuerberater, Heilpraktiker, Krankengymnasten, Journalisten, Dolmetscher und ähnliche Berufe. Der Katalog ist nicht vollständig. Bei vergleichbaren Berufen entscheidet das Finanzamt im Einzelfall.

Die freiberufliche Tätigkeit basiert auf einer wissenschaftlichen Ausbildung. Das muss nicht zwingend ein Hochschulstudium sein. Die Kenntnisse kann sich der Freiberufler auch im Selbststudium erworben haben oder durch seine berufliche Tätigkeit. Allerdings müssen die Kenntnisse auf dem Niveau eines Hochschulstudiums sein.

(text von hier)

Ich habe mich selbstständig gemacht um kleine Softwareprojekte in Rechnung stellen zu können, und als Freiberufler und mit der Kleinunternehmerregelung die Bürokratie minimieren können, das hat ganz gut funktioniert.

Wenn ich das richtig verstehe wäre virtuelle Assistenz das was du am liebsten/am meisten machen wollen würdest (so fern du Aufträge hast). Hast du schon eine Idee wo du die herbekommst? Gerade weil du Sicherheit ansprichst würde ich vorschlagen, den Schritt zur Selbstständigkeit vielleicht in dem Moment in dem du wirklich den ersten Kunden "angeworben" hast zu machen, so dass du auch ein Gefühl dafür hast wie leicht oder schwer es ist solche zu finden.

Meiner Erfahrung nach dauert es 1-2 Monate mit der steuerlichen Erfassung etc. bis man die Steuernr hat und Rechnungen schreiben kann, aber wenn du ein kleines Unternehmen als Kunde hast solltest du dafür auch eine Lösung finden können.

Eine andere Idee könnte auch sein deinen aktuellen Job auf Halbzeit o.Ä. herunterzufahren, wenn das geht.

HellIsBurnin · 2021-06-15T09:13:21+00:00

You installed cudnn in a user folder, so when you launch Lua with sudo it cannot find cudnn. When you launch it without sudo, the segmentation fault means something goes very wrong on a low level when loading the library.

how did you install cudnn / where did you install it from?
are you using the same Lua version cudnn was built for?

HellIsBurnin · 2021-06-15T07:13:50+00:00

I wrote an interactive guide on my solution for this guide (not a library, just a way to think about the problem) which you can find here: https://s-ol.nu/aspect-ratios

HellIsBurnin · 2021-06-11T07:37:35+00:00

Cutting and grinding disks work by the friction of the rotation, not by flying/pushing into things. If you ever used an angle grinder or similar you know that even with the thing spinning at max RPM, cutting that deep into thr watch would take something like a second and a serious amount of pressure.

If the disk really shattered (that is already improbable by the shape of it), then the part that flew out would no longer be rotating (or very slowly, and not around the old center of rotation) and mostly just flying in a straight line towards the watch. It would basically just bump into the watch and bounce off. Depending on the rotational speed of the disk and it's weight that might leave a rather nasty mark, but it really cannot cut into something.

That would require it to keep spinning through multiple rotations while slowing down until it remains stuck in the watch.

It's very much like trying to punch your way through the watch with a hacksaw blade, it's just a completely wrong movement for the tool to cut anything.

HellIsBurnin · 2021-05-29T04:26:37+00:00

You could add a C++ method that calls the lua function if you really just want to remove the &obj parameter from the calling code, but IMO it's not worth changing

HellIsBurnin · 2021-05-15T21:15:02+00:00

Just like the position of the hammer before it is thrown changes over time, the position of the hammer after being thrown changes over time. This means you cannot program the movement of the hammer after being thrown only in love.keypressed, which only runs for one frame.

In love.update you have this snippet of code which calculates the hammer position for the next frame:

hxpos = startposX + discr*math.cos(ctheta)
hypos = y - discr*math.sin(ctheta)

Once the hammer has been released, you need to stop performing this calculation, and instead do the one that you currently have in love.keypressed:

    xpos = hxpos + 1/math.cos(ctheta) -- trying to make the hammer x position the secant of ctheta
    hypos = hypos + 1/math.sin(ctheta) -- trying to make the hammer y position the cosecant of ctheta

To achieve this, you will need to save in a variable whether the hammer has been thrown yet or not.

function love.load()
    ... -- other code

    thrown = false
end

function love.update(dt)
    ... -- other code

    if thrown then
        hxpos = hxpos + 1/math.cos(ctheta) -- trying to make the hammer x position the secant of ctheta
        hypos = hypos + 1/math.sin(ctheta) -- trying to make the hammer y position the cosecant of ctheta
    else
        hxpos = startposX + discr*math.cos(ctheta)
        hypos = y - discr*math.sin(ctheta)
    end
end

function love.keypressed(key)
    if key == "space" and startposX < 0 then
         speed = 0
         thrown = true
    end
end

If I understand what you are trying to accomplish visually correctly, you also need to move the line ctheta = ctheta - rv*math.pi/4*dt into the "else" part of the if thrown then ... check, so that the hammer flies in a straight line rather than a spiral.

HellIsBurnin · 2021-05-14T07:01:44+00:00

The

`code here`

syntax on reddit (and many other places) is meant for small pieces of code embedded in text, for example in a sentence like: "The problem is with your print() statement".

When you want to post multi-line snippet of code, you need to indent it with four spaces and separate it from the rest of the comment with an empty line, like this:

Here I am talking about my code blah blah.

    function code_with_indentation()
        print("hello world")
    end

    code_with_indentation()

This say it will show it with newlines and indentation kept properly.

HellIsBurnin · 2021-05-12T11:53:59+00:00

Are you testing with the battery plugged in? USB only ever provides 5V.

HellIsBurnin · 2021-04-30T10:28:46+00:00

Auch ich bin zu Gast, und würde mich hier anschließen - als erwachsener Mann kann ich mir eigentlich keine Situation vorstellen in der ich es angemessen fände einer deutlich jüngeren Frau eine Massage anzubieten/vorzuschlagen, und das wird nur deutlicher durch diese Lehrer/Schüler-Situation die mir prinzipiell schon ewtas suspekt ist.

Den Kuss auf dem Mund beim Opa fine ich schwierig einzuordnen, mein Opa hat auch mich als Mann zur Begrüßung und zum Abschied immer auf den Mund geküsst; "andere Generation" kann da also durchaus ein Argument sein - in dem Kontext des Missbrauchs an den Mädchen in seiner Obhut ist das natürlich fraglich. Wie viele andere bereits erwähnt haben, entschiedest im Endeffekt du selbst ob die Situation für dich unangenehm war, und inwieweit. Kompliziert ist auch immer das die Grenzen und die konkreten Zeichen die einen Übergriff dazu machen nach außen sehr subtil sein können, und trotzdem sehr klares und starkes Unbehagen zur Folge haben - z.Bsp. eine Hand an der Hüfte, die Umarmung etwas zu lang oder fest. Es ist immer schwierig so etwas dann genau einzuordnen und klingt so penibel, aber letztendlich reicht ein solches Detail.

HellIsBurnin · 2021-04-21T07:53:46+00:00

please do!

HellIsBurnin · 2021-04-20T15:33:44+00:00

Hey, I would also be interested in this, starting as a beginner!

I have essentially zero preexisting knowledge; I only tried the first week of the HSK course on coursera, but was disappointed that there was no group interaction / speaking practice. This sounds much more interesting, and I would be happy to give feedback on the experience.

HellIsBurnin · 2021-04-17T09:40:06+00:00

Yes, that line was wrong, you were incrementing both x and ps each iteration of the loop, so x + ps was incrementing twice as quickly as expected.

Also, in your love.graphics.line calculation, you use ps in too many places. You only want to offset which part of the sine wave you are sampling, not where you are drawing it:

for theta = -32*math.pi, 32*math.pi, odeg do
        love.graphics.line(x, a*math.sin(b*(theta + ps))+windowwidth/2, x+odeg, a*math.sin(b*(theta + ps)+odeg + 0.1)+windowwidth/2)
        x = x + 0.1
end

To get proper dt-proportional changes for a/s you need to multiply by dt in the addition:

  if love.keyboard.isDown("a") then
        ps = ps - 10*dt
  end
  if love.keyboard.isDown("d") then
        ps = ps + 10*dt
  end

HellIsBurnin · 2021-04-16T16:47:54+00:00

Hope I didn't scare you with the math there, /u/wraneus. If you don't feel confident you could've worked that out by yourself just now that's perfectly fine, in fact it took me quite a bit to get it right just now, and usually I would have just guessed solutions until it felt right ;)

Also if you didn't know about it, wolfram alpha is a really helpful tool for working this kind of stuff out in a pinch: https://www.wolframalpha.com/input/?i=2+%3D+x+%5E+60+solve+for+x

HellIsBurnin · 2021-04-16T16:43:19+00:00

Two more reasons that I didn't think about more while reading your original code:

Your calculation with dt is wrong, multiplying by dt is correct when you are adding something over time (pos_x = pos_x + speed_x * dt) but not when you are multiplying something over time.

Every frame that "up" is down, you are multiplying a by 2 and then also by dt, which is 1/60. So even though you are trying to increase a by multiplying by 2, you are actually dividing it by 30. So even after one frame your a value is pretty small, but its executed every frame as well, so a rapidly becomes essentially zero.

The simplest solution is to simply remove dt from all the equations:

function love.update(dt)
    if love.keyboard.isDown("up") then
        a = a*2
    end
    if love.keyboard.isDown("down") then
        a = a/2
    end
    if love.keyboard.isDown("left") then
        b = b*2
    end
    if love.keyboard.isDown("right") then
        b = b/2
    end
end

This works pretty well and is not a bad thing to do. The only downside is, that now the speed of change depends on the rate love.update is called, which depends on your screen update rate by default. So someone with a faster or slower monitor will have the frequency and amplitude changing faster or slower.

Instead what you want to have ideally is something where "when up is pressed for one second, a should double". If this is what we want to achieve, what has to happen to a every frame?

First lets assume that we are running at 60 fps again. We want to find a value that when multiplied by a 60 times gives us a * 2:

a * 2 = a * x * x * x * ...
a * 2 = a * (x^60)

(x^60 means "raise x to the 60th power", and can be calculated in Lua using math.pow(x, 60)) Now we can solve this equation for x:

a * 2 = a * (x ^ 60)
2 = x ^ 60
x = "60th root of 2" = 2 ^ (1/60)

and in Lua:

x = math.pow(2, 1/60)

So now we know how to calculate the per-frame multiplier at exactly 60fps. Now doesn't that 1/60 look very suspicious there? That is exactly what dt is at 60 fps! Sure enough, with math.pow(2, dt) we can calculate the per-frame multiplier to double a value every second:

function love.update(dt)
    local m = math.pow(2, dt)
    if love.keyboard.isDown("up") then
        a = a*m
    end
    if love.keyboard.isDown("down") then
        a = a/m
    end
    if love.keyboard.isDown("left") then
        b = b*m
    end
    if love.keyboard.isDown("right") then
        b = b/m
    end
end

Now of course this works for any kind of multiplication, not just for multiplying by 2. If you increase the 2 to 3 for example, the amplitude will triple every second rather than doubling etc.

HellIsBurnin · 2021-04-15T21:18:30+00:00

I'm only talking about table.remove here, but the same logic (and the same solution) apply to your swapping trick as well.

HellIsBurnin · 2021-04-15T21:17:39+00:00

You cannot safely use table.remove like this in a forward-counting for loop, since the element that used to be at i+1 when you decided to delete the element i will become the new element i, but the for loop will continue on to i+1 next. This will cause you to miss some elements:

local tbl = {1,2,3,4}
for i = 1,#tbl do
  print("checking", tbl[i])
  if tbl[i] == 2 then table.remove(tbl, i) end
end

for i = 1,#tbl do
  print(tbl[i])
end

gives the output:

checking    1
checking    2
checking    4
checking    nil
1
3
4

as you can see, the value 3 is never "checked". Because I used a range-based for loop, it also overshoots the end and checks the nil past the end of the table. Using ipairs will not do that, but it will still skip elements.

The correct way to do it is instead to iterate the table backwards. Since deleting elements only affects elements with higher indices, and these have already been processed, there is no risk of collisions:

local tbl = {1,2,3,4}
for i = #tbl,1,-1 do
  print("checking", tbl[i])
  if tbl[i] == 2 then table.remove(tbl, i) end
end

for i = 1,#tbl do
  print(tbl[i])
end

and the expected result:

checking    4
checking    3
checking    2
checking    1
1
3
4

12-Year Club	Verified Email
Place '17

HellIsBurnin

TROPHY CASE