Readit News logoReadit News
TheLonelyGecko commented on Show HN: Open-source resume builder and parser   open-resume.com/... · Posted by u/xitang
pratio · 3 years ago
Also checkout https://jsonresume.org/ not my project but also amazing work
TheLonelyGecko · 3 years ago
No marketing on the website <3
TheLonelyGecko commented on Changes at YC   ycombinator.com/blog/chan... · Posted by u/todsacerdoti
spir · 3 years ago
Finally some sense-talking. The growing culture of paternalism in the employer-employee relationship is toxic to the foundations of our societal wealth.

Personal responsibility and equal opportunity are how we got to iPhones, toothpaste in every corner store, and a store on every corner.

TheLonelyGecko · 3 years ago
> The growing culture of paternalism in the employer-employee relationship is toxic to the foundations of our societal wealth.

???

TheLonelyGecko commented on Purego – A library for calling C functions from Go without Cgo   github.com/ebitengine/pur... · Posted by u/weitzj
emidoots · 3 years ago
Very cool! I will definitely give this a try, I've been looking to build Go bindings to Mach[0] soon.

It looks like this would make cross-compiling CGO easier (no target C toolchain needed?)

Does this do anything to reduce the overhead of CGO calls / the stack size problem? IIRC the reason CGO overhead exists is at least partly because goroutines only have an ~8k stack to start with, and the C code doesn't know how to expand it-so CGO calls "must" first have the goroutine switched to an OS thread which has an ~8MB stack.

One reason I think Go <-> Zig could be a fantastic pairing is that Zig plans to add a builtin which tells you the maximum stack size of a given function[1], so you could grow the goroutine stack to that size and then call Zig (or, since Zig an compile C code, you could also call C with a tiny shim to report the stack required?) and then eliminate the goroutine -> OS thread switching overhead.

[0] https://github.com/hexops/mach

[1] https://github.com/ziglang/zig/issues/157

TheLonelyGecko · 3 years ago
Nice, just-in-time goroutine -> OS thread switching.
TheLonelyGecko commented on Why big tech companies need so many people   thebuilderjr.substack.com... · Posted by u/flurly
BurningFrog · 3 years ago
I miss the "because they can" explanation.

If billions are raining from the sky, you can hire armies of people. Every manager wants to expand their "empire", and there is money to hire people, so in the end a lot of people get hired.

TheLonelyGecko · 3 years ago
Then a lot of people get fired. Then a lot of people get hired.
TheLonelyGecko commented on Why big tech companies need so many people   thebuilderjr.substack.com... · Posted by u/flurly
moron4hire · 3 years ago
That doesn't explain the useless engineering theater that these companies engage in, like code review and "readability", that drastically reduce IC velocity. If FAANG supposedly "only" hires the "best and brightest", then why are they so untrusting of their contributions?

I mean, I've never worked in a team that large. A big part of that is because I can't imagine asking someone else's permission to write code. If a company can get so big that they can't trust their developers to release code, maybe that company is just too big?

Companies like Google are a joke. All the Cap'n Crunch you can eat, but do your job and write some code and get it into production? Can't have that!

EDIT: the largest company I ever worked at only had about 300,000 employees.

TheLonelyGecko · 3 years ago
You should try code review, it’s a great tool.

u/TheLonelyGecko

KarmaCake day11June 5, 2019View Original