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

My access points are inaccessible to the public. You would have to trespass deep into my property.


Discussion from 2 weeks ago: https://news.ycombinator.com/item?id=27659105


The iPhone 12 starts at $729. You get a $30 rebate if you sign up for a new phone plan.


YES! TDD has saved me from this, listen to our friend fung. I put off learning about it for so long out of laziness but the payoff is huge.


> I believe many devs are afraid someone could see all their trial and error attempts and judge them

This is certainly part of the reason I do it. Sometimes I'll start repos anew, without the "mistake" commits and branches, and add that version to my Github before I send the link to a potential employer.


https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History

https://git-scm.com/docs/git-merge

C-f squash

You can compress a series of commits into one with squash in git.


I write a lot of frontend JS with hot reloading

make change => see result => cmd-z 1 time to fix result OR commit and keep coding

oops, it wasn't really fixed. cmd-z 3 times and see if that works

I know it's wrong, but what's right?


> I know it's wrong, but what's right?

Nah, it's not wrong. You're testing your code changes live.


no it's webpack HMR

(I know you're joking)


Hmm... I actually wasn't. By "live" I mean in the developer's own browser.


Ohhh, I thought it was a riff on "I don't always test my code, but when I do, I do it in production."


What's the alternative? What should I be doing instead of cmd-z?

> I'll Ctrl-A and Ctrl-V this into a new tab before it gets too messy

I did this about 400 times today


You should at least pay your intern a livable wage, $15/hr


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

Search: