FOX NEWS: President Trump says the Taliban wants to make a deal in Afghanistan

President Trump says the Taliban wants to make a deal in Afghanistan



Trump pays surprise Thanksgiving visit to troops in Afghanistan, announces peace talks with the Taliban are back on; reaction and analysis on 'The Five.'

via FOX NEWS https://ift.tt/2Y1xTUA

New top story on Hacker News: Improving CLIs with isatty

Improving CLIs with isatty
3 by jez | 0 comments on Hacker News.

New top story on Hacker News: Tracking down the true origin of a font used in many games and shareware titles

Tracking down the true origin of a font used in many games and shareware titles
3 by Lammy | 0 comments on Hacker News.

New top story on Hacker News: How to Build a Healthcare Unicorn?

How to Build a Healthcare Unicorn?
3 by saumik | 0 comments on Hacker News.

New top story on Hacker News: Find stuff in org-mode anywhere (2017)

Find stuff in org-mode anywhere (2017)
3 by skovorodkin | 0 comments on Hacker News.

New ask Hacker News story: Ask HN: Dealing with newcomers' arrogance?

Ask HN: Dealing with newcomers' arrogance?
3 by brianaluv | 1 comments on Hacker News.
I've been working(as a developer) on a software development project for quite a long time now. During this time, the team has changed a lot (a lot of people left, others arrived). Two coworkers and me are the oldest members of the team. Recently, I've been annoyed by the behavior of the majority of the developers on the project (those who are new compared to how long I've been on the project). Whenever they see something wrong in the codebase developed by former team members, like poor quality code or simply a defect, they laugh about it, making fun of the developer who wrote "such bad code"(without even knowing the developer in question or the context that caused him/her to write such bad code). Now, I've been long enough on the project to know that many reasons can explain poor quality code (like short deadlines, low budget, etc...), and the quality of the developer is not always one of these. Of course poor quality code should be pointed out, showed to people to learn what not to do or what is a better way of doing things. But It should not be used to make fun of people or humiliate them, especially when the people mocking others do not even write "triple-A" code. What also bothers me is that, the two other oldest members of the team don't say anything about that behavior. And that's why I'm asking if I should say anything or just let it go? Am I wrong feeling the way I feel? What would be the better way of telling it to the whole team? What would you do in my position?

New top story on Hacker News: Hack-a-Mol

Hack-a-Mol
3 by breck | 0 comments on Hacker News.

New top story on Hacker News: Google AdWords charged me for clicks in Istanbul while location-targeting the US

Google AdWords charged me for clicks in Istanbul while location-targeting the US
6 by siggi | 0 comments on Hacker News.

New top story on Hacker News: React in concurrent mode: 2000 state-connected comps re-rendered at 60FPS

React in concurrent mode: 2000 state-connected comps re-rendered at 60FPS
3 by macando | 0 comments on Hacker News.

New top story on Hacker News: ISOC revealed it would get 1.13B from US investors for .org

ISOC revealed it would get 1.13B from US investors for .org
3 by dano | 1 comments on Hacker News.