Spyke

Replies

Comment on

*Permanently Deleted*

Reply in thread

I bet you'd spend about 14 hours a week doing all that stuff, maybe as little as 7-10. Pessimistically then it's 56 hours of work a month and optimistically it's half that. So he'd be paying you from $31.25 to $62.50 an hour, which ranges from great to ridiculous in favor of you. Personally I wouldn't do it because of the weird dynamic of living with my boss, but there could be a great deal in there for you.

Comment on

University Students

Software devs in general seem to have a hard time with balance. No comments or too many comments. Not enough abstraction or too much, overly rigid or loose coding standards, overoptimizing or underoptimizing. To be fair it is difficult to get there.

Comment on

What is something that happened you initially thought was bad but ended up being grateful for and saw as very positive?

I got pulled over and the cop found a 1/2 gram of pot in my car (a very small amount), which ended up with me having to do community service and take regular drug tests. I was working as a line cook at the time, but being forced to stop smoking weed gave me the push to finally apply for an entry level manufacturing position at a local company who does drug tests. Years later I still work there, but as a software engineer, and attending online college. I wouldn't quite say I'm grateful about the ass backwards drug laws and invasive drug screening, but I really can't argue that my current situation is a lot better than it was back then. Without that event, I might still be working random entry level jobs.

c_lang

Comment on

C can be memory-safe (2023)

I don't speak C, but isn't this an extreme simplification of the issue? I thought memory could be abused in an almost infinite number of subtle ways outside of allocating it wrong. For example, improperly sanitized string inputs. I feel like if it were this easy, it would have been done decades ago.

Comment on

Live coding interviews measure stress, not coding skils

I can see how this could be unfair, but working as a dev sometimes does require you to be on top of things in a high stress atmosphere. For example, what if you're proposing an excellent technical solution in a meeting but some jaded older engineer is hard to convince? If you can't outline your thinking in that scenario, your solution could be discarded just because someone was louder than you. As someone who used to have performance anxiety, I believe it's generally something you can and should practice for. On the other hand, if there really isn't a need for this type of skill, it totally makes sense to avoid creating interview environments where you are filtering candidates based on it.

Comment on

What is something about how people view or use technology that needs to die?

I think we're coming to the end of a 50 year cycle of rapid technological improvement that's been a parasitic host for capitalistic predilections. Shareholders ride tech companies hard and put them away wet, fucking over workers and squeezing consumers in the process. Innovative and awesome companies end up getting subsumed into a shit whirlpool where the product gets worse, more expensive, and steals your data. So I guess the people in my example are the tech investors and MBAs feeding them, and their abuse of tech is what needs to die.