开源日报 - Page 103 of 262

开源日报第630期：《ImportExcel》

5 12 月, 2019

原文链接：https://www.theverge.com/2019/11/26/20984328/twitter-removing-inactive-accounts-usernames-available-date
推荐理由：推特是全球著名的互联网公司，也是全球网络舆论总阵地的动向，代表了社交平台的变换趋势。
Twitter will remove inactive accounts and free up usernames in December
Twitter is sending out emails to owners of inactive accounts with a warning: sign in by December 11th, or your account will be history and its username will be up for grabs again. Any account that hasn’t signed in for more than six months will receive the email alert.

“As part of our commitment to serve the public conversation, we’re working to clean up inactive accounts to present more accurate, credible information people can trust across Twitter. Part of this effort is encouraging people to actively log-in and use Twitter when they register an account, as stated in our inactive accounts policy,” a spokesperson told The Verge by email. “We have begun proactive outreach to many accounts who have not logged into Twitter in over six months to inform them that their accounts may be permanently removed due to prolonged inactivity.”

Twitter hasn’t yet said exactly when recouped usernames will be made available to existing users. The account removal process “will happen over many months — not just on a single day,” according to the spokesperson. So don’t expect some massive username rush to happen on December 12th. It might be awhile.

This doesn’t just affect people who’ve abandoned Twitter; it also stands to have an enormous impact on accounts belonging to the deceased. The Verge has asked Twitter whether those will also be pulled into the inactive pool and ultimately removed as part of this process. “We do not currently have a way to memorialize someone’s Twitter account once they have passed on, but the team is thinking about ways to do this,” the spokesperson said.

This might be your best chance to preserve tweets from deceased loved ones If you’ve set up a bot or another secondary account, you should be safe as long as it’s stayed active. The BBC’s Dave Lee reported on the username cleanup. It’s not unusual for huge online platforms to do this from time to time. Yahoo launched an “account recycling” effort in 2013, though some people who grabbed inactive usernames wound up receiving email intended for the old account holder.

Keep in mind that these accounts don’t have to actually tweet anything to stick around. They just have to log in and follow Twitter’s instructions. So even if the username you want seems long dormant based on activity, whoever owns it can still hold on to the username pretty easily.

Also, usernames with under five characters can no longer be registered on Twitter, so that’s another thing to consider when dreaming about switching to that username you’ve always wanted. The username some other fool is failing to put to good use.

The email being sent out has a subject line of “Don’t lose access to @(username).” Here’s what it says:

Hello,

To continue using Twitter, you’ll need to agree to the current Terms, Privacy Policy, and Cookie Use. This not only lets you make the best decisions about the information that you share with us, it also allows you to keep using your Twitter account. But first, you need to log in and follow the on-screen prompts before Dec. 11, 2019, otherwise your account will be removed from Twitter.
So which username will you be going for? Actually, probably best to keep that to yourself until it’s locked in.

下载开源日报APP：https://opensourcedaily.org/2579/
加入我们：https://opensourcedaily.org/about/join/
关注我们：https://opensourcedaily.org/about/love/
开源日报每天推荐一个 GitHub 优质开源项目和一篇精选英文科技或编程文章原文，坚持阅读《开源日报》，保持每日学习的好习惯。今日推荐开源项目：《ImportExcel》
今日推荐英文原文：《Twitter will remove inactive accounts and free up usernames in December》

今日推荐开源项目：《ImportExcel》传送门：GitHub链接
推荐理由：Excel 作为 Office三件套中的一员，强大的功能使其拥有很高的出场率。通过此 PowerShell 模块，您可以读写 Excel 文件，而无需在系统上安装 Microsoft Excel 。无需麻烦的 Excel COM 对象。创建表格，数据透视表，图表等等变得更加容易。
今日推荐英文原文：《Twitter will remove inactive accounts and free up usernames in December》
原文链接：https://www.theverge.com/2019/11/26/20984328/twitter-removing-inactive-accounts-usernames-available-date
推荐理由：推特是全球著名的互联网公司，也是全球网络舆论总阵地的动向，代表了社交平台的变换趋势。
Twitter will remove inactive accounts and free up usernames in December
Twitter is sending out emails to owners of inactive accounts with a warning: sign in by December 11th, or your account will be history and its username will be up for grabs again. Any account that hasn’t signed in for more than six months will receive the email alert.

