jswinghammer

Yeah I don't really get that either. It seems like it was unnecessary to even write this blog post or include any examples if you really had to say this publicly. This seems like a great candidate for an office email.

Right now I'm picturing the worst about someone without details so my brain is just making up things that are probably much worse than anything that actually happened. I didn't much control over that instinct either which is the most annoying part.

If you ever read CS Lewis's classic book "Mere Christianity" he uses a similar metaphor there too.

If you knew that if you lost more than 10% then it wouldn't matter to you because a bailout would be required you'd probably do a lot of things that don't seem rational from your current perspective.

This analysis is a fairly straightforward Austrian perspective. I would only qualify it to say that this would apply to publicly traded stocks. It's been observed throughout the 19th/20th/21 century versions of the business cycle that stocks tend to rise along with the boom only to seriously correct in the bust.

The funding prior to this latest IPO spree is largely the result of capital not having a lot of good homes in the US economy these days. This is partially the result of low interest rates but also having a heavy regulatory burden on new industry which doesn't exist in IT.

So I can't help but find the salaryman thing to be creepy and strange (not that you did this but rather that anyone does).

Is this a common situation to find oneself in?

Does someone explain the rules or do you just figure it out by what every else does?

Does no one complain or quit in frustration?

Does anyone try to stop this practice?

A Black Swan in this context would be a shock to the system that no one saw coming nor could see coming. For instance a change in the sun which would drastically warm or cool the earth far beyond the effects of CO2. Maybe a natural disaster or an industrial accident that had a cascade effect that would reach beyond what anyone could have seen coming. You can't do anything about either of these things but that won't stop people from suggesting it could have been avoided with the right (or more of): "fill in the blank with your favorite solution to all problems in life."

The praying part might be good advice but I'm not sure he needs to go to church first.

A few observations:

- Your post is a little judgmental of the people living this area. 9-5 jobs are nothing to be ashamed of and wanting to watch TV after a hard day isn't necessarily a fault. If I were a business leader in this area I'm not sure I'd be interested in working to fix this if such a thing is even possible or desirable.

- What is your skillset? Are you a programmer? If so then you should be able to find work anywhere, you could work remotely, or start a business.

Doing something out of guilt is nothing I'd ever recommend. If you were doing this out of love then maybe this might make sense.

I'm with you but some of this article is just hyperbole. The quote from 1984 seems out of place at best given the context.

The question is are they good reasons. It's probably a mistake to assume that our current knowledge and understanding of economics represents progress from where we were before.

Having just finished a detailed account of the history of economic thought I can assure you that there were times when economists far better understood the nature of prices that came well before Adam Smith and Ricardo-both of whom didn't really understand prices at all.

Schools of thought tend to continue until they reach a dead-end that's impossible to ignore. A new school picks up the pieces and continues on again. We have seen that with the fall and rise of Keynesian economics.

Using NOT NOT IN is a syntax error in any event. I was answering in the hypothetical in any event.

There have been promises to fix this forever. They know it's a problem. It's just not a high priority fix.

No. MySQL is able to optimize an anti-join but not the IN condition. It works about the same as having a LEFT JOIN with a not is null check in the where clause. MySQL will see NOT NOT IN as just IN.

I've found that most of my coworkers over the years don't really react very well to the idea of me having a side project-unless they have one themselves. I think they believe it's pretty strange to making something not work related.

I'm not sure I've worked with many programmers at all who read on the side let alone make much of anything. Maybe my experience is just weird.

Yeah this winter was a pretty tough one to have a new baby. I felt bad for her. I can only imagine she assumed the world was just awful and grey. Today is the first nice spring day in awhile too.

This last winter has my family itching to move elsewhere.

No very few countries do.

Yep still working on Aterium. Going really well.

Here are my reasons for not using Java:

Visual Studio .Net (huge), C# vs Java (C# has WAY more features), SQL Server integration (if you are using it), IIS is pretty much painless to configure and works really well with .Net, LINQ which is a pretty good ORM.

My startup uses .Net which I chose for the basic reason that I know it very well and I didn't have time to go learn something else while I was trying to get work done. Any server I add is in response to more paying customers so the cost doesn't matter at all. It cuts into the margin a little but I only add new servers when we add a lot of new business. The initial cost of VS.Net was annoying but it wasn't bad and I was able to run off of SQL Server 2008 Express for a very long time.

How would you do multicast over the internet? That seems like a disaster/not possible.

Sometimes table scans happen even when you think you know what you're doing. If someone adds a column and doesn't think anyone will be filtered on that column then it can easily happen. I usually ask people:

- how big is this table getting? - how are you querying on it?

That usually fixes most problems before they happen. Not sure it's my job to specify a join type though. A nested loop join isn't a bad thing or even a sign of a bad thing happening necessarily.

I'm definitely on board with this. My last job was pretty lonely until we all started eating together every day. Eventually our long table was taken away by HR and we had to find somewhere else to go. We all wanted to keep it though because it made work much better so we found a way to still eat lunch together.

Seems like a price floor would solve that problem assuming that's what the people paying for the contractors really want solved.

Well it's likely that Americans will experience such poverty again given the course things seem to be heading on.

From my limited observation it seems like that might be possible. Many of their workers seem to be Haitian or Chinese immigrants. I don't really go there for anything but the occasional strawberry shake so my sample size is pretty small.

One thing that I've noticed about McDonald's is the sort of people who work there in cities versus the country. I grew up in the country and McDonald's was a place for kids to work. In the city it's a place where adults work. I suppose given the choice I'd rather hire adults but I'm not sure how an adult supports themselves in a city like Boston on what they pay.

There can be any number of reasons why people didn't get jobs. Not sure you can sue them for failing to hire a large group of people.

No offense but are you just being obtuse? Clearly I meant something other than what you are suggesting.

If you have read the K&R C book I am not sure you would say that. It's great no matter what you do with it.

I'm with you on the budget destroying business. It's just so easy to queue up material to read.