2nd game firmly in progress btw if anyone cares. Will be definitely interesting to see how this works out. I'm not a game designer by any means but I'm putting together some ideas from other games in the genre and will have direct access to the data to balance the game so should be able to make something somewhat decent.

Current game still getting ~10k hits to the site per day so if I get half of that and have some ads and a "give me $20 for premium flair + no ads" or something I should get some passive income.

I recently had a 2 factor nightmare in which I only had access to email on a new machine, which wanted to send a code to my phone - which was new, and in order to set that up, I needed to access my email.

Pretty much got completely locked out of everything for 4 hours. Was absolutely infuriating.

You inspect the element to get the option text in the drop down list?

I use 2FA for everything important. The problem is with iMessage there's a big hole.

I got a company interested in me from Angels List. Let's look at the job board:

Secret question with a pick list? That's a thing?

I would lol at a lot of those salaries in the Midwest. Seeing what it's going to cost in the LA/OC area, super duper lol.

The question not the answer.

Yeah I'm not sure I'd trust a company that lowballs their salary like that. Here's their product:

Software Developer Paid Internship - no salary / no equity

Free snacks?

WTF is with the random period placement? Did you add that to prevent googling?

Followed by:



REMOVE CARD NOW. YOU HAVE 5 SECONDS TO COMPLY.

Yeah no need to make enemies.

Anyone have any idea why only my iPhone X would have problems logging on to my mom's wifi? My computer works, ipads work. But the iphone goes back and forth between "Unable to Join Network" and "Incorrect Password" - even though the password is correct.

It was doing something similar on a lot of networks in Central America. It would log on, be happy with the password, work fine. But then you wander into another area and all of a sudden it says bad password. For the same network, same password.

I thought it was a Central America thing. But now I think it's an iPhone X thing - possibly with crappy older routers. Although my Mom's has a 5G option. So it can't be that old.

I believe commits should document granular changes. If your feature branch requires 4 changes, it should be spread out among 4 commits.

If you have organized commits, then you shouldn't have merge conflict nightmares (no worse than 1 squashed commit). For example, I see a lot of people do this:

commit 1: Add x
commit 2: blah
commit 3: Undo x or replace it with y

In reality, commit 1 should be amended with 3 or vice versa. Otherwise, yes, this can potentially generate 2 conflicts when rebased.

Yea squashing commits seems like a misuse of git to me, that confused me.

I find the game updates interesting, so please keep doing them!

is it better to undo commits and then combine them? thats pretty much the same thing.

or do you want a bunch of little commits like the following?

-fixed broken unit test
-fixed syntax. added line in proper place.
-removed f from unit test (always forget the damn f lol)
-fixed typo in header wording
-temp commit. saving work to switch branches and work on different card.

I'd kind of like to see one of them, I guess you don't link to them to keep anonymous?

I prefer little commits, but with more details (e.g. which unit test). I would combine the two unit test ones if they're referencing the same one. If the syntax is related to the same unit test, I would combine that one too.

And consider using stash as a temp commit. Otherwise, ammend the commit later.

https://www.theatlantic.com/educatio...n-debt/563093/

Just curious - if anyone ever use one of these coding schools that takes a % of your first year income. Seems better than going way into debt.

When I was just getting started I almost got sucked into a DeVry type thing with a really expensive client-server programming course that I might still be paying off - and not using given the internet killed client-server. Blech.

What are some opinions on tech meetups as far as job networking goes?

Squashing A ton of commits is aids

Maybe we're weird but I looked at pull request description, then a pull request diff if I really needed to know something.

I can't remember ever needing to dig through commit history except when doing a git bisect - which is rare.

Hence we always just merged, never rebase, to avoid gnarly conflicts.

Or I guess when I needed to roll back changes. But that was almost always just a local branch. If bad stuff got into master we'd just fix it manually and add a new commit.

I was going to ask that too. I almost always look at pull requests for the logical grouping of related work.

Do you guys get value out of all of the effort spent maintaining a super clean git commit history?

The idea that some people are using force pushes to master just seems kind of crazy to me.