“As part of our commitment to serve the public conversation, we’re working to clean up inactive accounts to present more accurate, credible information people can trust across Twitter. Part of this effort is encouraging people to actively log-in and use Twitter when they register an account, as stated in our inactive accounts policy,” a spokesperson told The Verge by email. “We have begun proactive outreach to many accounts who have not logged into Twitter in over six months to inform them that their accounts may be permanently removed due to prolonged inactivity.”

Twitter hasn’t yet said exactly when recouped usernames will be made available to existing users. The account removal process “will happen over many months — not just on a single day,” according to the spokesperson. So don’t expect some massive username rush to happen on December 12th. It might be awhile.

This doesn’t just affect people who’ve abandoned Twitter; it also stands to have an enormous impact on accounts belonging to the deceased. The Verge has asked Twitter whether those will also be pulled into the inactive pool and ultimately removed as part of this process. “We do not currently have a way to memorialize someone’s Twitter account once they have passed on, but the team is thinking about ways to do this,” the spokesperson said.

This might be your best chance to preserve tweets from deceased loved ones If you’ve set up a bot or another secondary account, you should be safe as long as it’s stayed active. The BBC’s Dave Lee reported on the username cleanup. It’s not unusual for huge online platforms to do this from time to time. Yahoo launched an “account recycling” effort in 2013, though some people who grabbed inactive usernames wound up receiving email intended for the old account holder.

Keep in mind that these accounts don’t have to actually tweet anything to stick around. They just have to log in and follow Twitter’s instructions. So even if the username you want seems long dormant based on activity, whoever owns it can still hold on to the username pretty easily.

Also, usernames with under five characters can no longer be registered on Twitter, so that’s another thing to consider when dreaming about switching to that username you’ve always wanted. The username some other fool is failing to put to good use.

The email being sent out has a subject line of “Don’t lose access to @(username).” Here’s what it says:

Hello,

To continue using Twitter, you’ll need to agree to the current Terms, Privacy Policy, and Cookie Use. This not only lets you make the best decisions about the information that you share with us, it also allows you to keep using your Twitter account. But first, you need to log in and follow the on-screen prompts before Dec. 11, 2019, otherwise your account will be removed from Twitter.
So which username will you be going for? Actually, probably best to keep that to yourself until it’s locked in.

下载开源日报APP：https://opensourcedaily.org/2579/
加入我们：https://opensourcedaily.org/about/join/
关注我们：https://opensourcedaily.org/about/love/
开源日报第629期：《独立博客 chinese-independent-blogs》

4 12 月, 2019
开源日报每天推荐一个 GitHub 优质开源项目和一篇精选英文科技或编程文章原文，坚持阅读《开源日报》，保持每日学习的好习惯。
今日推荐开源项目：《独立博客 chinese-independent-blogs》
今日推荐英文原文：《A Beginner’s Guide to SQL Injection》

今日推荐开源项目：《独立博客 chinese-independent-blogs》传送门：GitHub链接
推荐理由：我们都曾从别人的博客中汲取知识，也可能自己写过博客帮上过别人。这个项目是中国独立博客的列表，也就是有独立域名和独立内容的博客。虽然博客比起各种平台来说阅读量少上很多，但是写博客本身应该是自己的事情，既然如此，一切都归于自己管理之下才是博客比起平台来说最大的好处。而这个项目正希望能够让这些博客被更多人发现，从而帮上更多人的忙。
今日推荐英文原文：《A Beginner’s Guide to SQL Injection》作者：Ashwin Goel
原文链接：https://medium.com/better-programming/a-beginners-guide-to-sql-injection-163c1ad2257f
推荐理由：如果没有好好对策的话，正面接一下可不是闹着玩的
A Beginner’s Guide to SQL Injection

