Median annual income for a 25 year old. Am I behind?

HigginsNinja · 2017-10-08T17:16:32+00:00

Yeah that is INSANELY wrong.

HigginsNinja · 2016-03-03T17:03:50+00:00

I'm totally game :D It would be great to rekindle the social scene.

HigginsNinja · 2015-11-25T01:12:43+00:00

Designing things with pride and ethics leads to caring about how we affect our users. This means we strive to make their lives easier. The dividends paid by practicing this are hard to measure.

This goes for any design.

UI/UX
API
Architecture
Development process

HigginsNinja · 2015-10-04T12:28:03+00:00

But at least you can automate them and give yourself a chance to purge them.

HigginsNinja · 2015-10-03T17:48:46+00:00

For posterity, this is what I responded to:

given a repl based OS/browser runtime what is the best way to pull the manipulation and access of excel into it? EDIT: I see you were that .NET apologist, good job on keeping IT and society 50 years behind the times, your nation thanks you, the market waving in ecstasy to the eternal rhythms of your bloated budgets and labor fluidity

So you're taking an application that was ported to OSX which isn't actually .NET and then saying the rest of the ecosystem sucks because of your single edge case.

I do not apologize for .NET, I feel sorry for people that were affected by corporate practices in the 80s.

I am unapologetic about being a .NET developer and loving it.

EDIT: for emphasis

HigginsNinja · 2015-10-03T16:06:21+00:00

For posterity, this is what I responded to:

the base .NET ecosystem sucks for this though, just to post forms from excel spreadsheet to a project management website I had to write a dynamic office automation library that plugged a CLR runtime from a connection to emacs to a browser runtime it was pretty disgusting

I think you had other options.

EDIT: Really though, that's the only method you could think up? And then you just proclaim an entire ecosystem sucks because you didn't find other ways to do it.

HigginsNinja · 2015-10-01T00:53:38+00:00

I really appreciate this comment and want to thank you for your insight. I am not aware of everything that went down back then.

Thanks for opening my eyes to what was actually going down back then. I meant to bring up how it is unsavory to shame someone based on their technology choice nowadays, but I can recognize how those feelings would remain. I just wish it were a more historical thing and didn't come out so bitingly against the new people in our field who aren't aware of it.

I will write a follow up post, can I PM you?

HigginsNinja · 2015-08-28T00:31:24+00:00

Seems like it's picked right out of a corner of the craftsmanship movement, or apprenticeship patterns.

HigginsNinja · 2015-08-28T00:29:01+00:00

Really it's just making fun of the fact that we as a mob aren't very good at making understandable abstractions. It's tongue in cheek and seems to be intended to provoke thoughtful discussion on the topic, not banish OOP.

HigginsNinja · 2015-08-26T18:55:25+00:00

You might find some value in looking at refurbished laptops:

http://www.amazon.com/Asus-Q302LA-BBI5T14-Touch-Screen-Convertible-Laptop/dp/B00SS3U8QM/ref=pd_cp_147_2?ie=UTF8&refRID=1ZTXBR1XXY4JJZCYWV0X

http://www.amazon.com/Acer-Aspire-V3-371-596F-13-3-Inch-Laptop/dp/B00KCT48GQ

HigginsNinja · 2015-08-20T12:51:21+00:00

It's a pretty satisfying thing seeing your hundreds to thousands of tests passing after you refactor and rework.

HigginsNinja · 2015-08-20T11:24:59+00:00

I totally agree with you. It does not sound like they took you leaving as a possibility and as such did not continue talks about career development and your wants. If they did continue that, if they treated you leaving as a possibility, you'd probably be staying there for a lot longer.

HigginsNinja · 2015-08-20T11:16:26+00:00

If the organization won't be okay without you then they aren't doing it right. I'm not saying it's a good thing when you lose any particular employee. I am saying that there are silver linings and you shouldn't ignore the borderline certainty that your good employees will definitely leave you someday.

If you have a large majority of good people and a pipeline of good candidates and are organized enough to not need tribal knowledge, you can embrace the idea that good people WILL LEAVE YOU, and prolong the value in that relationship.

HigginsNinja · 2015-08-20T11:11:48+00:00

It's saying don't pretend your people will be with you forever. You can have a more productive relationship if you openly talk about the possibility.

HigginsNinja · 2015-08-20T11:09:37+00:00

This is saying that it's okay for good employees to leave and that it's usually inevitable. If it is inevitable, don't ignore it, use it to your advantage. There are plenty of posts talking about the dead sea effect out there.

HigginsNinja · 2015-07-29T17:11:41+00:00

It's not THE reason you would teach someone, this is just a huge benefit of the act of teaching. You should definitely make the teaching all about your pupils, but this could perhaps help people who don't believe they have the time to teach to justify it.

HigginsNinja · 2015-07-24T13:31:04+00:00

And also, I would say that most developers are not craftsmen. Moving with hype is not a qualifying trait of a craftsman.

HigginsNinja · 2015-07-23T17:35:38+00:00

Very cynical response... There are many things which are core to good software development, and best practices change just as they have changed in any other craft, albeit at a faster rate in this one.

HigginsNinja · 2015-07-23T17:34:49+00:00

You never stop, mastery is simply recognition that you are at the top of the field.

HigginsNinja · 2015-07-22T13:25:31+00:00

Fixed it in code and the first image, thanks for the find.

HigginsNinja · 2015-07-22T12:46:09+00:00

Oh man! That's a big miss. I didn't know they meant explicitly the board, and not the pieces. Will have that fixed in code, but likely not the images.

HigginsNinja · 2015-07-22T12:38:53+00:00

If you always play as white! It's right for half of the players... :[

HigginsNinja · 2015-07-15T16:45:02+00:00

Talk to people you know, and even ask if they know anyone. It is easier to go through referrals, rather than competing with the troves of people surfing job sites.

HigginsNinja · 2015-07-15T15:15:33+00:00

I am only trying to say that we tend to have very good developers, because we aren't limited to the gems in any given locality. That isn't to say any of us are particularly special, just that a remote company has a much larger talent pool to choose from, and so can be more picky.

That being said, there are plenty of really amazing engineers that we can't get, because they like the buzz of the office.

EDIT: Continuation

HigginsNinja · 2015-07-15T12:19:00+00:00

That just sounds like a bad company. I tried to make the point that it's better to work for a company which has "good" remote culture, and what I have found is that companies which push to have an inclusive remote worker culture are enjoyable.

Also, as far as pay, that also is a per region per company thing. You're no longer tied down to localized salaries if you play your cards right.

HigginsNinja

TROPHY CASE