F-Droid and #google's #developer Registration Decree | F-Droid - Free and Open Source #android App Repository
▻https://f-droid.org/2025/09/29/google-developer-registration-decree.html
— Permalink
#playstore #fdroid #apps #store #sideloading #opensource #freedom #software #hardware #smartphones #cybersecurity #monopoly
(1) Open Letter to Satya Nadella, CEO of Microsoft on the Future of GitHub, Trust, and Digital Sovereignty | LinkedIn
▻https://www.linkedin.com/pulse/open-letter-satya-nadella-ceo-microsoft-future-github-dion-wiggins-f2yic
Dion Wiggins
Dion Wiggins
CTO at Omniscien Technologies | Board Member | Strategic Advisor | Consultant | Author
16 août 2025
16 August 2025
Dear Mr. Nadella (Satya Nadella) ,
As a developer of more than 40 years, across 33+ programming languages and even more platforms, I have seen the rise and fall of countless technologies, communities, and ecosystems. While I cannot speak for the global developer community as a whole, it is clear that a very large number of us feel the same deep sense of betrayal and alarm over Microsoft’s actions regarding GitHub. This letter is written not only from decades of professional experience and personal investment, but in solidarity with the thousands of developers, project maintainers, community leaders, and digital sovereignty advocates who have raised these same alarms. The issues are systemic, not individual.
Satya Nadella (2018): “We recognize the responsibility we take on with this agreement. We are committed to being stewards of the GitHub community, which will always remain open to all developers.”
In the above Microsoft Blog post, you promised that “GitHub will operate independently and remain an open platform for all developers,” and committed to “keeping GitHub independent and developer-first.” GitHub leadership assured the world that “GitHub will operate independently… That means GitHub retains its developer-first values, distinctive spirit, and open extensibility.”
Public promises on the Github website at the same time made simpler promises that have now been broken.
Nat Friedman (2018): “GitHub will operate independently… That means GitHub retains its developer-first values, distinctive spirit, and open extensibility.”
While Microsoft continues to highlight its open source credentials and assure developers that “nothing has changed” for users, the core issue is not superficial continuity, but the structural and strategic shift of GitHub from a genuinely independent, community platform to a fully integrated corporate asset. This is not about branding, but about irreversible changes to control, incentives, and accountability.
Microsoft Press Release (2025): “This transition enables us to accelerate GitHub’s contributions to Microsoft’s AI ecosystem.”
Today, those commitments are in question. As TechRadar reports: “Rather than appoint a new GitHub CEO, Microsoft will integrate GitHub more directly into CoreAI, led by Jay Parikh… GitHub will now report directly into its CoreAI division.” (TechRadar)
This reporting is echoed by The Verge, which noted that “Microsoft isn’t replacing Dohmke’s CEO position, and GitHub will be fully part of Microsoft instead of being run as a separate entity.” (The Verge)
These moves directly contradict the 2018 promise of independence and stewardship. They are not continuity but consolidation. For many in the community, this is not simply a broken promise but an outright lie. Your words from the past: “We recognize the responsibility we take on with this agreement. We are committed to being stewards of the GitHub community, which will retain its developer-first ethos, operate independently and remain an open platform”, now stand exposed as empty assurances at best, or an intentional lie at worst.
I repeat these phrases because you have not lived up to them and they seem unimportant to you today. Just a tool of the past, discarded once the acquisition goals were complete.
Microsoft’s decision to absorb GitHub into its CoreAI division, eliminate its independent leadership, and embed it deeply within the company’s AI and cloud business directly contradicts these promises. The official press release states this is to “accelerate GitHub’s contributions to Microsoft’s AI ecosystem.” Microsoft executives openly describe how “GitHub’s vast code corpus is foundational for the next era of Copilot and AI model development.”
This is not just a broken promise. It is an assault on open source itself. A collapse of credibility with the global developer community, and a direct threat to technological self-determination for every contributor, organization, and nation that depends on independent infrastructure.
Here is just a small sample of the many negative reactions to this announcement. These articles show a clear consensus across reputable tech publications: GitHub’s absorption into CoreAI is widely seen as a major structural shift, and for many, a direct betrayal of its once independent and developer-first identity:
The Verge – “GitHub just got less independent at Microsoft after CEO resignation”
Discusses how GitHub’s autonomy ends as leadership shifts under Microsoft’s CoreAI structure, posing a clear signal of deeper absorption. (The Verge)
TechRadar – “GitHub CEO resigns – is this the latest sign of its Microsoft absorption?”
Highlights the absence of a successor and emphasizes the strategic assimilation into Microsoft’s AI ecosystem. (TechRadar)
IT Pro – “What Thomas Dohmke’s departure means for GitHub”
Analyzes how the CEO’s exit signals major governance changes and closer alignment with Microsoft’s AI strategy. (IT Pro)
Windows Central – “GitHub Just Got Assimilated—CEO Out, Copilot In, Microsoft All Over It”
Signposts the end of GitHub’s independence and elevated priority of AI within Microsoft’s internal structure. (Windows Central)
Tom’s Hardware – “GitHub folds into Microsoft following CEO resignation—once independent programming site now part of ‘CoreAI’ team”
Explicitly frames the move as ending GitHub’s independence and compares it to other Microsoft acquisitions that lost identity over time. (Tom’s Hardware)
The Collapse of Trust: Big Tech’s Greed, Digital Sovereignty, and Its Consequences
Trust is the foundation of every open source project, community, and movement. Open source cannot function without the assumption that platforms and stewards act in good faith, respect contributors, and put the long-term health of the ecosystem ahead of short-term profit.
The breakdown of trust caused by the actions of Microsoft and other Big Tech firms is more than a single betrayal. It signals to the entire world that the social contract underpinning open source and digital agency can be bought, sold, and quietly rewritten by whoever controls the infrastructure.
It is disingenuous to claim that developers are “free to leave” when practical migration is obstructed by technical and network effects, and when so much of the world’s open source and digital sovereignty ecosystem is already tied into GitHub’s infrastructure. Genuine freedom requires open exit, true interoperability, and transparent guarantees. None of these can exist in an environment of creeping lock-in and vertical integration.
When companies that present themselves as stewards of community assets choose instead to exploit those assets for proprietary gain, they undermine not just their own credibility, but the very possibility of global cooperation in technology. Each time a platform is captured, centralized, or redirected to serve corporate interests, it pushes developers and innovators away from openness and into silos of mistrust and fragmentation.
No security, compliance, or anti-abuse argument can justify stripping developers, organizations, and nations of their digital sovereignty, or transferring unilateral control over critical digital assets to a single commercial actor. Security and compliance can and must be implemented in ways that preserve agency, transparency, and open governance.
Digital sovereignty is not a slogan. It is a core policy objective of governments, regulatory agencies, and open source communities worldwide, with documented legal frameworks and active enforcement across the EU, China, India, and many others. The concerns raised here are not hypothetical or parochial. They are echoed by policymakers, technologists, and civil society leaders globally.
This is not an isolated incident. The industry has seen similar betrayals before: Oracle’s handling of Java, Google’s abrupt shutdown of Google Code, and previous pivots by Microsoft itself. Each time, the developer community paid the price: wasted effort, lost code, broken commitments, and a new wave of skepticism toward platform promises.
The long-term impact is already visible:
Developers are increasingly hesitant to share their best work on public platforms for fear it will be extracted, repackaged, and monetized by corporate actors without consent or fair return.
Communities fracture, as trust erodes and contributors seek alternative venues or attempt to rebuild trusted enclaves outside Big Tech’s reach.
Innovation slows, as the collaborative advantage of open source is replaced by guarded, siloed development and legal maneuvering to prevent exploitation.
Governments and institutions start to question whether global digital infrastructure can be trusted at all, leading to regulatory walls, data localization, and a new era of digital sovereignty where nations must assert control over their technology dependencies to protect their agency and interests.
This is not just about code or business models. It is about the collective investment of millions of developers worldwide—years of unpaid, voluntary, and mission-driven work that made GitHub the backbone of modern software. That trust, once lost, cannot be restored by marketing or legal boilerplate. It is about digital agency and the fundamental right to control one’s own digital assets, collaborations, and infrastructure choices without the threat of unilateral interference, commercial extraction, or external lock-in.
Big Tech’s willingness to break trust for short-term advantage is sowing the seeds for a world where the promise of open, global collaboration and shared digital sovereignty is replaced by suspicion, legal battles, and technical walls. The more platforms like GitHub are captured and redirected for private enrichment, the less likely it is that the next generation of developers, communities, or nations will believe in or participate in open source at all.
Without trust, open source collapses. Without sovereignty, collaboration corrodes. And once credibility is gone, it is almost impossible to rebuild.
The world is watching, not your assurances, but your actions.
These concerns are not academic or hypothetical. They reflect the real and growing alarm expressed by thousands of developers, project leaders, digital sovereignty advocates, and policymakers worldwide. Digital sovereignty is not a slogan, but a legal and strategic reality, shaping government, enterprise, and technical policy from the European Union to Asia and the Global South. No reassurances, PR statements, or cherry-picked open source releases can substitute for the specific, transparent, and enforceable commitments demanded here. The complexity and length of this letter are necessary because the stakes—for global innovation, autonomy, and trust—could not be higher.
The following questions must be answered directly, with transparency, not PR spin. This is about the survival of open source as a trusted, collaborative foundation for global innovation, and about the preservation of digital sovereignty and agency for everyone who relies on these platforms.
1. Do you acknowledge that folding GitHub into Microsoft’s CoreAI division and revoking its independence directly contradicts your explicit public commitments to keep GitHub open and independent? If not, what specific facts justify your claim that these moves are not a corporate takeover and betrayal?
Microsoft pledged that GitHub would remain independent, open, and developer-first. Integrating GitHub into CoreAI, eliminating operational independence, and repurposing it as a pipeline for Microsoft’s AI ambitions is the very definition of a corporate takeover.
2. What concrete, legally binding measures will you implement, beyond policy statements, to guarantee that GitHub will never be used as a captive data source for Microsoft’s proprietary AI models or to lock developers and organizations into your ecosystem, undermining their digital sovereignty and agency?
The world sees this as a strip and extract operation: first mining community content, then enclosing it, and finally locking developers, communities, and entire organizations into Microsoft’s ecosystem, which is the opposite of open source and sovereign control.
3. What immediate, auditable steps will Microsoft take to repair the breach of trust with developers and platform stakeholders—including independent oversight and enforceable guarantees—to prove that GitHub will not be exploited for Microsoft’s commercial gain or to undermine the digital sovereignty of its users?
Repeated public promises were made that GitHub would retain its developer-first values and open extensibility. The loss of trust is not just about business decisions—it is about whether open source contributors, organizations, and governments can ever again believe in the commitments of those who control their code, collaboration, and infrastructure.
4. Will Microsoft commit, by enforceable policy and public documentation, that no public GitHub repositories will be used for training proprietary AI models or commercial products without explicit opt-in consent from project owners, thus protecting the digital agency and autonomy of all contributors?
Developers globally are concerned that their open source contributions are being silently harvested for commercial AI without consent, attribution, or compensation.
5. Will Microsoft provide developers and organizations with granular, real-time tools to track and control every instance where their code or metadata is accessed, processed, or used for AI or commercial purposes, along with a public log of such activity—empowering all users to exercise digital agency over their work and assets?
Developers have a right to track and control use of their code in AI and data pipelines. Sovereign organizations and communities have an equal right to transparent control over their assets and digital infrastructure.
6. Will Microsoft legally guarantee that all GitHub users retain unrestricted rights and technical means to export or migrate their code, data, and issue history at any time, without penalty or delay, and that no feature or license changes will restrict this freedom or diminish their digital sovereignty?
The health of the open source ecosystem depends on freedom of movement, agency, and interoperability—not closed integration with any vendor’s stack or barriers that undermine organizational or national self-determination.
7. Will Microsoft commit, by contract and technology, to never implement, enable, or cooperate in any form of kill switch, access denial, or politically motivated censorship affecting GitHub projects, regardless of pressure from governments or commercial interests—thus respecting the digital sovereignty and agency of all users worldwide?
Centralization amplifies the risk of politically or commercially motivated interference in developer access, especially during periods of geopolitical tension. Digital sovereignty means ensuring no single entity can unilaterally block, censor, or deny access to critical digital assets.
8. Will Microsoft agree to continuous, binding, independent audits of GitHub’s operations, with real enforcement power and board representation for open source foundations such as the Linux Foundation, FSF, or OSI, to safeguard the sovereignty and agency of the broader community?
A platform of GitHub’s global importance cannot be accountable only to its corporate owner. Recognized foundations must be invited to participate in this oversight. No internal Microsoft committee or advisory board can substitute for independent, enforceable, foundation-driven oversight with real transparency, developer representation, and binding authority. Only governance with teeth can rebuild trust and protect digital agency.
9. Will Microsoft publish a full, advance public record of all technical, legal, and policy changes that affect GitHub’s integration with Microsoft’s AI and cloud infrastructure, including any changes to data access, contributor rights, or project governance—providing all stakeholders with the information they need to protect their digital sovereignty and agency?
Developers, organizations, and governments need to understand the real scope of integration, dependencies, and any hidden impacts on autonomy, sovereignty, or compliance.
10. Will Microsoft publicly accept binding legal and financial liability, including retroactive remedies, if any use of GitHub code, data, or metadata for AI or commercial purposes is found to violate open source licenses, contributor agreements, relevant law, or the digital rights and sovereignty of its users?
The risk of legal and ethical breach is not theoretical—it is a live issue globally. This letter calls for binding, publicly auditable commitments, not ambiguous legalese, policy footnotes, or unenforceable pledges. The stakes demand real-world, transparent, and contractually enforceable action.
Specific Remedies the Community Expects
To ensure that trust is restored and preserved, and to provide the minimum foundation for moving forward in a world where digital sovereignty and agency matter, the following concrete remedies should be enacted:
Restore an independent GitHub CEO and governance board, separate from Microsoft’s AI, cloud, and product divisions, with real authority and transparency to protect community interests and platform autonomy.
Publish and enforce a clear, public data use and extraction policy for AI and all other Microsoft product development, including explicit opt-in or opt-out for project owners regarding code, metadata, and issue data, respecting the digital sovereignty of every contributor and community.
Submit to regular, external audits by recognized organizations such as the Linux Foundation, Free Software Foundation, or Open Source Initiative, with findings published in full to ensure accountability and agency for all stakeholders.
Contractually guarantee migration and export rights for all repositories and developer data, ensuring there are no technical, legal, or policy barriers to leaving the platform, thus safeguarding the freedom and digital sovereignty of every user.
Publish quarterly transparency reports detailing code access, AI extraction activity, and all data-sharing between GitHub and Microsoft’s internal systems, giving all users the visibility needed to maintain their own agency and control.
Pointing to isolated positive actions or PR initiatives does not address the irreversible structural shift underway, nor does it remedy the breach of trust caused by consolidating platform power without transparent, community-backed guarantees.
What happens next matters. If these concerns are not addressed openly and concretely, many developers, projects, organizations, and even governments will have to reconsider their continued trust in GitHub’s stewardship and Microsoft’s commitments to open source and digital sovereignty. Major voices in the community are already calling for alternatives and greater scrutiny of platform governance. I encourage other developers, open source advocates, digital sovereignty experts, and independent observers to follow this issue closely and demand real accountability for the future of digital collaboration and autonomous control.
I invite Microsoft, and you personally, to respond to these questions in a public forum or published statement so the entire developer and digital sovereignty community can judge for themselves whether these concerns will be taken seriously and addressed with binding commitments. Setting a clear, reasonable timeline for such a response—for example, within 30 days—would show respect for the global community that helped make GitHub what it is.
If no substantive answers are provided, many will conclude that Microsoft is unwilling to rebuild trust or respect the values that made open source and digital sovereignty possible in the first place. If silence or spin is all that follows, developers, communities, and national stakeholders will begin organizing alternatives, engaging with independent foundations for oversight, and calling for regulatory scrutiny of platform stewardship on an industry-wide scale.
What Microsoft does next will set a precedent for all of Big Tech. This moment is about more than one company or one platform. It is about whether open source, digital sovereignty, and the collective trust, investment, and creativity of millions can survive in an era of corporate consolidation and broken promises.
While I am only one voice among many, thousands of developers, project leaders, and digital-sovereignty advocates echo these concerns. The false assurances made in 2018, documented above, are the root cause of this collapse of credibility. We have no interest in PR spin, empty reassurances, or legal jargon. Only real, specific action and binding commitments will be accepted by the community. Thank you for your attention. The world is watching what you do next.
Sincerely,
Dion Wiggins
A concerned developer of 40+ years, writing in solidarity with the global open source and digital sovereignty community
#OpenLetter #Microsoft #GitHub #OpenSource #DigitalSovereignty #CoreAI #Developers #Betrayal #Trust #AI
#Intelligence_artificielle #Emmerdification #GitHub #Microsoft #Logiciel_libre #Economie_numérique
#Microsoft #bans #LibreOffice #developer's account without warning, rejects appeal - Neowin
▻https://www.neowin.net/news/microsoft-bans-libreoffice-developers-account-without-warning-rejects-appeal
David Uzondu · Jul 29, 2025 17:18 EDT · Hot! 38
Recently, we reported on LibreOffice, accusing Microsoft of intentionally using complex #file_formats as a tactic to lock in users to Microsoft #Office, hindering open source alternatives like LibreOffice.
Now, Microsoft has banned LibreOffice developer, Mike Kaganski, from using its services, citing an “activity that violates [its] Services Agreement”.
According to Mike, this happened last Monday when he tried to send a technical email to the LibreOffice dev mailing list, which is a normal part of his routine, but Thunderbird returned an error saying the message couldn’t be sent. His account was blocked upon retry, and he found himself completely logged out of his Microsoft account.
#How_To Install and Use #Gemini CLI on Ubuntu
▻https://www.omgubuntu.co.uk/2025/07/how-to-install-gemini-cli-on-ubuntu
A simple guide to installing and using Google’s Gemini CLI on Ubuntu, a free, open source command line way to access Gemini LLM and use it to work with local files. You’re reading How to Install and Use Gemini CLI on Ubuntu, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.
#CPU performance optimization guide – part 3
▻https://gpuopen.com/learn/cpu-performance-guide/cpu-performance-guide-part3
AMD GPUOpen - Graphics and game developer resources We look at optimizing CPU performance by reducing the number of instructions, and highlights methods to enhance instruction efficiency and algorithm throughput.
#CPU performance optimization guide – part 4
▻https://gpuopen.com/learn/cpu-performance-guide/cpu-performance-guide-part4
AMD GPUOpen - Graphics and game developer resources Optimize CPU performance by manually writing x64 assembly code, offering a detailed comparison with compiler-generated instructions and achieving improved performance through streamlined instruction sets.
#CPU performance optimization guide – part 2 – cache invalidation
▻https://gpuopen.com/learn/cpu-performance-guide/cpu-performance-guide-part2
AMD GPUOpen - Graphics and game developer resources Part 2 shares a real-world problem of cache invalidation in CPU performance optimization, explaining how different data structures, compilers, and CPUs affect caching behavior and performance, and provides benchmarking and analysis techniques to address these issues.
#python is Now the Most Popular Language on #github
▻https://www.omgubuntu.co.uk/2024/10/python-most-popular-language-on-github-2024
Python has overtaken JavaScript as the most-used language on GitHub, according to the code-hosting platform’s latest Octoverse report. The company attributes this momentum to a massive influx of “data science and machine learning on GitHub”, which has seen a 59% increase in the number of contributions to generative AI projects. With Python being heavily used across ML, data science, and related fields, the rise makes sense – it’s less that traditional software developers are switching to Python but more that developers working with AI-related projects are needing to use it. Plus, it’s good #News for open source, with GitHub reporting […] You’re reading Python is Now the Most Popular Language on GitHub, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without (...)
When Do You Become A #developer ?
▻https://hackernoon.com/when-do-you-become-a-developer-80c40f5fc008?source=rss----3a8144eabfe3--
Over the past year I’ve taught myself to code. I’ve built and launched four web applications, taken courses from front-end to back-end…Continue reading on Hacker Noon »
Guide to recover from accidental commits and rebase in #git
▻https://hackernoon.com/guide-to-recover-from-accidental-commits-and-rebase-in-git-d46cc0b54046?
REBASE can be HelpfulTraditional working of Git RebaseIn Git, the rebase command integrates changes from one branch into another. It is an alternative to the better known “merge” command.You heard it’s scary right? You can create or recreate HISTORY! ?People ask you to stay away from git rebase but, it can be very useful at times. This articles covers a good use of REBASE command contrary to the definition that is taken from the official git documentation.A good use of git REBASELet’s talk about a very common scenario which I think all developers may have encountered or will encounter one day.Suppose you are using the same machine for the company as well as for your personal projects and when you use two different accounts for your #github, you configure your local git like this:git config (...)
10 Shortcuts Web Developers Use to Get Results in Record Time
▻https://hackernoon.com/10-shortcuts-web-developers-use-to-get-results-in-record-time-a101f22c89
Full Stack DeveloperIn this blog, I have listed new ideas that smart web developers use in order to code in a magical way. These ideas help them to code their programs in easier as well as quicker ways.Ultimately, it results in the faster completion of a web project and software businessmen can better know the value of this quick completion.So, here is the list:Avoiding online inspiration.Collaborating with others.Trying at least one thing differentThinking outside the boxCursor movement shortcutsGeneric windows shortcutsIDE ShortcutsBrowser shortcutsLet’s have a deep look at all these innovative ideas that a smart web #developer uses:1. AVOIDING ONLINE INSPIRATIONSmart web developers use strategies in order to create the best output in the least time with least efforts. These strategies (...)
#web-development #software-development #productivity #technology
#security, Obscurity, Openness
▻https://hackernoon.com/security-obscurity-openness-55c14f7e9cc1?source=rss----3a8144eabfe3---4
And making open source alternatives — #DevStoriesThis is a transcript of a talk I gave at the Hacker Noon #devstories @Github event, with minor modifications to improve readability. I wanted to call out the irony that security calls for openness, but security is also the reason for obscurity and proprietary implementations, especially in the hardware world. Making security more open is what motivated us to found SoloKeys, and make open source hardware security keys.▻https://medium.com/media/6a0e0d8f7709f7937cc7221c95a19eaa/hrefWhat I think is really fascinating about security is the duality that I tried to capture in the title between openness and obscurity.Borrowing a definition from cryptography:A (crypto)system should be secure even if everything about the system, except the key, is (...)
#open-source #developer #authentication #hackernoon-top-story
This is why your startup needs to hire full stack developers
▻https://hackernoon.com/this-is-why-your-startup-needs-to-hire-full-stack-developers-dc2ad074c9f
Every year, we see new technology trends popping up. With it, come new programming languages, frameworks, and other stuff for developers to learn and build upon. So it’s needless to say that finding a full stack #developer, let alone becoming one is more difficult than it has been ever before. But your startup needs them, and here is why.In any software/web/app development process, there are 3 crucial components. The front-end, the back-end, and the database architecture that connects everything. Full stack developers are by definition, those that have proficiency in all three of these and can work independently on any web development project without the need for additional support.If you don’t believe in the hype of full stack developers, then definitely you might consider looking for (...)
#full-stack-developer #web-development #app-development #software-development
The Future of #robotics #development with Eva Li of Vincross
▻https://hackernoon.com/the-future-of-robotics-development-with-eva-li-of-vincross-dd8d85256d4e?
Episode 29 of the Hacker Noon #podcast: An interview with Eva Li of Vincross, a consumer robotics company.Listen to the interview on iTunes, or Google Podcast, or watch on YouTube.In this episode Trent Lapinski interviews Eva Li from Vincross, where you get to meet one of the robots Hexa, and learn about their new robotics development platform MIND KIT. They’re currently doing a KickStarter.“HEXA is a six-legged programmable robot.”“Our users are, but not limited to, software developers, programmers, researchers, people who are into robotics, hobbyists, and some students who are learning coding through HEXA.”“ You can not just learn programming, learn robotics, also you can make it actually useful in your daily life. We offer this ideal hardware and software to make your ideas come true” — Eva (...)
10 Tutorials in Today’s Top Languages!
▻https://hackernoon.com/10-tutorials-in-todays-top-languages-ce51ce6b4ede?source=rss----3a8144ea
But first, shoutouts to our investors of the week: Minh Doan, Atif Ali, & Monday Capital! Thanks to these guys (and our other 1.24k+ investors), we successfully closed our crowdfunding with max amount raised 12 hours ago!Ginni Rometty, the CEO of IBM once said, “Growth and comfort do not coexist.” As software developers, learning a new language or a new skill is necessary to grow and get us out of our comfort zones. This week at Hacker Noon, we’ve seen some great tutorials that will help you do just that!JavaScript:Promises in 70 lines of codeEver wondered how JavaScript Promise works internally? Obviously there is some native browser support involved, right? Nope! We can implement the Promise interface using pure JavaScript and it’s much simpler than you may think, we can do so in only (...)
#developer-tutorials #dev-tutorial #software-tutorials #software-development #hackernoon-letter
4 Myths About Programmer Motivation
▻https://hackernoon.com/4-myths-about-programmer-motivation-5fc4d654fe14?source=rss----3a8144eab
I’m just not motivated to code today.Myth #1: Managers cannot (or should not) affect motivationWhen managers believe that people either have or do not have motivation, they feel powerless to affect motivation. In her book Mindset, Dr. Carol Dweck refers to this as the “fixed” mindset. The fixed mindset is the belief that people are born with unchangeable strengths and weaknesses and that people would do well to build on their strengths and avoid tasks at which they are weak. She contrasts this with the “growth” mindset, which is the belief that people grow and learn throughout their lives.In Mindset, Dweck explains how to break out of the fixed mindset and adopt the growth mindset. She also provides research supporting the belief that this change is possible (even for old guys like me!). But (...)
#agile #programmer-motivation #developer-motivation #startup #software-development
Automate Your Workflow with #git Hooks
▻https://hackernoon.com/automate-your-workflow-with-git-hooks-fef5d9b2a58c?source=rss----3a8144e
Git hooks are one of the most underrated git features, and have the potential to increase your productivity as a developer. Have you ever wanted to run a command every time you commit or push? Lucky for you, that’s exactly what git hooks do — they’re custom scripts that run before or after git commands to automate manual tasks. Read on to find out how hooks could improve your workflow.Why use git hooks?I came to learn about hooks after embarking on a quest to automate my own workflow. You see, for better or worse, I make use of FIXME: comments in my code to remind myself to revisit something. My usual process involved doing a global search for “FIXME:” before committing, however I’m sure you can already see plenty of room for human error.Hooks came to my rescue. I was able to create a simple (...)
How to Use #git Hooks in Your Development Workflow
▻https://hackernoon.com/how-to-use-git-hooks-in-your-development-workflow-a94e66a0f3eb?source=rs
Get hooked !!Photo by Alvaro Reyes on UnsplashOverviewIf you’ve ever worked on an open-source project, or you’re working in a team, it’s very likely you are using some kind of version control. Version Control System(VCS) has become one of the major requirement for any project, Git being the most popular one. However, as the team grows in number, it becomes difficult to handle the different code styles and to enforce certain rules across all the contributors. These issues aren’t noticed by a contributor until he has pushed his changes which result in overheads for the core maintenance team. To enforce these rules and validate the code being pushed, Git has a great feature, called Git Hooks.What are Git Hooks?These are custom scripts which are triggered on certain specific git events. Hooks (...)
#developer #software-engineering #software-development #developer-tools
How to highlight and multi-select items in a FlatList component- React Native
▻https://hackernoon.com/how-to-highlight-and-multi-select-items-in-a-flatlist-component-react-na
You’ve probably heard about Flatlist component if you are working in React native and handling lists of various client data and details either from the API or form fields. Basically, Flatlist is a core component designed for efficient display of vertically scrolling lists of changing data. It is a component which came into existence in React native after the 0.43 version, it replaced the ListView component and enhanced the ability of developers to deal with lists more easily.What is Flatlist and How can we use it for displaying dynamic or static lists?FlatList is a simple component introduced to remove the limitations of the ListView component. The basic props required to handle a Flatlist are data and renderItem. For simplicity, data is just a plain array, whereas renderItem renders (...)
#flatlist-component-react #javascript #react-native #developer #flatlist-component
how CardChecker changed my development #workflow
▻https://hackernoon.com/cardchecker-easing-companies-development-workflow-32dde28e160c?source=rs
Image sourceI have been working as a Full Stack Developer for the last 2 years. I have worked in a small startup and also the opposite, MNC company. When I start with a new company it’s always exciting to work on new projects, technology stack. It’s always easy to understand their system, architecture. Because that’s the basic understanding every developer have. But apart from this, there is one thing, which I always found most difficult to understand, The Development Workflow of a team. Because it is something which not every company have in common. Everyone has its own way of developing products with its pros and cons. And as a part of the company you also have to follow this. I struggled a lot for my initial months to understand development workflow. And beyond that, you also have to (...)
#google I/O 2019 — Everything You Need To Know
▻https://hackernoon.com/google-i-o-2019-everything-you-need-to-know-ec5ca61192d7?source=rss----3
Google I/O 2019 — Everything You Need To KnowOnce again, we are approaching the #developer conference season and for the start, Google has confirmed the Google I/O 2019.The conference will take place at Shoreline Amphitheater in Mountain View, California same as last year. It will be a 3-day event starting on May 7 and ending on May 9, 2019. The dates were revealed by Google’s CEO Mr. Sundar Picahi in a tweet late last week.Glad the transmission was received:) See you at Shoreline Amphitheatre May 7–9 for this year’s I/O! #io19 pic.twitter.com/CXWpQR4Eza— Sundar Pichai (@sundarpichai) January 25, 2019Till that time, we are left with nothing but to speculate as what will be announced at the show. Let’s take a look at what to expect from Google I/O 2019 –Android QWithout a doubt, #android Q will be (...)
Bootstrapping A Career Via Developer Camp
▻https://hackernoon.com/bootstrapping-a-career-via-developer-camp-ebb73ef49b7a?source=rss----3a8
Developer CampWhile there’s hundreds of #hackathons held world-wide, there’s only one Developer Camp.Square, Getaround, Temple Run, OAuth, TestFlight, push.io, and Zūm — each of these have foundations at Developer Camp over the past twelve years. In fact, major compaines including Apple, Oracle, Google, Amazon, Disney, and Facebook have purchased companies from the winning teams at Developer Camp.What makes Developer Camp so unique and special? Three words.Inclusion, Diversity and Empowerment.Developer Camp is a concept that fused from several distinct, previously-existing event models. The first was BarCamp, a participant-driven “unconference” in which the content of presentations is decided by the attendees, presented by them, and organized entirely on the spot. Our camp incorporates this (...)
#developer Spotlight : Leslie Cohn-Wein of Netlify
▻https://hackernoon.com/developer-spotlight-leslie-cohn-wein-of-netlify-fe51e862fb18?source=rss-
In this installment of the Cosmic JS Developer Spotlight Series, we sat down with Leslie Cohn-Wein, a Front End Developer and Austin native now residing in Dallas, Texas. Leslie most recently worked as a Front End Engineer for Canvas United, a New York City-based digital agency, prior to starting as a Front End Developer at Netlify. Follow Leslie on Twitter or LinkedIn and enjoy the Q/A.Cosmic JS: When did you first begin building software?Leslie: I taught myself basic CSS in the early 2000s in order to customize my MySpace and LiveJournal backgrounds. To my surprise, that experience kicked off an enduring interest in code.After studying digital media in college and interning at the Denver Open Media Foundation theming Drupal sites for nonprofits, I moved to NYC for a role as a (...)
6 Free #software To Boost Your #productivity In 2019
▻https://hackernoon.com/6-free-software-to-boost-your-productivity-in-2019-61e22bd85195?source=r
Today everyone is running the race to be more productive. To discover smart hacks or shortcuts to save time. And since most people spend a large amount of their time staring into a computer screen, that’s a good place to start.Mobile phones might be winning the overall battle against the desktops. According to Google, more searches are done via mobile platforms than desktops. But as much as mobile phones might be booming, they got nothing on desktops when it comes to work.Most of the workforce around the globe still depend on a Mac, Windows or Linux machine to do most if not all of their daily grunt work.And if you’re anything like me, you’re always on a lookout for some kickass software to increase your productivity or make your work easier and enjoyable.In my quest to find such software (...)
Keyboards for Developers, Part 1 — Let’s Talk About #laptop Keyboards
▻https://hackernoon.com/keyboards-for-developers-part-1-lets-talk-about-laptop-keyboards-6b99298
Keyboards for Developers, Part 1 — Let’s Talk About Laptop KeyboardsI like obsessing over keyboards — I’ve owned many mechanical keyboards (which I’ll talk about in part 2 of this post), and I also like to have a good typing experience when I’m coding on a laptop.When it comes to #apple, there’s little choices — the Macbook/Macbook Pro keyboards are what you get. If you work in tech, chances are you don’t really have a choice of a laptop; you’re just given a Mac. There’s not much to talk about there.For personal uses, I like to have a PC laptop; that nowadays I tend to dual-boot Windows and Linux with. I’ve written articles about installing CentOS and Antergos on different PC laptops.When looking for such ultrabook laptops, aside from laptop weight, the #keyboard layout is one of my primary concerns. (...)