What is it and how can we protect our code from hackers and bad actors?
SQL injection is a web security vulnerability that allows an attacker to alter the SQL queries made to the database. This can be used to retrieve some sensitive information, like database structure, tables, columns, and their underlying data.

For example, suppose an application uses the following query to fetch someone’s login details:
```
SELECT USERNAME,PASSWORD from USERS where USERNAME='<username>' AND PASSWORD='<password>';
```
Here, username and password is the input provided by the user. Suppose an attacker gives the input as ‘ OR ‘1’=’1 in both fields. Therefore, the SQL query will look like:
```
SELECT USERNAME,PASSWORD from USERS where USERNAME='' OR '1'='1' AND PASSWORD='' OR '1'='1';
```
This query results in a true statement, and thus, the user gets logged in. This example depicts the most basic type of SQL injection.

SQL injection can be used anywhere to fetch any sensitive information from the database.

Note: This was the most basic example and meant only for understanding purposes. You’ll mostly not find any such cases in the real world.

You can use this cheat sheet to see how to make queries over different SQL database providers.
How to Detect the Presence of SQL Injection?
In most cases, SQL injection can be detected easily by providing invalid parameters, like ‘, ” a’ or 1=1–, “a”” or 1=1–“, or a = a, a’ waitfor delay ‘0:0:10’–, 1 waitfor delay ‘0:0:10’–, %26, ‘ or username like ‘%, and etc. You can then observe the changes in the behavior of the application.

You may try to analyze the length of the response from the server and also the time it takes to send the response. Payloads like ‘, a’ or 1=1–, and etc. might show changes in the response by the database server. But if there’s no change, then we try to trigger time delays using a payload like a’ waitfor delay ‘0:0:10’–. This might make the server delay for a specific time before sending a response.

After determining if the website is vulnerable to SQL Injection, we can try to extract some sensitive information from the database.

Before that, we need to identify the number of columns the SQL Query returns. This is essential because if we try to extract an unequal number of columns than what the query actually returns, then it will return an error.

We can determine the number of columns by using the order by command. For example:
```
www.onlineshopping.com/products.php?pid=8 order by 1

www.onlineshopping.com/products.php?pid=8 order by 2 // If the parameter is a string then you need to add ' after 

it.www.onlineshopping.com/products.php?usr=b order by 3

www.onlineshopping.com/products.php?usr=a order by 4
```
The significance of — is that it’s a comment indicator in SQL, which makes the rest of the query a comment. Now to preserve the space after –, we add any character after that so that space doesn’t get ignored in the HTTP request. We might also use # or /* */ for comments depending on the SQL database provider.

Continue this process until you encounter an error. If you encounter an error while using the payload order by 5 but not while using order by 4, this means that the query returns 4 columns.
How to Exploit Using SQL Injection
Once you know that the application is vulnerable to SQL injection and you have identified the number of columns, we try to find necessary information about the database, like DB name, DB user name, DB version, table names, column names of the required table, and etc. Check out the SQL injection cheat sheet to find the respective queries.
Types of SQL Injection
- Error-based: This type of SQL injection relies on the error messages being thrown by the database server, which might provide us some useful information regarding the database structure.
- Union-based: This technique uses the SQL UNION operator to combine the results of two SELECT queries and return a single table. It allows an attacker to extract information from other tables by appending the results to the original query made to the database.
- Blind Injection: This happens when the application is vulnerable to SQL Injection but the results of the SQL query are not returned in the HTTP response. In this case, we query the database for any true/false statement and see the changes for both true and false conditions. It is of two types:
- Content-based: In this technique, the database server is queried with any conditional statement and the response from the server is analyzed for any difference while sending a true condition and a false condition.
- Time-based: This technique relies on injecting an SQL query that makes the database wait for a specific time based on the specified condition. The time taken by the server to send back a response determines if the query is true/false.
- Out-of-band injection(uncommon): This is not a very common type of SQL Injection as it depends on the features being enabled on the database server. It relies on the database server’s capability to make a web request like HTTP, DNS, andftp to send data to the attacker.
How to protect your code from SQL Injection?
- Never construct a query directly with the user’s input. Instead, use Parameterized Statements. They make sure that the inputs passed into SQL queries are treated safely.
- It’s always good the sanitize the user input. Also, proper input validation should be done for example, a name can’t be digits or a phone number can’t be alphabets. However, this can be bypassed at times.
- Use a safe driver to interact with your SQL Database. They automatically prevent against all SQL Injection attacks. For example, SQLAlchemy for python.
下载开源日报APP：https://opensourcedaily.org/2579/
加入我们：https://opensourcedaily.org/about/join/
关注我们：https://opensourcedaily.org/about/love/
开源日报第628期：《简易版本 project-x》

