As a biker, having to park my bike at Walgreens and seeing the same Jump bikes parked at the bike stand, from the day before, and nowhere to park my bike is definitely a nuisance. Didn't really encounter this issue before, people normally come and go with their bikes. As a walker, when entitled scooter peeps jump on the sidewalk and start whizzing around you, and at almost hit you, it's a nuisance as well. I like the Ford Go Bikes/Citi Bikes, it's organized and it's a proven system in NYC and other cities, that doesn't burden others. Except those who lose parking spots in their neighborhood to docking stations.
Why are we so eager to blame companies on HN. I wish people would take ownership for their own actions instead of blaming companies. I can't wait for the article, "Take ownership of yourself, stop blaming others".
Also, this isn't taking token sales mainstream, token sales are already mainstream. This is making token sales available to the privileged (accredited investors) before they are available to the public.
I feel like amazon is my second search engine. So yes there is room with category specific search engines. Reminds me of when people started making specific apps from craigslist sub-categories.
I know I'm going to get shit for this. But what Shkreli did is common practice, and us disgracing him is Liberals using Alternative Facts. Where in the real world it's common to buy an outdated drug that many people don't use. Raise the price on it and try to innovate the drug into being a better drug, by using the increased profits. He just got himself into trouble because he doesn't know how to handle himself on twitter. I urge people to research this and look further into it, instead of having quick answers. There's a reason he wasn't convicted of anything. Sure, hike pricing drugs does sound evil and I get why people are mad. We want to live in a world where everybody has access to affordable healthcare, but sometimes the way things work aren't always simply put.
It's just as easy to make the tech industry look like a piece of shit. Especially with AI and self-driving cars. How dare Gooogle and YC take away jobs from hard-working middle-class Americans. It's almost worse, instead of price gouging, tech is going to take away jobs of many if not all Americans in the near future, but nobody on here wants to state that fact and say how sleazy tech is.
Now is more important than ever to be truthful with ourselves and how the world works and not get hyped up over shit, until we understand the whole process. Let's problem solve instead of name call and understand the process of things. Like how YC is testing a universal wage for people in Oakland.
I agree, to that extent, I really wish Bloomberg or Business Insider articles weren't posted on HN. They often are fluff and don't understand the details, and thus just create unneeded noise on HN.
I think Apple needs acquihire snapchat and promote Evan as the new Apple CEO. I have zero hate for Cook and think he is great CEO. But Evan is shaping up to have some the most modern product prowess out there. I don't know if these spectacles will be a hit, but I think his choices are in the right direction.
I'm not comparing frontend to backend. I also think data is fun and I don't mean to be little the job, but in a real world scenario its detail intensive, under appreciated, tons of edge cases and extremely complex if you plan to make it scalable and fast. So if you are an aspiring data engineer be aware of these pitfalls, because the first couple times you do it you will think its fun to try something new and create some fun useful analytics, but customers will often complain at how long it takes and want more. It starts to wear away at ones drive and passion for data. Its not the data aspect its the job/deadline aspect.
I agree. I enjoyed doing it the first couple times, but people would often complain why I wasn't done sooner and didn't appreciate the level of complexity that went in to doing it. Once the appreciation was gone, I believe that's when it turned into a mind-numbing task for me. I don't mean to be little the job, I think I have just become sour to it because of the lack of appreciation.
So I guess you are a data engineer? What makes it fun for you? How do work with your customers to give them what they need in a timely matter? I would be interested to know what stack you use to go from dirty data to customer consumption.
We should rename this job position to Data Sanity Engineers.
I have been thrown these projects at work before, where I'm the frontend engineer and I need to make some cool D3 visualization, but low behold the data is shit, and I have to help the backend team make the data useable. It's a mind-numbing job, that nobody wants, because it sounds like a one month task to get a good REST API up and working, but it usually takes three months, because you have to go back and forth making sure the data is right, and there is always 10 tricky edge cases that you have to work some magic on. Not only that but you need to have smart people cleaning the data, so that you don't make some big mistake down the line or your REST API is super slow, and you have to add another couple weeks or month to rework the data again. So that one month becomes three months, and most likely a year, because somebody will say that looks great but can we also add this, and it goes on and on. It's literally a mind-numbing job that most nobody wants. I have found that products like Tableau are the best for this, you still have to clean the data, but it helps speed up the process.
I guess there are many way to use points, but what was described in this article isn't the way we use them. Points are great for a group of people to groom a story (estimate a features difficulty). Points are an estimate of difficulty. The way we do it is we have a story that describes what feature will be built, then as a group we talk about it and then all at the same time (so we aren't persuaded by others) rate the story with points (level of difficulty) and if we all (developers) rate it at the same points then we add the points, if we have different opinions on the points (level of difficulty) then we discuss why we think it's easier or harder. And this helps others who wrote the story foresee issues or know of other simpler solutions. Works great if you ask me, and that's how we were taught to do it.
Yes, yes, yes, I am also a GCP cheerleader. It's so easy and intuitive to use. A load balancer is called a load balancer, an instance is called a compute instance, SQL is called SQL etc.., no AWS name deciphering. GCP's sidebar UI navigation is a dream compared to AWS's mind numbing grid of features. I had a fault tolerant highly scalable system up in hours, and I'm not a dev ops guy, I mostly do frontend.
Agile works fine. I find that people are broken and don't want to change, or they want to adopt some magic formula by talking about it a lot but don't actually practice it and when they run into problems they blame the process they weren't practicing correctly. If somebody has a process to change people's bad attitudes I would love to learn that.
If anybody has any resources to add to this list, please do or post your links in the comments. I just added Ian Goodfellows link to their html book. I would like to have a solid list of deep learning resources. Thanks!
Probably need a company to do it. Like Microsoft made Typescript, Facebook made React, Google made Angular, etc... We need Dropbox to make this, since they have Guido and he can push this on the python 3 community to make this a standard library. Dropbox please rescue us and pull the python to javascript community together. Please!!!
Can all of you python to javascript library creators get together and create one solid library, or maybe not all of you, because it would be a grid-lock of decisions. How about half of you with the most similar ideas get together and do one super solid library, instead of having 20 of these python to javascript libraries so the community can easily decide on one to use as a standard. This would be awesome! Thanks!
My friends, family and I have had a completely opposite reaction. We have all ditched Spotify for Apple music because it integrates with our apple tv, and other devices so well. Beats radio is also pretty good for music discovery, with Deadmau5 and Pharrell having their own DJ spots.
Commenting should be how people down vote. You should have to explain why it's not a good idea. Then if others agree with you, your comment will get up voted. Just as my comment is a downvote of github's downvote.
This comment is basically a down vote of github's down vote. Comments should be the down vote, because someone needs to explain why a suggestion, answer, code change, submission, etc... is not a good option. If that comment (down vote) is a good idea, it will then be up voted.
This comment is now getting downvoted. To be clear, so people stop downvoting this comment, this parent comment was initially downvoted to -1, it obviously isn't anymore.