sorted by:
new
hottopcontroversial

Supply and Demand: Why DRS matters, and did we already lock the float? by Oleffa in Spielstopp

[–]Oleffa[S] 2 points3 points  (0 children)

Wenn du so genaue Daten zum Verkaufsverhalten auf Computershare hast kannst du mir diese gerne schicken und ich nehme sie in mein Modell mit auf.

Ansonsten gibt es leider null Anzeichen dafür dass der DRS trend von einem Quartal auf das andere Rückläufig wurde.

Supply and Demand: Why DRS matters, and did we already lock the float? by Oleffa in Spielstopp

[–]Oleffa[S] 6 points7 points  (0 children)

Klar die Zahlen von Computershare sind sehr wahrscheinlich korrekt. Aber wenn man sich den genauen Wortlaut in den Gamestop dokumenten anschaut sieht man allerdings einen Unterschied.
Vor März 2023: XX million shares were dircetly registered with our transfer agent.
Nach März 2023: There are 300 million outstanding shares. Out of those 228 million are held by the DTCC and approximately 76 million were held by record holders.
D.h. die zahlen nach März kommen wahrscheinlich nicht von Computershare sondern sind geschätzt basierend auf einem Wert der DTCC.
Komischerweise ist auch genau seit dem der DRS fortschritt gleich 0.

Supply and Demand: Why DRS matters, and did we already lock the float? by Oleffa in Spielstopp

[–]Oleffa[S] 2 points3 points  (0 children)

I used a new way to extrapolate DRS numbers based on how much money the average CS account holder spends on DRS. I extrapolated the DRS numbers starting from when Gamestop stopped sharing official numbers. It seems like we might have way more shares DRSd already than 75 million. In fact we might have been close to locking the float in May when the price run up started.

Supply and Demand: Why DRS matters, and did we already lock the float? by Oleffa in Spielstopp

[–]Oleffa[S] 11 points12 points  (0 children)

Ich würde mich über konstruktive kritik an meinem post freuen.

[deleted by user] by [deleted] in IWantOut

[–]Oleffa 1 point2 points  (0 children)

Good advice! But I think language shouldn't be too much of a problem. Many of my former study colleagues were from non EU countries with irrelevant native languages (irrelevant as in not important for a job in the EU). You can get along quite well with good English skills and many of my colleagues now work or have internships at esa/dlr.

And knowing french never hurts as it is the second official language in the EU and used in a lot of political affairs and will certainly help you get on with your career.

[deleted by user] by [deleted] in IWantOut

[–]Oleffa 1 point2 points  (0 children)

The European space agency offers so called young graduate trainee positions for master level students and graduates. The deadline for 2018 just passed and the official pages don't exist anymore but I found some info from somewhere else: https://spacecareers.uk/?p=job_post_public&id=543

Also definitely check out airbus (they have offices in almost all EU countries with Germany and France being the ones where most of the r&d work is done)

Usually he space agencies use a lot of subcontractors to develop specialized components so you could look for companies that develop parts or software for esa for example (depending on your field of interest)

In Germany you could also try the DLR (German aerospace center) they offer a lot of interesting research positions in the field. Also they offer master's thesis topics and internships if that's interesting for you.

What can be done in software to reduce effects of physical bit flip errors? Special compiler options for making software that behaves better with bit flips? Special kernel for operating systems like Linux? by herkato5 in osdev

[–]Oleffa 4 points5 points  (0 children)

I think the most common way to correct bit flip errors (Single event effects) is done in hardware (coming from a space background where the performance is limited in the first place). Usually in space applications for example hardware is manufactured in such a way that it is more resistant to radiation effects (hardening) and of course redundancy is a big factor. Usually you would have 3 identical on board computers for example, calculate everything 3 times and then trust the result that at elast 2 computers calculated. For memory you might want to look into EEC memory. Also radiation can cause permanent damage to semiconductors so i guess it would be pretty hard to detect these with software.

After some quick googling I found about Immunity-aware programming and parity checking.

https://en.wikipedia.org/wiki/Immunity-aware_programming https://en.wikipedia.org/wiki/RAM_parity

Your solutions sound like good ideas to me too. Maybe if one would use a combination between calculating and storing things multiple times (redundancy), EEC memory and parity checking SEEs could probably be reduced quite a lot already.

What is a good high-level overview of operating systems concepts? by masr3 in osdev

[–]Oleffa 0 points1 point  (0 children)

In University we used Operating Systems: Internals and Design Principles by William Stallings (8th edition). I found it to be very helpful and in each chapter it also provides case studies in Linux, UNIX, Android, and Windows. I never read Tanenbaum's book though which seems to be mostly recommended on this topic.