3 12 月, 2019
开源日报每天推荐一个 GitHub 优质开源项目和一篇精选英文科技或编程文章原文，坚持阅读《开源日报》，保持每日学习的好习惯。
今日推荐开源项目：《简易版本 project-x》
今日推荐英文原文：《A Framework for Overcoming Tough Bugs Without Pulling Your Hair Out》

今日推荐开源项目：《简易版本 project-x》传送门：GitHub链接
推荐理由：React 和 Vue 这样的流行框架上都有在组件内保存数据后根据数据操作的功能，毕竟这玩意可是相当好用的。这个项目把流行框架上的这些功能借了过来，在你只需要这些而不需要更多功能的时候可以使用。语法方面使用了 Vue 里常见的 bind 等，而功能则包括常见的数据保存，属性设定和事件监听等这方面常用的功能，虽然是直接在 html 里使用的语法，太过于复杂会损失易读性，但是在一些小项目里不需要杀鸡用牛刀的时候可以尝试。
今日推荐英文原文：《A Framework for Overcoming Tough Bugs Without Pulling Your Hair Out》作者：Chris Geelhoed
原文链接：https://medium.com/better-programming/a-framework-for-overcoming-tough-bugs-without-pulling-your-hair-out-8da3e376c5bc
推荐理由：在调试代码过程中的小建议
A Framework for Overcoming Tough Bugs Without Pulling Your Hair Out

8 tips for breaking through roadblocks as a programmer
Programming is hard. The ability to translate an idea into code isn’t something that comes naturally to most people, and sometimes we get stuck.

Even after coding for years, you will still hit roadblocks regularly. Computer programming is an incredibly deep field, and it just isn’t possible to master everything about it.

Plus, we all have bad days sometimes.

Maybe you can’t fix a stubborn JavaScript error, or you can’t explain why your website looks completely broken in Internet Explorer, or maybe you can’t even start your development server.

Software can break in an almost unlimited number of ways, and it often does. Murphy’s law.

Setbacks in coding can’t be avoided, but they can be handled gracefully. Here are eight tips that will help you debug your code as painlessly as possible:
- Take care of yourself first.
- Use the tools that are available to you.
- Speed up your debugging cycle.
- Ask for help.
- Look at the obvious stuff first.
- Read your error messages.
- Think about what changed last.
- Take time to reflect on what you’ve learned before moving on.
1. Take Care of Yourself First
Even if you spend most of your day looking at a computer screen, you are still a human being, and it’s difficult to think clearly when you’re tired, hungry, or otherwise uncomfortable.

Try to keep tabs on yourself when you are coding. If you suddenly find that you are hitting a wall, think about what might be off. Have you gone without a break for a long period of time? Are you in an environment that makes it hard to concentrate? Did that third cup of coffee give you the jitters?

Pay attention to yourself and look for patterns like these. Small details could have a surprisingly large impact on your productivity.
2. Use the Tools That Are Available to You
Software development has come a long way since the rise of the internet and good tools now exist to make debugging easier.

