I seem to remember people were saying earlier in this thread that GoDaddy was a pretty bad domain name registrar. Which one do you guys use?

namecheap.com (haven't thought about it in a few years, so check nothing's gone massively wrong)

Related: a docu on scienos just released on HBO. Worth a watch if you don't know the full story and are in the mood to get pissed off about something.

That's an awesomely creepy documentary!

daveT,

Update!?

FWIW, they were offering a lot more last time I checked.
Are you in MA?

So I shared an idea with a friend at work who promptly went on to pitch it to the head architect and his manager. They loved it and have been singing his praises for 2 weeks now. I assume my only course of action now is to swallow it, move on and learn to keep my mouth shut from now on?

Before anyone asks, I pitched the idea 2 months ago to another architect and he told me to get started on the side but wait till the current release cycle was over ( in June). So I started a bit and this kid is literally just copy pasting some of my code and putting his name on it lol

Yea, no I am sure they are. They almost hired a guy we referred who was awesome on another project and he would have been 2.5x that. It was funny because the hiring manager was always adamant that there was always an opening for the cheap linux sys admin and would interview tons of people and then just deny them, he told me over 140 people denied in like 2 years.

Cambridge/Boston

I would make sure one way or another that everyone knows it was your idea and a lot of the code is coming from you.

A few things I have learned the hard way:

