• 开源镜像
  • 开源沙龙
  • 媛宝
  • 猿帅
  • 注册
  • 登录
  • 息壤开源生活方式平台
  • 加入我们

开源日报

  • 开源日报第850期:《视频剪辑 QuickCut》

    31 7 月, 2020
    开源日报 每天推荐一个 GitHub 优质开源项目和一篇精选英文科技或编程文章原文,坚持阅读《开源日报》,保持每日学习的好习惯。
    今日推荐开源项目:《视频剪辑 QuickCut》
    今日推荐英文原文:《Non-Technical Skills That Help Developers》

    今日推荐开源项目:《视频剪辑 QuickCut》传送门:项目链接
    推荐理由:这个项目是一个使用 PyQt5 来完成的带有图形界面的视频剪辑软件,它并不像其他专业软件一样拥有许多非专业使用时用不到的功能,而是集中于平时简单处理视频常用的功能上,同时图形界面也使它比命令行界面的 FFmpeg 更便于使用。除了常用的合并分割视频等需求外,这个项目还提供了诸如调用别人家 API 来完成的自动生成字幕等拓展性功能,使得其用途更加广泛。
    今日推荐英文原文:《Non-Technical Skills That Help Developers》作者:Maxim Chechenev
    原文链接:https://medium.com/better-programming/non-technical-skills-that-help-developers-1d56e10c27db
    推荐理由:对开发者的一些非技术层面的建议,大部分与开发工作有关

    Non-Technical Skills That Help Developers

    How many new and unknown things there were when I started my career as a developer! The technical side was more or less clear, but everything about processes, internal communication, behavioural things, and so on was new. I learned most of these things by trial and error.

    I like to do some kind of self-reflection about my experience. It helps me to see how I end up where I am now. Looking back at my knowledge, I highlighted a few pieces of advice that I wish I had known before. It’s a mix of non-technical and behavioural skills.

    1. There Is No Such Thing as a Dumb Question

    I had this thing. I got my first job as a junior developer, and I was proud and happy. But I also had imposter syndrome — I knew that my skills and knowledge were quite low. And I didn’t want anyone to uncover that.

    So whenever I had anything that blocked me or something difficult, I was trying to solve it myself without asking for help. Or I was too shy to ask my questions, especially in front of a group of people. “They will think that I’m an imposter. Hide it, Maxim!”

    But in fact, it’s the opposite.

    People wait for questions from each other, and these questions are not stupid, they are just regular, typical questions. No one expects that you know everything; it doesn’t matter if you are junior or senior. It’s a part of working in the team — to communicate with each other, ask, and help.

    Don’t be afraid — just ask all questions that you have.

    2. Don’t Take It Too Seriously

    In most cases, we work in companies where your mistake will not affect someone’s life. Ninety percent of developers don’t work on building software for airplanes, self-driving cars, medical devices, etc.

    Usually, we just move JSONs from one place to another. If my code doesn’t work correctly, no one will die and no nuclear station will explode. Someone just will not be able to load funny cat videos or send dating messages. Or their Instagram feed will be down for ten minutes (how can people even survive it?). Fancy fashion brands will not be able to show their new banner. That’s ok — people can survive it.

    Sure thing, the IT industry looks fancy and essential; we have many modern devices and shining technologies.

    The round-shouldered developer (no offence, it’s just an image of myself) is a new sportsman, new astronaut, new rock star. People invest vast amounts of money in us round-shouldered people! Of course, we start to think that we are doing something significant and severe. But after all, in most cases, we just do a servant’s job. We help transform someone’s ideas into the product by moving JSONs from one place to another.

    3. Be Yourself, Don’t Pretend

    We all have the values that we believe in. What we are looking for in others. What we respect. Our passions.

    Corporate life can have a significant impact on it. It can change your motivation, sacrifice your values.

    I worked in a company where we were doing nothing for months but got paid. “What a dream company!” you can say.

    But it was incredibly dull and killing me. I could just go to the office, pretend that I’m doing something. Nothing happened there at all. It’s sad, as I saw so many problems and possibilities in our product, but no one cared. I wasn’t able to do a thing because the whole environment was passive and offensive. I had no power and no support to change it.

    I couldn’t take it, and I left that company. I was just spending my time for nothing. My life has a value and a purpose, and I won’t spend it in places where no one cares about anything. I don’t want to lose my energy and passion. My experience and knowledge have value, and I won’t spend my time in places where no one cares about me. I’m not just a little man without a voice in a vast corporate machine.

    And I firmly believe that people enjoy it and respect it when you follow your values.

    4. We Build Products, Not Just Code

    Developers don’t just sit in the dark corners of the office and write code. Sure, the outcome of our work is the code converted into a product.

    But what is a product?

    It’s an idea that is solving some problems — real human problems, not machine problems.

    Usually, there is user research, there is a business plan for how to make money, and people check markets to find a niche for this product. It’s way more than just lines of code. It’s an attempt to solve something, to make some parts of our lives better.

    “So what is the deal? I’m the one who can transform this idea into a working solution,” you ask.

    And the idea is to always think about the work from a product perspective. Am I doing the right things that users need? Will this feature degrade application performance? How do I know that this task will improve something? And a lot of similar questions are extremely beneficial to ask yourself. Because when you start to care about the product, you and your team can achieve great results.

    Great ideas should not come top-down only. Anyone should be able to propose an idea.

    5. Respect People, Not Titles

    People with titles like “lead developer” or “senior developer” look wise. They are great teachers who always help you and find the best words to motivate you. Gods who fix bugs by just looking at a display. Your best friends who would never let you down.

    The title doesn’t mean a thing (well, in 50% of cases).

    Sometimes you work with people who don’t want to help and teach, who are arrogant. People who love corporate political games. Who even don’t have excellent and friendly communication skills.

    Who knows how they get this title? Maybe they were the first engineer here and have been working here for ten years. Or perhaps they know how to show their best during the interview. Maybe they are just a good developer who wants to code more than to talk to people.

    Different companies have different definitions of seniority level. For some, it’s fine to focus more on technical skills, and some companies care about soft skills. And that’s fine.

    The point is this: Never judge people by their position in the company, and don’t have high expectations just based on the title. Find the right people, those with a decent character. Be respectful to these people, and you will be great friends (who cares if it’s a junior developer or a receptionist?). Respect people.

    6. Soft Skills Are Essential

    Why do I need these? Why do I need to communicate with someone else? Can’t I just talk to my computer in my very own way?

    I doubt it. The IT industry is not an industry of grumpy, bearded men who barely know how to talk (except how to talk to computers). I’m not sure that it ever was like that.

    We work in teams, and we work with real people with their mindset and characters, which usually are not the same as what we have. We need to consider that we are all different.

    Working communication is not just informal talks during lunch about the latest Netflix show or weekend plans. We need to talk to each other healthily at any meeting, and in corporate messages and emails.

    There are multiple reasons to do this, but the most important is that people work better when they can trust each other and communicate pleasantly. You don’t need to be a friend with everyone; no need to have drinks after work. But we need to respect our colleagues and help without aggression and any toxicity.

    Otherwise, if I cannot talk healthily, people will ignore me and avoid my opinion. The team itself will become less efficient. And I can forget about any kind of promotion or salary raise.

    7. Always Negotiate the Offer

    Interviews are exhausting. You spend a lot of time and energy, and you make a real effort to do it. So when it comes to the offer part, it’s easy to think that it’s finally done. That you just need to sign it and have a rest.

    Not really.

    The very last step is negotiating. You get your offer, and then you discuss it. It should not be scary at all. Because a company is interested in hiring you, they also spent a lot of time making this interview process.

    I’m not saying that you should go wild and ask for a 50% higher salary, but there is always room to negotiate. Maybe not a salary, but additional perks, holidays, contract length, stocks, etc. The worst-case scenario — the company just says no to your request, but they won’t withdraw the offer.

    Stay polite and friendly, and negotiate the offer. It will not hurt when you hear stories from your next colleagues that they have better contracts only because they arranged them.

    8. Don’t Burn Bridges

    Stay professional when you leave a company.

    Don’t make any conflict, don’t blame anyone, don’t write aggressive and offensive farewell emails. Yes, of course, sometimes you are right, and that nasty message would be fair, at least for your dignity.

    Life is unpredictable. The IT world is tiny, and you never know who you will meet again as a colleague or even a boss in the future. Your next employer can do a reference check and call that company that you just left.

    It’s better to keep a respectful and professional relationship with your ex-companies even if you hate that place and everyone there.

    9. Rest

    No one is complaining that he didn’t work enough when they lie on their deathbed.

    Don’t forget to rest. Disable work notifications on your phone (especially when you go on vacation). If something needs your attention, people will call you on your phone.

    Continually checking the working Slack is a terrible habit, as you won’t stop thinking about work. But your work is not your life. Think about your hobbies, family, pets, friends, etc. If you like coding after work, that’s fine as long as you are not doing work things.

    Take care of yourself and your health.

    Thanks for reading!
    下载开源日报APP:https://opensourcedaily.org/2579/
    加入我们:https://opensourcedaily.org/about/join/
    关注我们:https://opensourcedaily.org/about/love/
  • 开源日报第849期:《情感分析 Senta》

    30 7 月, 2020
    开源日报 每天推荐一个 GitHub 优质开源项目和一篇精选英文科技或编程文章原文,坚持阅读《开源日报》,保持每日学习的好习惯。
    今日推荐开源项目:《情感分析 Senta》
    今日推荐英文原文:《10 Awesome Chrome Flags You Should Enable Right Now》

    今日推荐开源项目:《情感分析 Senta》传送门:GitHub链接
    推荐理由:情感分析旨在自动识别和提取文本中的倾向、立场、评价、观点等主观信息。它包含各式各样的任务,比如句子级情感分类、评价对象级情感分类、观点抽取、情绪分类等,是人工智能的重要研究方向。该项目包含百度发布的情感预训练模型SKEP,能使用pip和源码快速安装,并支持一键分析预测情感。

    或许……是计算机拥有智慧的重要一步?

    今日推荐英文原文:《10 Awesome Chrome Flags You Should Enable Right Now》作者:Sanjeet Chatterjee
    原文链接:
    推荐理由:Flags 相当于 Chorme 浏览器的实验室,包含 google 尚在开发的许多实验性功能,本文介绍了一些推荐启用的设置。

    10 Awesome Chrome Flags You Should Enable Right Now

    Enhance your browsing experience with these experimental features

    (Image source: Author)
    Wouldn’t it be cool if you could magically upgrade your browser with features not known to the average Chrome user?
    Below are ten Chrome flags that help you to do just that.

    Chrome Flags are experimental features that aren’t yet enabled by default. To enable these, see chrome://flags. The flags stated below may be in the pipeline for official release in the near future. However, as of writing, they are still in testing.

    Reader Mode

    Reader Mode removes unnecessary visual clutter for distraction-free reading — highly important when so many visual elements fight for our attention. Poof, gone.
    (chrome://flags/#enable-reader-mode)

    Focus Mode

    Focus Mode opens the tab in a new framed window, omitting the tab strip and search bar for a cleaner interface.
    (chrome://flags/#focus-mode)

    Impulsive-Style Scroll Animations

    Rebuilding their Edge platform, Microsoft has brought their natural scrolling motion to Chromium.

    “The main idea is that each ‘tick’ of the mouse wheel tries to mimic a physical-based world where content starts moving quickly (an impulse) and then slows due to friction.” — Microsoft
    (chrome://flags/#impulse-scroll-animations)

    Tab Groups

    Tab Groups is for grouping and managing multiple tabs together, such as for different types of cheese.
    (chrome://flags/#tab-groups)

    PDF Two-Up View

    PDF Two-Up View is for viewing a PDF with two pages at a time. Interesting.
    (chrome://flags/#pdf-two-up-view)

    Force Dark Mode for Web Contents

    This forces all websites to render in a dark theme — even those that don’t have one yet, such as Medium. Yes, looking at you, Medium.
    (chrome://flags/#enable-force-dark)

    Quieter Notification Permission Prompts

    This is a simple feature to reduce permission prompts disrupting your flow.
    (chrome://flags/#quiet-notification-prompts)

    Tab Hover Cards

    Tab Hover Cards displays the tab previews on hover. It probably comes in handy when you have over 30 tabs open and can’t read the tab titles anymore.
    (chrome://flags/#tab-hover-cards & chrome://flags/#tab-hover-card-images)

    Enable Page Sharing via QR Code

    This flag allows you to share web pages with QR codes, for easily sending content to your phone. Of course, it comes with the awesome Dino mascot. Note: As of writing, this only seemed to work on Chrome Canary.
    (chrome://flags/#sharing-qr-code-generator)

    Parallel Downloading

    Chrome can establish multiple connections to download a single file in parts, resulting in an increase in download speed.
    (chrome://flags/#enable-parallel-downloading)

    Conclusion

    There are many more Chrome flags that are in testing, and many more features yet to come. If you like to live on the edge, check out Chrome Canary — the bleeding edge of the web. Thanks for reading.
    下载开源日报APP:https://opensourcedaily.org/2579/
    加入我们:https://opensourcedaily.org/about/join/
    关注我们:https://opensourcedaily.org/about/love/
  • 开源日报第848期:《github-readme-stats》

    29 7 月, 2020
    开源日报 每天推荐一个 GitHub 优质开源项目和一篇精选英文科技或编程文章原文,坚持阅读《开源日报》,保持每日学习的好习惯。
    今日推荐开源项目:《github-readme-stats》
    今日推荐英文原文:《Four of the biggest tech CEOs are about to be grilled by Congress》

    今日推荐开源项目:《github-readme-stats》传送门:项目链接
    推荐理由:github最近对页面进行了不小的调整和美化, 作为github用户, 我们也会希望自己的readme变得更加漂亮. 这个项目可以动态的获取仓库的信息并写入readme, 有统计卡片, 热门语言卡片, 以及自定义主题等功能.
    今日推荐英文原文:《Four of the biggest tech CEOs are about to be grilled by Congress》作者:Richard Nieva
    原文链接:https://www.cnet.com/news/four-of-the-biggest-tech-ceos-are-about-to-be-grilled-by-congress/
    推荐理由:美国国会或将解雇四个著名科技巨头的CEO, Apple, Amazon, Facebook, Google的统治地位可能因此收到巨大的挑战和冲击. 本文将介绍美国政治和科技界对峙的细节.

    Four of the biggest tech CEOs are about to be grilled by Congress

    It’s fitting, though perhaps a bit anticlimactic, that when Mark Zuckerberg, Jeff Bezos, Tim Cook and Sundar Pichai convene on Wednesday for a highly anticipated congressional hearing, it will be over video chat.

    Silicon Valley’s technology has changed the world, allowing people around the globe to stay connected even during an unprecedented pandemic. But the success of Facebook, Amazon, Apple and Google’s parent company, Alphabet — and the four men who lead those companies — has brought about another unprecedented phenomenon: the stunning amount of control Silicon Valley has over what the world sees, reads, buys and does online.

    How much control? Facebook is the world’s largest social network, with a user base roughly equal to the world’s two most populous countries combined. Amazon controls 38% of US online sales — Walmart, its nearest competitor, had just shy of 6% — and has data on other retailers using the giant platform. Apple’s App Store is a powerful gateway for software developers to find an audience with the company’s massive iPhone and iPad customer base. And Google processes about 90% of all web searches globally.

    The hearing, delayed by two days to accommodate a memorial for the late Rep. John Lewis, marks the first time lawmakers will have the opportunity to grill the CEOs of those four powerful companies at the same time. Officially, the topic is antitrust, the culmination of a more than year-long investigation into the market dominance of Big Tech by a House Judiciary subcommittee led by Rep. David Cicilline (pictured above), a Democrat from Rhode Island. In that time, the subcommittee has gathered more than 1.3 million documents from the tech giants, competitors and antitrust enforcement agencies for the investigation.

    But politicians are known to go off-script, and the hearing is expected to become a free-for-all, touching on topics as varied as election security, political bias and relations with China.

    Government officials have been wrestling with the power of tech companies for decades. In 1984, AT&T was broken into eight separate companies. Microsoft, the tech industry’s original baddie, was accused of having a monopoly on PC software in the 1990s, a landmark case that simmered into a settlement in 2001. The European Union also forced Microsoft to open its operating system to competitors and repeatedly fined it. But an industrywide reckoning that the hearing represents is uncharted territory.

    The hearing is a rare public interrogation of Big Tech’s most important leaders at a crucial time. The US presidential election looms, the country is struggling with social upheaval over racial injustice and the world is staring down a deadly contagion. All the while, Americans are using tech’s services and devices to find information online, buy supplies, and download and stream entertainment while they shelter in place.

    “They all control dominant platforms,” said Hal Singer, a senior scholar at the George Washington Institute of Public Policy, referring to the companies. “This is a good opportunity to get them all together and see if any patterns emerge.”

    Separate battles

    Each of the four companies is facing its own antitrust battle. All of them are reportedly targets of probes by the Department of Justice or a coalition of state attorneys general. Google and Facebook have confirmed various investigations, while Amazon and Apple haven’t publicly acknowledged them.

    With Facebook, which was originally scheduled to report second-quarter earnings on Wednesday but moved them to Thursday, regulators are looking into the company’s acquisitions of competitors like Instagram and WhatsApp. For Amazon, Congress has largely focused on the company’s private-label business, which sells Amazon brands of clothing, food and consumer goods like batteries and diapers. Apple has seen scrutiny over the cut it takes from software developers on its app store. For Google, regulators are focused mainly on the search giant’s dominance in digital advertising.

    At Wednesday’s hearing, all those disparate threads will intersect like a very wonky and nerdy crossover episode. Republicans have also called for Twitter CEO Jack Dorsey to join the hearing, in the wake of a massive security breach earlier this month. Dorsey isn’t on the witness list.

    Adding to the intrigue is the newbie status of Bezos. Zuckerberg, Pichai and Cook have all testified before. (Zuckerberg, the youngest of the bunch, has the most experience testifying on Capitol Hill. In 2018, he fielded questions during two sessions, for almost 10 hours over two days, after the Cambridge Analytica data scandal. He also testified last year about Facebook’s planned Libra cryptocurrency.)

    Despite his rising profile — and wealth — Bezos has never faced Congress. Last Monday, the fortune of the world’s richest person grew by $13 billion in one day alone, bringing his total net worth to almost $190 billion.

    Bezos may have an uncomfortable day. President Donald Trump has taken personal shots at the Amazon boss, apparently over coverage by The Washington Post, which Bezos owns separately from Amazon. It’s likely Republicans allied with the president will pick up the baton and run with it. But there are also legitimate questions to ask about Amazon’s size and business practices.

    A virtual affair

    All high-profile congressional hearings are in part political theater, filled with pageantry and spectacle. When Zuckerberg testified before Congress two years ago, an activist group set up 100 cardboard cutouts of Facebook’s CEO on the lawn of the Capitol Building, imploring him to “Fix Fakebook.” Protestors dressed as bunnies and superheroes chanted slogans like “Zuckerberg, you’re absurd!” After he sat down for his first hearing, photographers snapped pictures of him for nearly a full minute before the proceedings could continue.

    On Wednesday, the circus won’t be following the young mogul. The event will be conducted virtually, an accommodation to House rules because of the coronavirus pandemic. That means the hearing will lack the drama that comes with in-person visits to D.C. Cutting exchanges, like Rep. Katie Porter’s needling of Zuckerberg over his hairstyle last year, are unlikely to play out. Snappy timing is hard to perfect over Zoom.

    Some observers have criticized the format of the forum. Having all four CEOs appear at once means they each get a fraction of the time in the hot seat. The attention would be more focused if each testified individually.

    The hearing may be more show than substance. The real developments will come later. A landmark case against Google is expected to be filed this summer. Facebook awaits the findings of several probes, including one by the Federal Trade Commission. So the hearing is unlikely to be a game-changer, even if it will give the CEOs an opportunity to defend their companies in public.

    People watching the hearing should lower their expectations, says David Balto, a former lawyer in the Justice Department’s antitrust division whose clients include tech companies. There is only so much lawmakers can accomplish in these settings, he says, and Congress should focus on trying to get a public commitment from the companies to reform their competition practices. That would mean, for example, getting Zuckerberg to commit against big acquisitions that “consolidate” the industry, like its buyout of Instagram.

    “The hearing is tremendously significant,” Balto said. But “be ready for disappointment,” he adds, if you’re looking for big changes.
    下载开源日报APP:https://opensourcedaily.org/2579/
    加入我们:https://opensourcedaily.org/about/join/
    关注我们:https://opensourcedaily.org/about/love/
  • 开源日报第847期:《字符串:变成链接 autolink-js》

    28 7 月, 2020
    开源日报 每天推荐一个 GitHub 优质开源项目和一篇精选英文科技或编程文章原文,坚持阅读《开源日报》,保持每日学习的好习惯。
    今日推荐开源项目:《字符串:变成链接 autolink-js》
    今日推荐英文原文:《Why you should have the discussions even if you’re right》

    今日推荐开源项目:《字符串:变成链接 autolink-js》传送门:项目链接
    推荐理由:这个项目是用于一个看似很小的需求——对字符串中的链接进行修改使其变为一个 HTML 的链接标签。要想自己实现的话并非那么简单,所以作者单独把这个功能写成一个库,并为其加上了一些附加要素,诸如为标签提供不同的属性,或是允许开发者自己传入回调函数实现自定义转换功能等等。
    今日推荐英文原文:《Why you should have the discussions even if you’re right》作者:Ken De La Guera
    原文链接:https://towardsdatascience.com/why-you-should-have-the-discussions-even-if-youre-right-31a875015483
    推荐理由:与团队成员交流不仅是为了解决自己的问题,也是为了解决其他人的疑惑

    Why you should have the discussions even if you’re right

    We engineers can be an interesting lot. Due to the nature of our jobs, we are wired to think a certain way. Engineers are essentially told “I want you to get from point A to point B”. No roads, rivers, or anything exists between the two points. Maybe you’ll build a road, maybe you’ll build a rocket, or maybe trebuchets are back in style. It is up to the engineer to decide how to get there.

    This type of ask is typical and results in very analytical minds. This same mentality can also make it difficult to work with other engineers. Everyone has an idea of how to best do things, and it isn’t always easy to come to an agreement.

    If you have never read “Programming Sucks”, I highly recommend you read it. The article illustrates the dichotomy I am talking about in a comical way. Here is an excerpt:
    • Tom and Harry have been working together for years, but have an ongoing feud over whether to use metric or imperial measurements, and it’s become a case of “whoever got to that part of the design first.”
    This is funny and seems like a joke but it actually happens in real life.

    Engineers are by necessity very opinionated and generally know how they want to tackle a problem before they even start writing code. Collaboration by extension then becomes very difficult.

    I think learning how to collaborate is one of the hardest things to learn to do well, especially in the tech field. If you learn how to do this, you will be wildly successful, and here is why.

    Collaboration allows you to make sure that your plan is bullet proof and accounts for everything needed. Even if it turns out the original plan was solid, it still provides the confirmation, disseminates the information, and also provides a potential learning opportunity for collaborators.

    If I could, I would copy and paste those last two sentences 10 times, and call the article done. This is because there is a lot in those sentences that I think we should always keep in mind. Collaborating:
    • Ensures the solution provided adequately meets all requirements/hurdles.
    • Disseminates the information to the team.
    • As team members ask questions and you are able to answer them, it helps them understand and grow.
    Here are some other benefits that were not explicitly listed:
    • Improves your communication skills since you are having to pitch this idea to the team and then intelligently address any concerns that are brought up.
    • By extension from the previous point, collaborating also makes you more knowledgeable. There is a knowledge gap between knowing enough to do something, and knowing enough to speak about it.
    • Helps to increase the adoption of patterns. Check out the linked article for a more in-depth explanation. Establishing problems means you are not only fixing today’s issue, but tomorrow’s as well.

    Conclusion

    I wanted to expand on some of the points above. Among other things, talk about peer reviews and how it leads to less bugs and more maintainable code. I am intentionally cutting this article short so that hopefully the message above is not watered down or lost in the process of a long read.

    Collaboration allows you to make sure that your plan is bullet proof and accounts for everything needed (no one is perfect). Even if it turns out the original plan was solid, it still provides the confirmation, disseminates the information, and also provides a potential learning opportunity for collaborators. All of the above makes you a better engineer, makes for a more efficient team, and makes work more enjoyable.
    下载开源日报APP:https://opensourcedaily.org/2579/
    加入我们:https://opensourcedaily.org/about/join/
    关注我们:https://opensourcedaily.org/about/love/
←上一页
1 … 46 47 48 49 50 … 262
下一页→

Proudly powered by WordPress