Take the time to learn about the tools available in your arena. If your focus is on front-end web development, then learn how to use your browser’s built-in development tools. If you write PHP, learn about Xdebug and how breakpoints can be used in your IDE.

Whatever kind of programming you do, explore your ecosystem and try to learn how experts in your area debug their code. This kind of research is sometimes hard to justify when you have deadlines to meet, but it’s an investment in time that will pay itself back tenfold.
3. Speed Up Your Debugging Cycle
Classic programming is essentially a guess-and-check process. Your write some code then check the result. If it works, you move forward. If not, you are now debugging.

The time between writing code and seeing its result should be as short as possible. A quick feedback cycle allows you to iterate quickly and maintain your train of thought.

Do whatever you can to speed up this process. For example, if you are debugging a component that appears at the very bottom of a long page and find yourself scrolling down to it again and again to test your code, move that component to the top temporarily.

If you are writing CSS or JavaScript then take the time to set up hot reloading so that you don’t need to make a hard reload every time you change your code.

Whatever you are doing, try to notice the little steps that you are repeating and think about how they can be eliminated.
4. Ask for Help
Sometimes, you look at something for so long that you get lost in the weeds and lose sight of the bigger picture. This is called tunnel vision, and it is a problem for junior and senior engineers alike.

Instead of spending hours stressing over a problem alone, invite a colleague to look at it with you. It’s amazing what perspective an outside set of eyes can bring to the table.

We all want to be super-devs that can solve every problem alone but this isn’t a realistic goal or expectation.

A better approach is to collaborate with your team and leverage the experience of the people around you. You might be struggling with a problem that the person sitting next to you solved last week.
5. Look at the Obvious Stuff First
Most of the bugs that you encounter as a developer will be obvious, but only in hindsight.

Be self-aware as you explore solutions. Are you making assumptions without verifying them? Are you going down a rabbit hole that could be totally unrelated to your bug?

It’s a good idea to check off the little things first. Some good questions to ask yourself are:
- Did I forget to save?
- Is the code I’m editing even being loaded? If I print “hello world” at the top of my script do I see the output?
- Did I forget to require that module?
- Did I forget to call that function?
- Did I forget to return that value?
- Are things spelled correctly?
I can’t count the number of times I’ve pulled my hair out over a problem that ultimately came down to a simple spelling mistake.
6. Read Your Error Messages
Error messages can be intimidating when you first start coding, but they give you extremely valuable information. Take the time to read them carefully and give yourself a minute to digest them.

If the message gives you the line in the script where the error was thrown, give that line a closer look.

If the message gives you an error code without further explanation, try googling that error code — you might be able to find additional info.

Error messages can look like gibberish at first glance, but they are often the best way of understanding what went wrong. As you gain experience as a developer, they will make more and more sense to you.
7. Think About What Changed Last
This sounds a lot like the “Retrace your last steps” advice that your mom gave you when you lost something as a kid, but it’s important nonetheless.

When your code is working fine one day and suddenly breaks without explanation, you should look for what changed.

Did you upgrade your version of Node.js? Or maybe you switched from Vagrant to Docker. Things that changed recently are much more likely to cause issues than things that have already been working for a long time.

If you are fortunate enough to have the history of the project captured with a version control system like Git, then it might be worthwhile to check out the code from previous commits and see if those versions have the bug you are dealing with.
8. Take Time to Reflect Before Moving On
Fixing a bug comes as such a relief that it’s tempting to just forget about it and move on to the next task, but this is a big mistake!

Take a moment to enjoy your success, but then reflect on the problem that you just solved.

Do you understand how the bug was created in the first place, and how it was fixed? If the answer is no then you might want to dig a little deeper before moving on.

If the bug tripped you up for hours or days, it might even be worthwhile to document it somewhere — either publicly or in your own personal notes.

