redidas

Personally, I'd rather have a few extra mm of thickness and batteries that are not glued to a keyboard. Efforts could be made to keep this tech more repairable.

What about for say a small non-profit that isn't tech-savvy that will have at most 10 pages of content?

I could see where this could really be an issue if there was a lot of content or integration with the website being made. And I suppose too preserving old URLs (if that's something the client cares about)

How does Weebly compare to other options like Squarespace? I'm currently researching these kinds of services so this couldn't come at a better time.

That HR barrier is really difficult to understand. There are so many libraries and frameworks these days, and companies are looking for a person with particular experience in a particular combination of things. It doesn't seem to matter if you know similar tech and are willing to switch over.

I wonder how much good talent is never even looked at because of this.

From their description I'm guessing Northeast Minneapolis. It is an old blue-collar area currently being revived, and has quite a few older 3-story houses.

A lot of the old warehouse buildings have been gutted and renovated, turned into office spaces, breweries, lofts, restaurants, and coffee shops. Its also considered the arts district of Minneapolis.

I think the crime used to be worse than it currently is, but I'm not certain of that. I started working in the area a few years ago, and I haven't witnessed anything unpleasant. It feels quite safe here.

If you go across the river to North Minneapolis, you'll run into a rougher neighborhood with bars on windows and stuff like that. But even then I've heard things are improving over there too.

Add to that list "Business Intelligence" developer/analyst, although that term is gradually changing into something about analytics and data science, which are demanding degrees in statistics.

The reality is that a lot of "Business Intelligence" work is writing SQL & reports for business types that don't know how to write SQL or don't want to learn.

It means writing a lot of reports, but its a good way to get exposed to a business and yet still be involved with light development. There's room to grow too if you want to learn more about data warehouse design, ETL processes, OLAP cubes, etc etc.

I dropped Dropbox (except for when I have to use it at work).

The tipping point for me was Condoleezza Rice. But there were other issues that were building up. It was consistently eating my laptop battery, and on my desktop with traditional hard drives, it would take forever to start up and finish indexing files.

I replaced Dropbox with a mix of things. My documents went to Google Drive. I converted my old windows desktop into a xubuntu linux home server type thing, and installed BT Sync for the other files I had to sync.

I also do plenty of other things with my home server. Really wish I set one up sooner.

I don't see how that's anti-competitive.

Isn't that just... competitive?

No you are not. In fact Gruber's podcast yesterday talked about that very thing. They thought it might be called iPhone "pro" because anything else meaning bigger just doesn't sound like Apple.

Overall this whole event was odd. It was more Apple reacting to trends rather than setting them...

Hi HN

I told myself I'd submit this to get HN's feedback on this side project when I finished it... but I kind of ran out of steam/passion to finish all the lessons and promote the site.

The primary audience for this was going to be business analysts and other semi-technical people that would get some value out of knowing how to write report-style queries in SQL. So I was only going to focus on SQL SELECT statements.

Once the app was "finished" and it came time to write the content, I had several realizations:

  - Teaching is hard  
  - I should have wrote the content/lessons first  
  - The lesson viewer could have been done differently  
  - SQL lessons should really have an interesting database to go with it  
  - I had a lot more fun experimenting/rewriting the app than finishing it  

But I'm curious - was I heading in the right direction? Is it worth finishing the content?