• Make sure everyone knows when something is your idea (in non-obnoxious way of course)
• Make sure everyone knows upfront if you think something is going to be hard (set expectation low, then potentially surprise to the upside)
• Make sure everyone knows you are working late (if you work in a shared office then that's set - if not try to send summary emails to a large group before you knock off)
• Make everyone in the whole damn department knows if you/your team comes in on Saturday. Be sure to remind them often. Never assume they're paying attention or that they will remember if not reminded.

There might be some more but they're pretty much in the same vein. Don't be a wallflower and assume people are going to give you credit where credit is due. Make sure you get your story out there early and often.

As a side note, no one ever notices or cares if you come in early. At least not at any of the jobs I've had. But they notice who's usually the last one out of the office.

Interesting, no sense of urgency, if he could find someone cheap ok but if not that was ok too, not concerned about wasting anyone's time.

I told one of my friends they totally loved me and are offering me the job. Totally fell for the April Fools prank.

I sent the resume in on Monday night. Wouldn't expect a reply this quickly, but I'll keep you posted.

If nothing else is gained, I am setting up the development environment in emacs and doing a bit of coding. The development environment has come a long way since I used Clojure last. It is pretty impressive, actually.

So one of my close friends offered me a contract gig to work on updating a former client's iOS App to iOS 7. He would oversee my work with each pull request.

Worked ~15 hours and fixed all the bugs. Did all the testing on the device and everything is good to go. Unfortunately we were dragging our feet on shipping the build to the client to test.

2 months later today we made some last minute fixes and test it in the simulator, all is well... shipped the build, client tests and app crashes 10 seconds into using it.

Client sends email stating that what we worked on for the past 2 months, that nothing is fixed.

So now I'm looking into it now.

ArghGGhhh

Did you test on actual device? Simulators are pretty much worthless for testing imo.

Probably great advice I hope to learn someday. Im definitely a pushover who expects karma to handle everything. Ill become a functioning adult one day I swear

I would also say that guy is not a friend. Nobody on my team would take credit for someone else's idea like that. And taking the work without crediting you is even worse.

We didn't bother with the last minute fixes. But yea I agree, moving forward, strictly going to test on iPhone.

So funny thing is that I checked out a commit prior to when I started working on the project, and I was able to reproduce the bug. So something must of changed on Apple's end to make something not work? I dunno, but I did fix it just now.

Yea that guy is definitely not a friend.

You should just start telling everyone that you made it and pitched it a while ago, and that this architect pithed it up the chain and now its being worked on. If anyone asks if you were involved with him pitching it up the chain you can say no, or just that you gave him the idea and he kept it mind or something that doesn't directly call him out but is honest and helps get you the acknowledgement.

You may think telling 1-2 people this won't spread, but that is incorrect. Especially if you tell 2 people at the same time, so it isn't viewed as a secret.

I went to the office and met him and he was a really good dude. He runs their infras with a pretty small group of people with tons of automation and scripting.

His overall attitude was very much one of being open to ideas and information and doing business at all times, but seemed to be very able to make firm and quick decisions. He seemed to be constantly juggling growing his team with working with major vendors to be on the edge.

You may be in a really good situation.

The absolute no-no is not saying anything.

Almost equally as bad is creating a big stink about how this was your idea and someone stole it.

You have to accept the situation as is and interpret it for everyone in your favor. One way is to act like everyone knows this was your idea and your project and the guy who stole it from you is working under your guidance. Ask various people how this is going, what the impact is going to be, how your guy's doing and whether he's doing everything he needs to do to make the project successful. Offer advice, take tons of credit for yourself and drill into any signs of failure and create doubts about his ability because you may need to throw him under the bus if it fails. For example, "Oh that feature is not working yet? That's surprising, I had it pretty much working, he's starting from the code I showed him and he should know exactly what to do because I told him. You know what, I'll spend some time to help him get back on track." You want people to give you credit if it goes well but blame him if it fails. And feign mild surprise, but quickly brush it aside when people don't seem to know this, like, "Oh he didn't tell you this came from me? that's weird, I guess he's not good with that stuff, but that's fine, he'll learn."

This is kind of devious but if your story is accurate, he deserves it.

I know nothing about the corporate world but why on earth would you ever swallow?

I could maybe see the pitching without credit somehow being not super douchy, but copy pasting code and putting his name on it is beyond all doubt. **** that ****.

No idea what the best course of action is though (reading candybars post makes me really happy i know nothing about the corporate world).

"So I started a bit and this kid is literally just copy pasting some of my code and putting his name on it lol"

Where is he copying and pasting it from?

I'm more of a "don't worry about this ****" type of person - but thats probably because I've generally worked at small-ish companies with strong technical management and good co-workers and so things like this have rarely come up and your true value is pretty apparent to most people. If I had to do most of the things in Suzzer's post I'd be looking for a new job pretty quickly.

However, I wouldn't stand for copying code. I once submitted a pull request to an open source project where the committer copied my code and committed it as his. I complained to the committer and his boss because I think its inexcusable and its usually very obvious what was done.

hello programming'ers,

small question. i know there was a blog recently (semi blog) about somebody going through the process of making the big pivot to programming from a semi related or unrelated field.

i was wondering if that is acceptable content, or was that a special case? i imagine the latter given you might be inundated with blogs if you were to allow that sort of about face. but figured i'd ask.

i currently have an econometrics/quant. econ background, and have pivoted out of finance, into strategic operations (test & learn software), and finally have landed in the field i want to be in which is data science and analytics. however! my programming skills are kind of embarrassing, even after having taken some courses (included those recommended here) to partial completion.

i get questions like "is this line of code pythonic? does it make any sense in spite of it working? what is the root of what i'm doing to my computer from an EEngineer's perspective and why is that relevant? why is this algorithm more correct than another?" all the time; and it would be neat to have an open dialogue with all the smart people that frequent these forums.

my objective is to eventually get into one of following fields: machine learning, artificial intelligence, game physics and real world translation.

thanks!

So, are you working on this project now? Can you just casually name-drop yourself while in groups?

Something like, "Oh yeah, when I was writing an earlier version of this part, I had problem X." Then when they ask what you mean, you can point out that it's your work, like its no big deal.

It is welcome content imo.

Mechanical keyboard purchased. This better be awesome.

Went with black widow ultimate. Needed some backlighting. Tried the stealth edition but didn't like the feel, not enough feedback.

Gonna be weird not using ergo keyboard anymore.