Write about what the bug was, how you fixed it, and what you learned. Doing this will put you in a much better position to quickly identify and fix similar bugs in the future.
Summary
Stubborn bugs are probably the worst part of programming. They aggravate us, waste our time, and sometimes make us feel like imposters.

When you find yourself in a battle with a bug, take a moment to acknowledge that this happens to everyone and then think back to the tips mentioned in this article.

They won’t give you the answer, but they will give you a solid foundation to work from and a good place to start.
下载开源日报APP：https://opensourcedaily.org/2579/
加入我们：https://opensourcedaily.org/about/join/
关注我们：https://opensourcedaily.org/about/love/
开源日报第627期：《手绘风 roughViz》

2 12 月, 2019
开源日报每天推荐一个 GitHub 优质开源项目和一篇精选英文科技或编程文章原文，坚持阅读《开源日报》，保持每日学习的好习惯。
今日推荐开源项目：《手绘风 roughViz》
今日推荐英文原文：《How to Be a Rock Star Developer.》

今日推荐开源项目：《手绘风 roughViz》传送门：GitHub链接
推荐理由：一个普通的统计图表看着实在太普通了，兴许应该换换花样了，这个项目是一个 JS 图表库，顾名思义可以画图表——只不过画出的图表是手绘风格的。虽然说是手绘风格，要是正儿八经的来画倒也能和普通的统计图表一样容易看懂，但是这个项目可以修改显示的样式，从而让图表更加……具有独特的个性。

今日推荐英文原文：《How to Be a Rock Star Developer.》作者：Ravi Shankar Rajan
原文链接：https://medium.com/swlh/how-to-be-a-rock-star-developer-4c7b0d17a9a0
推荐理由：成为像摇滚明星一样帅气，或者应该说，强势的开发者
How to Be a Rock Star Developer.

Be essential, not indispensable.

Image Credits : Pixabay.com

Ask anybody to describe a rock star developer and you will get a myriad list of definitions.
- They solve every problem quickly
- They are deadline beaters
- Their code is virtually bug-free
- They love taking challenges which are unsolvable
- They are the backbone of the project. Nothing works without them.
And so on…….

So far so good. But that brings us to another question.

Do rock stars remain rock stars forever? Why do we often see situations when developers start as rock stars and end up being mediocre? What brings their downfall?

The short answer is indispensability.

Their downfall starts from the day they start becoming indispensable to the project. Work starts revolving around them and sooner or later they end up getting sucked into work from all sides. No meeting starts without them. No solution is complete unless vetted by them. They cannot go on vacation as nobody is there to cover for them. And the other developers get so accustomed to The Rockstar handling difficult problems that they become lazy and complacent.

The result? The rock star loses his creativity. He gets burned out. His work degenerates and becomes scrappier by the day and one day he quits. The project suffers. The team suffers and the company suffers for putting all the eggs in one basket. The rock star developer also, often never recovers from the burnout scars and becomes a mediocre developer who does his work assigned to him, nothing more.

The lesson here is becoming essential and not indispensable.

An essential developer focuses on the work to be done but keeps himself out of the picture. Their goal is to help others help themselves so that they can free their time for bigger things.

An indispensable developer, on the other hand, monopolizes all the work and hurts himself and the team in the long run. The essential developer creates a team of rock stars and the indispensable developer leaves behind a motley of ignorant and incompetent fools.

And real rock star developers leave behind a 10 X times more effective team rather than focusing on being 20 X times better than the rest of the team.

Here are some ways to be a real rock star developer.
Be a Linchpin.
Seth Godin in his book Linchpin describes the linchpin as a person who can “invent, lead (regardless of title), connect others, make things happen, and create order out of chaos.” Linchpins are the people who can work with “no rule book,” people who are happy to always make their best effort to transform even mundane tasks into works of art to be cherished.

And as a developer, you can be a linchpin by simply gifting your knowledge. In ancient tribes, those who had the most power, the Kings and Queens and Chiefs were those who gave the most gifts. In the modern world, a developer’s power comes by gifting empowerment to other developers. There can be several simple ways to go about it.
- Be a mentor and groom junior developers
- Write utility codes that can be used by all.
- Create a side initiative project in cutting edge technologies involving other developers.
And so on…

