Hacker Newsnew | past | comments | ask | show | jobs | submit | kwakubiney's commentslogin

Feigning confidence might even be the hardest part of this all.

I resonate highly with this. Especially when brainstorming ideas with my manager. He's very quick with suggestions, and I am always saying ehhh I don't know let me think about it. I have realized that him giving me ideas quickly to iterate on is beneficial because I am always able to refine it. I still do think it is a deficiency in some sense as I would have loved to be one of those guys who could just grok stuff instantly and contribute quicker

Let me give you guys a perspective from someone who did Electrical Engineering in Africa. There are hardly any job openings centered around electronics so the programme/curriculum is Power Engineering heavy. Most of the professors did research around this area, and there were very few who did anything in the sciences. I had the chance to pick some electives from the Computer Engineering department, but this was just during my third and final year of university. Unlike OP, I did not have an issue breezing through circuit problem sets, though they felt very repetitive, I was not bad at it, nor did I fail any classes.

I had an eye opening experience when I had my first taste of programming when I took C programming in my second year of university. What do you mean I can run a command and see instant output? Amazing! This was not the case for my electronics and power engineering lab sessions. We were using equipment that had been around since the 80s with little to no supervision. Just a bunch of routine "experiments" which I can barely remember any of. In my third year, I took Digital Computer Design (a C.E elective) and I realized I had been wasting my time learning about how the power grid in my country works. I tried my best to salvage as much as I could by picking more C.E electives, albeit not many available, did as best I could.

Everyday I wonder, how different would my life have been if I studied CS or even CE, I do not know. But, I appreciate the little this journey taught me, that you can always squeeze lemonade out of whatever lemons life gives you. I see my old EE notes now and they don't make sense to me, but I appreciate the happy chills solving circuit problem sets gave me. I work in software now, and I get that 1000x more, and that is how I know I made the right choice.


Haven’t felt it in so long, but it’s what keeps the bills paid


I don't think we will get to a point where we can safely mitigate the risks associated with this. It is almost futile to pull this off at scale, and the so called "benefits" are not worth the tradeoff.


I don’t know how I feel about the assumption that model training isn’t an engineering problem


Nice project. Filtering took forever though.


Have made improvements to the filters! Hope you get a better experience now


Is there a way I can use this to run remote commands on another host? Something similar to what ssh does?


You could pipe to bash?


Ah right, but this does not support bidirectional streaming so I won't be able to get the remote stdout on the client, I guess.


Couldn’t you just pipe the stdout to another dumbpipe


Not a very friendly API


This works:

Remote:

  $ socat TCP-LISTEN:4321,reuseaddr,fork EXEC:"bash -li",pty,stderr,setsid,sigint,rawer&
  $ dumbpipe listen-tcp --host 127.0.0.1:4321
  using secret key fe82...7efd
  Forwarding incoming requests to '127.0.0.1:4321'.
  To connect, use e.g.:
  dumbpipe connect-tcp nodeabj...wkqay

Local:

  $ dumbpipe connect-tcp --addr 127.0.0.1:4321 nodeabj...wkqay&
  using secret key fe82...7efd
  $ nc 127.0.0.1 4321
  root@localhost:~#


Thanks


I use it to practice Leetcode problems


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: