407 karma · joined November 29, 2008
Dublin, Ireland.
Email: phil at domain below
www.brassy.net
Giving the hexadecimal representations of the 3-way handshake... really? You may have gotten a dumb recruiter and you may think you're smart, but from my perspective, you answered the questions in a pretty dumb way given the context of non-technical recruiter, very obviously reading answers from a sheet of paper.
I've done two of these before and I've often said "Oh well, it might be down on your sheet at this thing" and the recruiter goes "Ah, yeh, that's it. Tick" and moved through 3-4 questions that in theory I might have gotten wrong. If you take the "be a dick" routine... Congrats. You won the moral war. Best of luck with your next job.
Workday's building out a new cloud platform based on Openstack, custom deployment tooling, containers & sensu for monitoring. We want system engineers who can code to come in to work on project related work.
If you're far in the east bay commuting to the city or the valley, there's a good chance you come right by our office every day. We're on the intersection of 580 & 680! We've got some extremely strong technologists, passionate about open source working here trying to create a best in breed delivery system and cloud platform for our software.
We treat our config mgmt process like a software pipeline and we've a lot of software engineers on staff working on this problem hand in hand with system engineers.
I've been here for nearly 7 years and it's a fabulous, medium sized company to work for with some great people.
http://www.workday.com/company/careers/job_description.php?i...
To me I think about "investing" as trying to guarantee a return over the long haul. All the smart evidence points to taking a strategy that links you to index funds. This is what I ended up doing in terms of carving up my investments https://www.bogleheads.org/wiki/Three-fund_portfolio
When I started this though what I actually, of course, wanted to know more about was the sexier, potentially much higher return end of "picking stocks". This is still sexy to me, and I still get inclinations to pick stocks every now and again, particularly in the tech sector where I feel like I have an edge. But as I've done dummy investments in the past, the market has bitten me in lots of unexpected ways. General market downturns, edgy sentiment around quarterly earnings, bad product releases etc. etc. So now I call this what it is: high stakes gambling. I do play, but with money I'm ok losing. The kids college fund goes uses the three fund strategy described above making heavy use of index linked funds.
Problem is, it seems a little disingenuous
I'd really like to see more effort going in to API's that allow you to pull data from (in this case) PostgreSQL in a meaningful way that are open, extensible and composable. Maybe this is a "big platform" problem, but for me all these once off dashboards just don't scale when you've got so many different parts of your stack.
As someone who competes against them for talent, and having seen dozens of examples from different parts of their business, Amazon is an extremely competitive employer on the tech side for experienced employees. They typically pay nicely above market
We have whole swaths of teams that just do backend development.
Basically, get in to a larger organisation that allows you to specialize a little more. Or go work for a company that just sells backend infrastructure / middleware :-)
Don't get me wrong on Reddit. I'm a member and love reading it. But there's times I want serious and times I want jokey.
So, the killer reason people are here are because of the other people that are here. Which is the reason you can't just replicate this by building a clone with better software.
Often times I find the comments about articles here more illuminating than the articles themselves and that speaks to the quality of visitors.
1. Find yourself a niche. Expert in X where X isn't just a programming language. Build relevant domain expertise which means people who are hiring you are hiring your experience as well as your skillset and you get to stop them running down rabbit holes. e.g. Java programmer who's built large real time streaming systems with Spark. Find a niche that's hot where lots of companies are looking for that expertise.
2. Be fairly mercenary with pay and job. Holding out for higher offers, setting expectations with recruiters early in the process about your salary expectations etc. Ask for exactly what you want.
If you're on $160k now, walk in and ask for $190k with a view to taking that for a year or two and then looking for $220 or $240k. Don't wait for the employer to give you a figure. Set that expectation with the recruiter early so they're not wasting your time. Be aware on that kinda money, employers are going to expect big things and in lots of cases will expect more than just coding.
I realise this is may be very obvious, but you will literally be optimizing for money. That could lead you in to shitty situations / companies. Personally I'd caution against that for most people. However, I understand money can sometimes be the most important hole in peoples lives with certain personal / debt situations, so I don't mean to judge.
If you are assessing your self worth against your paycheck though, this route won't satisfy you!
* "uncool" work. Stuff noone internally wants to work on.
* time critical - hiring takes time.
* lack of domain expertise - development isn't all equal. Ideally you want people who understand the problem domain.
* quick hit stuff - want something knocked up that'll take 3 to 6 months. Not worth the effort of resource planning internally.
* budgetary - typically contractors in most bigco's (that I know of) don't come from standard headcount budget. Headcount numbers are typically one of the kpi's used to measure growth.
Often times one or more of these reasons conspire together to make a compelling case to go externally.
http://chimera.labs.oreilly.com/books/1230000000545/ch12.htm...
* one tcp connection per request
* Server push functionality / server initiated streams
* current implementations means http/2 works over tls _only_ - neither Firefox nor chrome currently support non encrypted connections. This does keep things simpler with things like proxies in the middle I presume also.
* tls implementations must now support sni also so basically http/2 is now a forcing function for supporting sni which is awesome.
http://plg.uwaterloo.ca/~gvcormac/treccorpus/
92k messages, 52k of which are labelled as spam messages in the 05 corpus. Totals 300mb or so
The problem here is it's passive aggressive and doesn't actually communicate the issue to your colleague. The fact he's producing bad code probably isn't something he gets up to do every day.
The first part of any situation like this is clear communication. Talk to the person and you may have to do it dozens of times before it gets through. That doesn't mean the equivalent of throwing a bug report at him "Hey buddy, your code is shit. Fix it!"
He's a colleague. Sit down and talk through some of the code. Note your concerns and offer to help. Have clear and precise examples of your concerns, maybe presenting him with evidence. The first reaction any sane person is going to have if someone approached them like this is embarrassment and they're probably going to get a little defensive. Know that going in and tailor your conversation appropriately.
Enter in to the situation with some level of respect maybe even if that person hasn't really shown that he's deserved it.
Possibly, he'll never change, but I've seen enough people get better through coaching, mentoring and encouragement to know it's just as likely he'll make an effort if approached in the right way.
This is how I typically approach these types of problems....
Ask yourself if you're ready to see this through and by that I mean every possible outcome including leaving or getting fired or potentially getting the other guy fired. That means assessing your financial situation, possibility of getting more work etc. to me the logic goes that if this is such an important thing then I should be willing to accept all outcomes as this is the Right Thing To Do. It might seem a little melodramatic but it forces you to ask yourself hard questions.
Then, approach the boss. Tell him that you heard what he said before but the quality of your colleagues work is such that you can't stand over it and it's affecting everyone working on the project. If you end up having double standards for the code it brings everything down to the lowest common denominator.
My next option would be to bring a _solution_ to the table as opposed to just a problem. Let's bring in code reviews and I'll work with MrProblemCoder directly on his reviews one on one for a few months to try and bring his standard up. However, you need management backup for this. Maybe you don't even want to single him out, maybe you sit down collectively once or twice a week to do group reviews and breakouts afterwards. Maybe Friday afternoons are review the review days. The big thing here is that you want to make clear to the boss that there is a Significant Problem in a clear, rational way and have him understand the impact of it. Try leave your emotion at the door. Then present a solution which involves the group taking collective responsibility for the code quality with you leading the charge, but that management must back up and present.
If the outcome of that conversation isn't positive, then you have a management who doesn't care about quality and more importantly doesn't trust what you're saying about the impact. That would make it much easier for me to walk away as I now understand they've chosen the next path for themselves.
If you're not ok with that path then you could still try "influencing" these types of initiatives over a longer period of time instead of entering in to brinksmanship. Institutionalise code reviews for a portion of the team and show less bugs/rework and show the cost of crappy code. It's a softer approach and may take months and months of collecting data and influencing your colleagues.
These situations are not easy unless you're actually in a position to institute change directly!