I found my initial transition a bit difficult. I gave up my managerial duties and ended up being treated as more of a contractor than a full-time employee. Things like being left off of company-wide emails and a few other things like that.

I wouldn't have kept working remote for my first company for very long and was already thinking about finding a local job. Luckily I was offered a great opportunity that kept me remote and so that's what I've kept doing.

And in all honesty I'll be working remotely for at least another 3-5 years because a local job wouldn't even come close to paying what I make working remotely for an NYC company.

[SPOILER]
ONE. I find it much more readable and easy to tell what's happening at each step
[/SPOILER]

Just easier to cut and paste his code than redo the same work...

Lol tapatalk. spoil tag doesn't actually create spoiler but spoiler does. Now viewing on the web it's the exact opposite.

The 2+2 app is the same way FWIW.

I just assumed it was an intentional joke

Also, not smart enough to figure out what's going on there, but only spent a few minutes at work trying to figure it out

busy day in this thread... bump. anyone have any resources?

Udacity has an advanced python course I'm going to check out. anyone have anything else?

I know it's not optimal, but have you done codecademy? Is the experience level far below where you're at?

I don't know many good Python resources aside from maybe t*rrenting a university book.

Still haven't found a good solution for this, anyone got any ideas?

Designing a comments system:

Comments
----------
ID (PK)
UserID (FK)
Date
Comment

Now the problem is that the comments system works across multiple entities on the site. Arcade games, tutorials, manual entries etc etc. I don't want multiple comments tables per entity, just one table for all comments would be best (unless there's a really compelling reason not to).

So how to associate comments with a generic entity? A few years ago I did it my creating a GUID for each entity, and linking to the GUID in the Comments table. However, this has some pretty horrible problems, for example if someone reports a comment you flag it as reported, but in the admin pages all you have is the comment and the GUID, and it's difficult to elegantly find the source of that comment without having to search all your entities tables for the GUID.

Any ideas? Everything I can think of has some sort of inelegant design aspect to it. For example, with each comment I could store it's URL where it was posted but that again gets tricky if the comments are paginated or the URL of the entity changes (could happen).

Could you store the metadata that lets you derive the url? That shouldn't change (maybe?) and if you updated the irk paths you'd be able to calculate the new url.

One table with guids makes sense to me.

Confused about this. Can't the comment be flagged reported in the Comment table? Why are you searching for the entity?

The context matters sometimes.

EG:

Someone comments "this content is racist" and the author of the content in question flags the comment because their content isn't racist.

In the admin section, you have the flagged comment "this content is racist", but you need to take a look at the content to see if it is or not. So you have to search a bunch of tables for the corresponding GUID to find out what entity it's referring to, a game, a tutorial etc.

Storing meta data is the only way I guess. Every entity has a unique ID, so I guess I could store:

Entity (int)
EntityID (int)

Where Entity is an enum:

enum Entity{
Game = 1,
Tutorial = 2
}

etc

hows the flagging functionality work? maybe just throw some extra data in there instead of complicating the comments

OK, that makes sense. GUID + enum seems fine. It's not elegant but I don't think there's an elegant solution.

Thanks for feedback, guess that's the way to do it then. Feels a little nasty but guess that's the only way!

I'm unclear if your asking how to structure you DB or your objects? It seems
that your asking about the db, and the problem you're running into is that a
Comment record can tie into records from many other tables.

Conceptually, you have a "type" problem, in that you have all these entitities
that are of the Commentable type, but that type exists nowhere in your data --
but only in your head. So what does that "type" mean? You mentioned a source,
like games, tutorials, etc. Is all you need a text description of that source?
I'll assume so.

You can solve this at the DB level, eg in your reporting problem, by creating
this type with derived tables.

and then join your comments table on this derived table using guid.

I find this more readable than the previous posts. It's also easier to tell what's happening

My proposal got accepted for Google's summer of code so I will be completely busy this summer. I have to admit, I'm pretty nervous about this since this won't be an easy project. I'm already experiencing imposter syndrome now. What's scary is that I will have to work with core audio which will be used for live video and chat.

In addition if I fail to implement my proposal that means no stipend.