LaPingvino | 11 months ago | on: Show HN: I made a tool to port tweets to Bluesky mantaining their original date
LaPingvino's comments
LaPingvino | 3 years ago | on: Sapling: A new source control system with Git-compatible client
I have used (actually introduced) Mercurial before at a company and considered them basically equivalent enough, only to get stuck in some horrible design choices of early Mercurial (named branches and not having rebase by default). I am happy to see these elements corrected in Sapling, giving me enough confidence that I might actually use Sapling over time...
LaPingvino | 3 years ago | on: Sapling: A new source control system with Git-compatible client
LaPingvino | 4 years ago | on: How generics are implemented in Go 1.18
LaPingvino | 4 years ago | on: How generics are implemented in Go 1.18
About the second part, you seem to mix up goroutines and channels. In a concurrent system, you would need locks for your example, and channels fix this. Goroutines are just the representation of independent processes and can be implemented and ARE implemented differently per compiler, check e.g. how tinygo and gopherjs do this.
Your example point 2 doesn't make any sense, check fan in and fan out patterns with channels. Go supports message passing, that is what channels are. You really didn't try Go and it shows.
LaPingvino | 4 years ago | on: How generics are implemented in Go 1.18
LaPingvino | 4 years ago | on: How generics are implemented in Go 1.18
Go is a language made for the human factor.
Go generate by the way is mostly NOT used for generics. Check for example Vugu, which compiles UI documents to pure Go code. Go generate is made to incorporate any random external tool without making it complicated for the humans using it. And it makes sense because the goal was not single pass compilation, it was single pass parsing, which is exactly WHY Go generate is useful. It is still true to the exact way this has been defined. Go is simple in ways that matter.
LaPingvino | 6 years ago | on: The dystopian world of software engineering interviews
For anyone doing programming tests, I would like to give some advice, too, based on the tests I did and got through successfully:
- Always give it a try - Always explain what you do and what you are trying to do - Don't worry about sending in an incomplete test when you don't manage to do it - Be verbose about what you are trying to do to solve it - Don't be afraid to ask questions
My first great programming job was at a place where I got a hard mathematical problem to solve, and I didn't manage to solve it at the moment, so I asked if I could take it home. I didn't manage to solve it at home but sent in the broken code that I had either way.
I got the job.
Why? Because the broken code I sent in showed that I understood recursion (it was for a Common Lisp job, that code was in Clojure) and the other people, even if they did manage to solve it, used more common languages and iterative solutions. He wanted someone who got the spirit of what they were working with, so that got me in. I asked my boss later how to solve that question, and he didn't manage either.
When I did the interviewing myself, the situation was similar. One candidate sent in a huge resume that looked impressive, but didn't send in the test. Immediate fail. Two others had a hard time with the test, but they showed that they cared about making it work, and that was enough for us to accept them: the core thing we wanted to see was that they could learn and cared enough to learn about what they needed.
One of those became main programmer and leader of many others later on, and made the company hugely successful.
LaPingvino | 7 years ago | on: Ask HN: Got a CS degree, but I’m unable to be programmer. What can I do?
LaPingvino | 10 years ago | on: Are Swiss banks buying Bitcoins?
LaPingvino | 10 years ago | on: Rob Pike: Simplicity Is Complicated [video]
LaPingvino | 11 years ago | on: Debian package management, the Arch way
I wrote it because I love Arch package management, but I don't like the fragility of it, found that out the hard way... I try to bring most of the bliss over via this tool.
LaPingvino | 12 years ago | on: Can 10,000 hours of practice make you an expert?
LaPingvino | 12 years ago | on: Microsoft announces Windows 8.1
Try this in Windows 8...
LaPingvino | 14 years ago | on: 1995 DOS game opensourced, needs hacker love
I will include the data-files in the repository. This is the very first release, and it's far from perfect as it is of course.
LaPingvino | 14 years ago | on: 1995 DOS game opensourced, needs hacker love
The .exe and the data files: http://plasmaworks.com/files/pits/pits95.zip
The level editor (Source Code got lost, but Apache-license is also valid for this one. If someone can disassemble it and create some maintainable sourcecode from it, very welcome) http://plasmaworks.com/files/pits/pitsedit.zip
Screenshot for reference (more googling for puzzle pits): http://www.google.com/imgres?imgurl=http://www.old-games.com...
LaPingvino | 14 years ago | on: 1995 DOS game opensourced, needs hacker love
LaPingvino | 15 years ago | on: Steve Jobs: The Next Insanely Great Thing
LaPingvino | 15 years ago | on: Amazon selling remaining Kindle 2 stock for $89 on Black Friday
LaPingvino | 15 years ago | on: Why exams mean nothing out of context