The key here is to give your art for free without expecting any repayment in return. This can be your best ideas, your incredible coding skills or open-sourcing that amazing software you designed.

By empowering the team with the most precious gift you ever gave, you are not only building your own tribe but also fostering diverse creative energies within the team.
Control FOMO-Fear of Missing Out.
Essential developers are eager to explore new opportunities but also very selective in what they choose to do and what they choose not to do.

For example, you want to attend a highly informative course on SAP HANA. But the timings are clashing with a meeting, which you need to attend every day to give a status update. You know precisely that you do not contribute anything to the meeting but people expect you to be present in the meeting. You are popular and don’t want to disappoint anybody but at the same time, you know the meeting is not adding any value to you or to the team.

What will you do? The real fight here is between satisfying your ego versus satisfying your knowledge. Essential developers know that tangible value far outweighs the loss in popularity votes and they select precisely that.

Essential developers do a trade-off between the essential and non-essential every day. They are OK if there is a drop in popularity as their focus is on long term tangible results which benefit all. They believe and advocate the logic that less means more and more = mediocre. More and more is always valueless.

Staying true to your purpose and being selective results in a more meaningful quality of life. Essential developers are not afraid of missing out on the action. Rather they relish the joy of missing out(JOMO) so that they can use the time constructively.

Essential developers focus on the real work, their real results and let the non-essential fall away.
Be an Everyman’s leader.
The essential developer is an everyman’s leader.

He might not have any position or power but he always takes that extra effort to help whoever needs his help. He is an agent of change and quite often developers flock around him rather than around their managers when they are feeling lost or stuck somewhere. He sees you struggle, take five minutes to teach one neat trick and show you that you can do it too. He creates a single point of trust who can be approached by anybody in times of need.

And at crunch times, the everyman’s leader rises to the occasion, help people around them rally and organize, and work cooperatively to resolve the part of the situation they have some influence over. And above all, they do not hoard knowledge as they know knowledge is power only when it is shared. They share their knowledge because they consider that if it’s useful to them, it will be useful to everyone.

That said, the main characteristics of a real rock star developer are the same for almost any field or position: integrity, adaptability, and the desire to do excellent work. And it all comes down to one simple truth; — pour your soul into whatever you do. Represent your brand in such a way that the whole world knows that you own it. You will then be truly a star in the real sense.

As Ice cube has rightly said.
Don’t worry about being a star, worry about doing good work, and all that will come to you.

下载开源日报APP：https://opensourcedaily.org/2579/
加入我们：https://opensourcedaily.org/about/join/
关注我们：https://opensourcedaily.org/about/love/

开源日报第630期：《ImportExcel》

Twitter will remove inactive accounts and free up usernames in December

Twitter will remove inactive accounts and free up usernames in December

开源日报第629期：《独立博客 chinese-independent-blogs》

A Beginner’s Guide to SQL Injection

What is it and how can we protect our code from hackers and bad actors?

How to Detect the Presence of SQL Injection?

How to Exploit Using SQL Injection

Types of SQL Injection

How to protect your code from SQL Injection?

开源日报第628期：《简易版本 project-x》

A Framework for Overcoming Tough Bugs Without Pulling Your Hair Out

8 tips for breaking through roadblocks as a programmer

1. Take Care of Yourself First

2. Use the Tools That Are Available to You

3. Speed Up Your Debugging Cycle

4. Ask for Help

5. Look at the Obvious Stuff First

6. Read Your Error Messages

7. Think About What Changed Last

8. Take Time to Reflect Before Moving On

Summary

开源日报第627期：《手绘风 roughViz》

How to Be a Rock Star Developer.

Be essential, not indispensable.

Be a Linchpin.

Control FOMO-Fear of Missing Out.

Be an Everyman’s leader.