> In any case, enforcing age based job restrictions remotely is not feasible and I would thank the individual and encourage them to reach out to you when they turned 18.
I mean, I wouldn't consider it if I hadn't worked with his dad for 5 years. It's not like I'm actually hiring, but yeah.
I was aware of those 3 rules, and was really looking for the citation on 3 earlier. I was thinking about paying him, I can afford a few hours of minimum wage, and if I think I can't I can always stop it, but even then I'm not 100% certain what I'd need to do for that. Do I actually need to file for incorporation of some kind? at this point I'd probably just go sole proprietorship if I have to. Then I'd guess I'd need to either have him do a 1099 or W2 of which I might need to contract out to a HR company to deal with some of it, especially because of the across state lines stuff. I honestly only vaguely remember my employment around his age.
I just want to ensure I don't somehow end up with them owning half the startup if it ever goes somewhere by virtue of a later lawsuit.
right, but what if it is open source code? even though it's something the startup would use.
Also it's not clear to me if a minor can actually contribute to an open source project legally as they have to be able to accept a contract legally I would think.
I'd much rather have excellent documentation, and less crappy defaults so I don't have to ask so many questions, or do as much search, or blog as many "how to's", but we can't all get our wishes.
sigh I usually only click on other peoples questions if I think I know how to answer it. That's like 70% there's another 20% which might be curiosity, and maybe 5% other reasons. (This is all not including Unix SE where I read stuff to see if it needs retagging or editing or some other form of moderation.)
So imagine if everyone did what you did and now 50% of question askers really don't need an answer, they're just trying to add yet another source of "documentation*. If the noise ratio was that high I wouldn't bother.
Idk about you but my blogs return quite quickly on google if you search for something I wrote about. This seems like a more appropriate outlet for this kind of thing. Of course if the dev's around you have forgotten how to search... well I doubt they are worth what they're paid.
You need enough rep to edit a post, but really the question isn't the problem. It's the fact that you didn't actually need an answer.
It's really more that it seems to be self serving, because you weren't really asking a real question. The StackExchange model isn't really a Wiki, or a blog, or whatever. If you want to write user friendly documentation there are lots of ways to outlet that. SE is about people who have real problems that are really searching for some help, IMO, or maybe the just want to learn something they didn't know about (e.g. what's your favorite editor might get answers that included editor's and reasons you'd never heard of).
I do think this adds noise to signal, because what people who answer questions are there for is to help people who need it. You didn't, and thus it seems more self serving.
I think even if you thought the question should have been asked... you should have waited a day (or longer) and given someone else a chance to answer the question. Then you could have accepted their answer, or written your own if it wasn't good enough.
I've answered my own questions many times on SO site's... but I don't think that you should ask a question you know the answer to when you ask.
I do not think SO is a wiki for programming question. I feel it's a place for people to go for help when they have a problem.
Given I occasionally ask questions I could have looked up, so it helps other people, and occasionally I end up answering my own question (by looking it up), after I've given others a chance to provide an answer.
It just feels like abusing the system by asking a question you know the answer to. That will stay unanswered for 2 days (since that's how long it takes before you can accept your own answer). At the very least he should have given other people a chance to answer, instead of rep whoring.
'Postgre' is improper always. You should either say 'Postgres' or 'Post gres que el'. There is a Factoid on the Postrgres site about proper pronunciation, and there have even been discussions about just going back to the name 'Postgres' which was the original name of the project.
I'm not sure 4 is in the right order, considering you didn't name anyone/anything. I would put kernel dev's above framework devs. 0 and 1 are equal in my mind. Basically you should be able to give names for up to your #8 if you can't name person/company/project it should probably be lower.
I would order 0 1 (etc), 2, 3, 5, 8, 4, 7, 9, 10 11, 12, 13, 14 (comma placement is explicit where I find those levels equivalent)
it's a client to the restful interface... web browsers current suck at restful interfaces because forms don't support all the http methods, and you can use your own image for a button (or other form element).
I personally think you can learn everything you need to know by reading ch8 and on. the appendices are a great HTTP reference. seriously though the book seems to rehash the same stuff over and over, ch8 is more of a summary of that same stuff.
I mean, I wouldn't consider it if I hadn't worked with his dad for 5 years. It's not like I'm actually hiring, but yeah.
I was aware of those 3 rules, and was really looking for the citation on 3 earlier. I was thinking about paying him, I can afford a few hours of minimum wage, and if I think I can't I can always stop it, but even then I'm not 100% certain what I'd need to do for that. Do I actually need to file for incorporation of some kind? at this point I'd probably just go sole proprietorship if I have to. Then I'd guess I'd need to either have him do a 1099 or W2 of which I might need to contract out to a HR company to deal with some of it, especially because of the across state lines stuff. I honestly only vaguely remember my employment around his age.
I just want to ensure I don't somehow end up with them owning half the startup if it ever goes somewhere by virtue of a later lawsuit.