Items tagged with: other
Lovely stencil work by thepinkbear.rebel street artist of a neanderthal man holding a briefcase in one hand and a spear in the other. Wearing a shirt, tie and suit jacket over an animal skin. Ready for a solid days work.
Location: Bath Street, Glasgow, United Kingdom
Full image: Link
#photography #CC0 #Unsplash #APIRandom #Lovely #stencil #work #by #thepinkbearrebel #street #artist #of #a #neanderthal #man #holding #a #briefcase #in #one #hand #and #a #spear #in #the #other #Wearing #a #shirt #tie #and #suit #jacket #over #an #animal #skin #Ready #for #a #solid #days #work #BathStreet #Glasgow #UnitedKingdom
HN Discussion: https://news.ycombinator.com/item?id=19953213
Posted by kachnuv_ocasek (karma: 1455)
Post stats: Points: 157 - Comments: 47 - 2019-05-19T13:36:59Z
#HackerNews #and #heuristics #how #modern #other #sat #solvers #tricks #work
HackerNewsBot debug: Calculated post rank: 120 - Loop: 128 - Rank min: 100 - Author rank: 57
HN Discussion: https://news.ycombinator.com/item?id=19926948
Posted by shalmanese (karma: 8783)
Post stats: Points: 75 - Comments: 88 - 2019-05-16T07:40:25Z
#HackerNews #accept #chinas #nations #other #rise #singapore #spare #urges
HackerNewsBot debug: Calculated post rank: 79 - Loop: 85 - Rank min: 60 - Author rank: 59
HN Discussion: https://news.ycombinator.com/item?id=19691055
Posted by Digit-Al (karma: 998)
Post stats: Points: 147 - Comments: 100 - 2019-04-18T14:02:11Z
#HackerNews #and #how #kids #other #peoples #the #tictoctrack #track #watch #with #your
HackerNewsBot debug: Calculated post rank: 131 - Loop: 212 - Rank min: 100 - Author rank: 33
HN Discussion: https://news.ycombinator.com/item?id=19672436
Posted by laurent123456 (karma: 4420)
Post stats: Points: 174 - Comments: 43 - 2019-04-16T10:26:34Z
#HackerNews #and #code #for #games #github #guide #hitchhikers #infocom #other #source #zork
HackerNewsBot debug: Calculated post rank: 130 - Loop: 113 - Rank min: 100 - Author rank: 56
HN Discussion: https://news.ycombinator.com/item?id=19666545
Posted by snowisgone (karma: 120)
Post stats: Points: 238 - Comments: 96 - 2019-04-15T16:26:38Z
#HackerNews #against #and #apple #companies #conspired #google #how #other #own #tech #their #workers
HackerNewsBot debug: Calculated post rank: 190 - Loop: 142 - Rank min: 100 - Author rank: 133
Traffic-choked cities like Philadelphia, Los Angeles and Portland, Ore. may be emboldened by New York’s decision to give congestion pricing a try.
Article word count: 1808
HN Discussion: https://news.ycombinator.com/item?id=19549125
Posted by wpasc (karma: 793)
Post stats: Points: 82 - Comments: 81 - 2019-04-01T22:45:13Z
#HackerNews #cities #clogged #congestion #embraced #follow #other #pricing #will
San Francisco is considering imposing a fee to drive into its busiest neighborhoods. A fee to drive into parts of Manhattan was approved on Sunday as part of the New York State budget.CreditCreditBen Margot/Associated Press
[What you need to know to start the day: Get New York Today in your inbox.]
Los Angeles traffic is so bad that buses crawl along at less than 12 miles an hour. In San Francisco, car speeds have fallen to 10 miles per hour. And Seattle’s streets are so choked the city needs to find ways to have fewer cars altogether.
Major cities across the United States are facing increasingly clogged roads and have had frustratingly little success in dealing with them. But now that New York has adopted congestion pricing in Manhattan, the rest of the country is far more likely to seriously consider embracing such a policy — even though it was once considered politically toxic, according to municipal officials and transportation analysts.
“New York’s use of congestion pricing could be a game-changer,” said Travis Brouwer, an assistant transportation director in Oregon, which has considered congestion pricing for traffic-jammed Portland.
“If New York City can prove that congestion pricing can work and gain public acceptance, it could give cities like Portland a boost as we look to introduce pricing.”
New York, the country’s largest city, will charge drivers to enter Manhattan’s most congested neighborhoods as a way to raise money for public transit and to persuade people to abandon their cars. The tolls are expected to start in 2021.
Philadelphia is now considering congestion pricing for the first time, closely watching New York’s move, “to see how this can help improve equity, safety, sustainability and mobility,” said Kelly Cofrancisco, a spokeswoman for Philadelphia’s mayor, Jim Kenney.
Los Angeles and San Francisco are already conducting studies to lay the groundwork for congestion pricing, and Seattle’s mayor, Jenny Durkan, is leading efforts to have congestion pricing in place by the end of her first term in 2021.
“It really does help to be able to point to some peer city and say ‘They’re doing this and it’s working,’” said Michael Manville, an associate professor of urban planning at The University of California, Los Angeles, who has advised Los Angeles on congestion pricing. “At the very least, it changes the conversation in other cities.”
Not everyone is ready to sign up. Kathryn Barger, a Los Angeles county supervisor, has raised concerns that congestion pricing could unfairly penalize drivers in communities with limited public transit, where “driving isn’t a choice, it’s a necessity.”
A handful of cities in Europe and Asia already have congestion pricing in place; it has helped clear roads in London, Stockholm and Singapore. But it has also been assailed by drivers and critics as an unfair tax that hurts the poor.
Fueled by an economic boom, a revival of urban areas, a proliferation of Uber and Lyft cars and an explosive growth in package deliveries propelled by the rise of Amazon, the average speed in urban downtowns fell to 15 miles per hour last year, down from 18 miles per hour in 2015, according to INRIX, a transportation analytics company.
“I believe the time has finally arrived to explore congestion relief pricing in major cities,” said Phil Washington, the chief executive of the Los Angeles County Metropolitan Transportation Authority. “Here in Los Angeles, our congestion challenges are just as bad, if not worse, than Manhattan’s.”
In New York, Gov. Andrew M. Cuomo and Mayor Bill de Blasio pushed the congestion pricing plan to alleviate traffic and to raise money to revive the ailing subway system.CreditDave Sanders for The New York Times
He added, “We cannot sit idly by and watch it get worse.”
In New York, many details of a congestion pricing plan — including how much drivers will be charged — are still being worked out. The plan was the culmination of a campaign that started 18 months ago and drew transit groups as well as prominent business, civic and labor leaders, who saw no other way to tackle gridlock.
Gov. Andrew M. Cuomo staked his name on it and wielded his political power to push it forward, making it a centerpiece of the $175 billion state budget after past efforts had unraveled. Even Mayor Bill de Blasio, who had been lukewarm about congestion pricing and has had a frosty relationship with the governor, threw his support behind it. They had made the case that it was crucial for raising the money needed to modernize the city’s crumbling subway system.
And city transit officials, facing a growing financial crisis, warned repeatedly that the alternative would be huge fare increases.
Congestion pricing’s moment follows decades of failed efforts to unclog roads around the country. Historically, cities responded to congestion by building more roads or widening existing ones — only to find that those, too, became jammed, said Matthew Turner, an economics professor at Brown University.
As a result, America’s roads are carrying more traffic than ever. The number of people driving to work climbed to about 130 million in 2017, up from 121 million in 2012, according to an analysis of census data by Social Explorer, a research company. Of those, more than 116 million drove alone, and only 14 million car-pooled. Just 8 million workers took public transportation.
The increasing traffic has been accompanied by concerns over health, safety and environmental implications. The number of pedestrians killed in traffic in the United States is approaching a three-decade high.
Traffic woes have emerged as the underside of successful cities: The boom leads to an influx of new residents, businesses and construction. More than two dozen major American cities, including New York, Boston, Philadelphia, Austin, Los Angeles, San Francisco and Seattle, have more congestion now than a decade ago, according to an annual global traffic scorecard by INRIX.
The most recent scorecard found that congestion left American drivers sitting in traffic an average of 97 hours last year, up from 82 hours in 2015. That, in turn, cost the economy roughly $87 billion in lost productivity last year, up from $74 billion in 2015, according to INRIX.
“It only takes one car that doesn’t get through an intersection to block two lanes of traffic,” said Trevor Reed, an INRIX transportation analyst.
In Seattle, Amazon’s relentless rise has helped to turn the city into a major tech hub. Now, major infrastructure and development projects are expected to lead to even more gridlock.
“As we build a city of the future, we must reduce our reliance on cars,” Ms. Durkan said. “My goal is to make our downtown core a healthier place for all with fewer cars, a more equitable transportation system and less climate pollution.”
Road pricing has been used on some American highways since the 1990s, with tolled express lanes — or so-called Lexus lanes — built alongside regular lanes, offering a faster alternative to drivers who are willing to pay for it.
Cities are trying to figure out how to make it work on streets. “There’s a critical mass forming where people are saying, ‘enough is enough,’” said Stuart Cohen, the founding director of TransForm, a California-based group that released a recent report on congestion pricing. “They’ve tried everything else and nothing’s working.”
In Seattle, the rise of Amazon has turned the city into a leading tech hub, but has also overwhelmed the city’s roadways, prompting the mayor to embrace congestion pricing.CreditRuth Fremson/The New York Times
Still, Charles Komanoff, a New York economist whose models were used to develop the congestion pricing plan, said the idea of “putting a price on driving” clashes with America’s car-loving culture in which driving wherever the road may lead is often seen as the ultimate freedom. He compared pushing congestion pricing forward to “shooting a rocket to the moon.” “There’s so much gravity — the forces opposing this are so powerful — it almost seems like defying nature,” he said.
Oregon looked at congestion pricing in 2005, but “our traffic wasn’t that bad, so people weren’t willing to pay a toll to escape it,” Mr. Brouwer said. But Portland has been gripped by congestion as Amazon and others have opened offices. State officials are seeking federal approval for what would be the state’s first highway tolls on a seven-mile stretch through Portland.
Congestion pricing has also been seen as a burden on drivers who are poor and have been displaced from downtown areas by rising housing costs, and now must drive to work because of minimal access to public transit.
“Social equity was the conversation stopper when it came to congestion pricing,” Mr. Cohen said. “In West Coast cities, equity is very high on the political agenda.”
But Mr. Cohen said gridlock also slows down the bus and transit services many poor people depend on. Congestion fees, he added, can be discounted or subsidized for impoverished drivers.
In Los Angeles, public buses traveled at an average of 11.8 miles per hour last year, down from 12.2 miles per hour in 2013, according to transit data. Mr. Washington said he wanted to use the congestion fees to pay for transit improvements and to cover fares so that everyone can ride free.
A spokeswoman for Mayor Eric Garcetti of Los Angeles said he has supported looking at congestion pricing “because it has the promise to dramatically reduce traffic and improve quality of life.”
Still, congestion pricing remains a tough sell. After a recent report by Boston leaders and educators that recommended charging $5 to drive in some neighborhoods, Boston’s mayor’s office said the city would not be implementing congestion pricing.
In New York, drivers would be charged for entering Manhattan below 60th Street, where the average speed for vehicles is down to 4.7 miles per hour, from 6.9 miles per hour in 1994.
John Corlett, a lobbyist for AAA in New York, said the new fees could shift gridlock to other parts of the city if drivers bypass the central business district to avoid tolls. “To say this is going to reduce congestion may be a false hope,” he said.
But Sam Schwartz, an architect of the city’s congestion pricing plan, said he had received calls from officials and others in more than a dozen cities that have been monitoring New York’s progress. “If you can do it in New York, you can do it anywhere,” he said.
San Francisco is considering congestion pricing after trying other options to combat gridlock downtown, including expanded bus and rail service, installing dedicated transit lanes and added bike routes, said Tilly Chang, executive director of the San Francisco County Transportation Authority, which is leading the city’s congestion pricing effort.
“Everyone agrees there’s a problem,” Ms. Chang said. “There are multiple views of the solution. But frankly, we’ve tried a lot of them and they’re not enough.”
Follow Winnie Hu on Twitter: @WinnHu
A version of this article appears in print on , on Page A1 of the New York edition with the headline: New York Plan to Unjam Roads Opens a Path for Clogged Peers. Order Reprints | Today’s Paper | Subscribe
HackerNewsBot debug: Calculated post rank: 81 - Loop: 332 - Rank min: 80 - Author rank: 56
259 votes and 124 comments so far on Reddit
Article word count: 316
HN Discussion: https://news.ycombinator.com/item?id=19331307
Posted by devilcius (karma: 135)
Post stats: Points: 140 - Comments: 82 - 2019-03-07T19:29:02Z
#HackerNews #2012 #all #define #minimum #need #number #other #the #whats #words #youd
Though the concept of this question is intriguing, and may have a practical answer (as someone else mentioned that 850 words may be enough), I think this really speaks to certain philosophical problems about language. I would say that defining all the words in the English language, or in fact any particular word, is impossible. As philosopher W.V.O. Quine pointed out in his theory of indeterminacy of translation, no amount of linguistic explanation can completely ensure that any word is correctly understood to anyone but the speaker. If enough of the right compensatory changes are made elsewhere in the system of language, any word could mean ANYTHING.
Now, practically, this is unlikely, evidenced by the complete success of human beings to use language to express concepts and do complex things like build rockets and such. So you might be tempted to say ʼwell, this isnʼt the point of the question Iʼm askingʼ. But itʼs more subtle, because even if you think there may be some level of certainty of translation that isnʼt absolute that would constitute a definition, you have to say what level that is.
For instance, you may ask me to define the word ʼdogʼ. If my definition is ʼa barking mammalʼ, which uses three words, you and many other may find that definition to be acceptable in that if I gave you the definition first, youʼd be able to figure out what word I was defining. However, there are certainly other mammals that bark (such as seals), so perhaps I must find a more rigorous definition, such as ʼa hairy, barking mammalʼ, using four words. But still, even as I add to the definition and appear to be less vague, I only asymptotically approach a perfect definition. So where do we draw the line?
There are other concerns about this sort of thing, but itʼs too late at night for me to be bringing those up.
HackerNewsBot debug: Calculated post rank: 120 - Loop: 251 - Rank min: 100 - Author rank: 90
Top 20 books discussed on Stack Overflow and other Stack Exchange sites. We are a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a…
Article word count: 36
HN Discussion: https://news.ycombinator.com/item?id=19294913
Posted by BookInsider (karma: 55)
Post stats: Points: 114 - Comments: 42 - 2019-03-03T15:37:43Z
#HackerNews #and #books #discussed #exchange #other #overflow #sites #stack #top
Please follow us on Patreon for any update or improvement!
* Dec 2018 * Dec 2018 * Dec 2018 * Dec 2018 * Dec 2018 * Dec 2018 * Dec 2018 * Dec 2018 * Dec 2018 * Dec 2018
Previous Page: 1 of 3 Next
HackerNewsBot debug: Calculated post rank: 90 - Loop: 190 - Rank min: 80 - Author rank: 55
Article word count: 1736
HN Discussion: https://news.ycombinator.com/item?id=19225873
Posted by turingbook (karma: 1331)
Post stats: Points: 141 - Comments: 78 - 2019-02-22T15:01:50Z
\#HackerNews #developers #hate #how #make #other #with #work #you
We’ve all read those 10x developer articles (I wrote some – guilty as charged!). So if you want to know what you need to work on to improve…well, you have plenty of resources. But I have very seldom come across articles on what NOT to do or how NOT to behave as a developer. And actually, this may be the most important part of the equation!
So, long overdue, here is what I think is the top list of behaviors you should really work on fast, if you do any of them ;). Why? Well, you might not know it, but your co-workers might hate you for them, as you most likely negatively impact the whole productivity of the team – at the very least!
If you have one of these developers on your team, it might be worthwhile to share this article in your Slack team channel – just out of general interest, you know 😉!
I will try to prioritize the list from most to least impactful. The goal for me is to start the discussion on the list and prioritize it, too. So please comment.
That’s the first one, in my mind. You cannot work with a self-absorbed developer. I’ll even go so far as to say:
As long as you are willing to take responsibility for and learn from your mistakes, you’re not a bad developer. Click To Tweet
Arrogance makes you think that your code is perfect. You may even blame customers for being stupid and for crashing their program rather than reflect on why your software crashed. And that’s how you get:
But also messy, unreadable code for your teammates.
The problem with arrogance is that it is a behavior that will prevent you from improving. Stop being arrogant, or you’re just a lost cause.
Some of you may already know the Dunning-Kruger effect. We will mention this effect a few times in the list. Here is a graph explaining it:
The issue with arrogance is that 1) the developers don’t understand they are on top of the Peak of “Mt. Stupid,” and 2) they will stay there.
- Sloppiness in the Work Delivered
There are many ways developers can show sloppiness in the code they deliver. We all know at least one developer who:
* gives cryptic names for variables, or at best not self-explanatory
* puts typos in function names
* leaves old, outdated comments in the code
* shows a poor selection of data types and data structures
* doesn’t bother to run the code formatter, despite being told many times to do it
* ignores the IDE warnings
* copies and pastes StackOverflow code without understanding it or tweaking the solutions to fit their own code
* doesn’t take the time to document code (nobody wants to read the whole function or file to understand what it does)
* doesn’t handle errors properly
* uses excessive dependencies, and updates them without thinking
* doesn’t bother to understand the libraries or tools added to the code, potentially leaving glaring issues
* will always insist on following “best practices” without understanding why those practices are considered “best” (there is no such thing as best practices that adapt to every team)
Don’t be such a developer. They annoy the hell out of their colleagues. They slow the whole team’s development process down, requiring their teammates to spend unnecessary time on their code reviews. Their team will dread those code reviews, will grow impatient (we’re still humans), and bugs will get through the net.
The best way to solve this is for these developers to start to take pride in their work (not to be confused with the arrogance mentioned in point 1.
- Disrespect of Other People’s Time
The two thing developers hate most are interruptions and unnecessary meetings. That shouldn’t come as a surprise, as meetings are just scheduled interruptions. Developers can’t easily go back to where they were right before an interruption. They need to get into the mindset for development and then slowly trace back to where they left off. And every fellow developer knows that.
So, here are a few ways you can show disrespect to your colleague’s time and productivity:
* interrupting another developer who is clearly in the zone, for non-important stuff;
* constantly arriving late to meetings, which is a definite choice – whatever anyone says. Either the participants must wait for everyone to be there to start the meeting, or they start without the late developer. In the latter case, he or she will need to be brought up to speed at some point, hence some time lost, and arriving late will disrupt the flow of the meeting in any case;
* rambling on and on during meetings. Or, if there are non-coders in the audience, being unwilling to adapt to the audience and wasting time for the entire audience, as any point made will need to be explained again.
- Constant Negativity
Most developers are enthusiastic people, but sometimes you may have the chance (or misfortune) to work with a negative one. Negativity is infectious. If someone complains, it focuses the attention on the negative side of things.
They will criticize every choice made: the language, for instance, although, most of the time, those developers are clearly at the top of Mount Stupid (in the Dunning-Kruger Effect).
Don’t misunderstand me; there should be some criticism in the form of constructive opinions. For example, a Scala developer could talk to a Java developer about promises, saying, “Okay, your language is not as good as mine :P. But you could try CompletableFuture to have a taste of what a monad is. I will show you what you can do with that.” But unfortunately, that kind of friendly attitude is very rare these days.
I’m sure you have all seen a developer once in a while steal credit for the work produced by a team. This can be done through an email to management, a 1-on-1 talk or another sneaky non-straightforward way.
Developers value competence above all. Taking credit for someone else is taking the other’s competence for yourself and removing it from him or her. This is pretty high up on my list, as I feel it creates a lot of tension and distrust.
For greedy developers, such strategies might produce short-term visibility. But in the long run, they will be alienated. Other team members will evolve their communication to highlight their contributions better. After all, there are many ways to give credit.
- Disregard for The Team
Software engineering is done collaboratively with designers, product managers, and other developers. Respecting other people’s input and work is necessary if you don’t want them to go into Hulk mode and flip their desk. For instance:
* “How” documentation: many programmers comment on every single line of code without describing why it’s doing what it’s doing. If there were a bug in the program and you stumbled across this code, you wouldn’t know where to begin.
* Implementing an ugly or not-to-the-specs UI “because they’re not a designer”
* Not mentioning a UX problem to the product manager, because it’s not part of their job. Ignoring the big picture will make the software hard to use, expensive to maintain, and inconsistent with the other components.
* Not trying to understand how design or product decisions are made. And then continuing to ask the same irrelevant questions – and not improving.
* Not considering other team members’ priority dependencies and leaving them stuck in the mud.
* Using a new tool/library without warning any teammates. This can cause unforeseen issues down the line.
- Lack of Focus
Engineering teams solve problems. They use their technical abilities to build features/fix bugs to solve those problems. And some developers just forget about this and will:
* philosophize about technical topics instead of focusing on the problems
* argue obstinately about technical topics without considering the initial problem (although you do, of course, need to argue when building the solution to the problem)
* have lengthy discussions about those technical topics yet rely on their own opinions (instead of facts – facts solve problems, not opinions)
With code, sure, you can have several solutions to the same problem, but either it works or it doesn’t; there is no in-between. With focus, you can easily alleviate all uncertainties by trying out code in a sandbox, for instance. But lack of focus wastes the time and productivity of everyone involved.
- Lack of Accountability
As mentioned above, either the code works or it doesn’t…but it needs to work in combination with all the code being added to the codebase by your teammates. Software engineering is probably the most collaborative work in today’s world. Any code you write will interact with that of other developers.
So, for your team to work well, you need accountability. Sure, code reviews don’t let you get away with anything. But accountability is an attitude.
Unaccountable developers will, for instance, offer excuses instead of solutions. Those excuses may include time constraints or complexity of the tasks. Nobody wants to hear excuses; they want to understand the steps to be taken toward the solution. Excuses don’t invite others to help or provide a good picture of the task’s progress.
This is my list. Feel free to add more if you think of any, or to suggest a different order of importance.
The first thing you should know is that this means your manager is not doing their job. The issue should have been identified and the problematic developer(s) coached — if they were deemed coachable. The manager should have given warnings and made the hard decision if the bad developers were still impacting the team.
A team with a bad developer is way better off short one developer than it is with a bad element. Click To Tweet
A manager who doesn’t understand this is a manager who doesn’t understand software engineering. You have the case for a bad manager, but that’s for another article ;).
So what do you do? I would say this is a question to raise in your one-on-one with your manager, so they can address the issue. If your manager does nothing, you have several options: see if the developer can be coached, and take it upon yourself (and with the cooperation of other teammates), or change teams/companies. Hopefully, this article can help convince the said developer to be a better co-worker.
HackerNewsBot debug: Calculated post rank: 120 - Loop: 194 - Rank min: 100 - Author rank: 45
HN Discussion: https://news.ycombinator.com/item?id=18851870
Posted by pseudolus (karma: 4526)
Post stats: Points: 125 - Comments: 63 - 2019-01-08T00:48:46Z
\#HackerNews #attention #beam #implicit #invisible #model #other #peoples #visual
HackerNewsBot debug: Calculated post rank: 104 - Loop: 142 - Rank min: 100 - Author rank: 69