Forem: temaweb10

How to start your journey in Open Source using the example of a small Go project

temaweb10 — Fri, 02 May 2025 08:47:28 +0000

Hi! I am the developer of a small project called Deletor, a utility for cleaning files on Go. I want to tell you why open source is cool, and how you can start small.

Why Open Source? I started with a simple one: I wanted to make a convenient tool for myself. But when I posted the code on GitHub, I realized that open source is not about "free code." It's about:

- Sharing experiences with other developers

- Getting feedback from real users

- An opportunity to learn from those who review your code

Why participate? When I see a new PR in Deletor, it's always inspiring. Someone took their time to improve my project. And you know what? It works both ways.

Participation in open source is:

- Practice working with real code

- The opportunity to get a quick feedback

- A chance to learn how to write code that is understandable to others

Deletor as a launching pad. Deletor is not a huge project with thousands of stars. It's utility, but it has everything you need to get started.:

- Clear code structure

- Active issues of different difficulty levels

- Quick code review (usually within 24 hours)

What will you get?

- Practical experience working with Go

- Feedback from experienced developers

- The ability to add a real project to your portfolio

- New acquaintances in the community

Conclusion. Open source is not about the size of a project or the number of stars. It's about people who want to create something useful together.

Deletor is a great project to start with because:

- It is small, but contains all the necessary components.

- We have a friendly community.

- We quickly answer questions and review the code.

Join us! Let's do something cool together.

AI as the New Opium for Developers: The Dependency That’s Killing the Industry

temaweb10 — Mon, 03 Mar 2025 16:08:09 +0000

Artificial intelligence is rapidly transforming the IT industry, promising convenience and speed. But behind this facade lie serious risks: the degradation of skills and the creation of a generation of developers incapable of critical thinking. It’s time to ask ourselves: Are we becoming hostages to a technology that promised us freedom?

Crisis of Fundamental Knowledge: "The Operator Generation" AI is turning development into a "puzzle assembly." Young programmers are losing the ability to understand why code works. The more people rely on AI, the less they develop their own judgment and cognitive skills.

This will lead to:

Decline in the quality of architectural solutions: Developers will create systems that work but are inefficient.

Loss of the ability to solve complex problems: If developers stop understanding the basics of programming, they won’t be able to tackle tasks requiring deep knowledge of algorithms, architecture, and optimization.

Loss of the ability to innovate: If you don’t understand how basic things work, you won’t be able to create something new.

Research:

A study by Microsoft and Carnegie Mellon University showed that the more people rely on generative AI tools to complete tasks, the less they demonstrate critical thinking skills.

The article "The Widening Gap: The Benefits and Harms of Generative AI for Novice Programmers" notes that beginners relying on AI may struggle to develop metacognitive skills and face an illusion of competence.

AI is like a crutch. If you use it constantly, your muscles atrophy. The same happens to the brain: if you don’t train it, it becomes weaker.

Junior Developers Under Threat: How AI Will Create a Shortage of Senior Specialists Artificial intelligence is already capable of generating simple code, performing tasks that were once assigned to junior developers. Why would companies hire newcomers if AI can do the same work faster and cheaper? At first glance, this seems like progress: companies save resources, and projects are completed faster. However, behind this convenience lies a serious threat to the entire industry.

Imagine this: today, AI replaces junior developers, and in 5–10 years, the industry will face a catastrophic shortage of experienced professionals. Senior developers will become even rarer and more expensive. Companies will be forced to compete for a limited number of specialists, leading to rising salaries and increased development costs.

Vulnerabilities in AI-Generated Code AI generates code without considering security. The number of repositories containing personal and payment data has tripled, the number of APIs lacking authorization and input validation has increased tenfold, and the number of exposed confidential API endpoints is growing. As AI-generated code scales, so do the risks to application security, highlighting the need for more effective risk identification and management.

The company Apiiro, with support from Gartner Research, published a concerning report on the security of AI-generated code. Experts analyzed millions of lines of code across dozens of companies in the financial, industrial, and tech sectors. The analysis revealed that when using AI to write programs, security inevitably takes a backseat to development speed.

Apiiro specialists propose a comprehensive approach to solving the problem. First, it’s crucial to implement advanced automated code analysis systems that can detect vulnerabilities during the development stage. Additionally, new security standards tailored to AI development must be developed. Furthermore, the protection of repositories containing sensitive data should be strengthened by implementing multi-layered access control systems.

Trusting AI without verification is like trusting a blind driver to navigate a mountain road.

AI Hallucinations: Lies Without Blushing AI doesn’t understand what truth is. It simply predicts the next token based on the data it was trained on. And it can mislead even experienced developers.

Code Hallucination (2024): The authors explore various types of hallucinations in code generated by large language models and present the HallTrigger technique for effectively creating such hallucinations.

Conclusion: What Should We Do?
Recommendations for developers:

Don’t fear the future: Let this environment motivate you to strive for excellence, not procrastination.

Learn the basics: Algorithms, data structures, patterns—the foundation without which you can’t solve complex problems. Make them chase you, not the other way around.

Don’t delegate everything to AI during training: Write code manually, even if it takes longer.

Train critical thinking: Ask yourself, “Why did AI suggest this?”

Don’t forget about security: If you don’t verify its suggestions, you risk creating an insecure product.

How I made a file downloader on React and posted it on npm

temaweb10 — Mon, 15 Apr 2024 14:28:02 +0000

react-file-uploadify is a flexible and customizable React library for uploading drag-and-drop files. Users can easily drag and drop files, delete selected files, and customize the component by adding their own classes via props. The library also provides the ability to set limits on the number of accepted files, their size and file types.

Creating a library template using npx create-react-library

To create this library, we used the create-react-library tool, which allows you to quickly and easily create a new React library. We used the following steps:

We have become a create-react-library globally: npm install -g create-react-library
Created a new library using the command: npx create-react-library react-file-uploadify
The project structure was generated automatically, including the necessary files for library development
Publishing an npm package npm publish

Installing my library

npm install --save react-file-uploadify

Using

import { FileDropZone } from 'react-file-uploadify'
import 'react-file-uploadify/dist/index.css'
import React, { useState } from "react";
import myClassNames from './myClassNames.module.css'
const App = () => {
  const [files, setFiles] = useState([])
  const updateFiles = (incomingFiles) => {
  setFiles(incomingFiles);
  };
  return (
  <div style={{width:"600px", height:"300px", margin:"32px"}}>
    <FileDropZone
    onChange={updateFiles}
    maxFilesSizeInMb={2}
    acceptTypes={[".docx",".pdf",".jpg"]}
    haveFileList={true}
    multiple={true}
    minFiles={2}
    maxFiles={5}
    lang={"en"}
    classNames={{
    "file-drop-zone_box": myClassNames.myFileDropZoneBoxClass,
    "file-drop-zone_button": myClassNames.myButtonClass,
    "file-icon": myClassNames.myFileIconClass,
    "file-box": myClassNames.myFileBoxClass,
    "file-box__file-button": myClassNames.myFileButton
    }}
    />
  </div>
  );
}
export default App;

The main functionality

Multiple File selection: Users can select multiple files at the same time.
File Types: You can specify the types of files that users can select.
Limit on the number of files: You can set the minimum and maximum number of accepted files.
File size limit: It is possible to limit the total size of the selected files.
Displaying a list of selected files: You can show a list of selected files.
Customization: The component is easily configurable by adding its own classes via props.
Language: you can choose Russian or English interface language

Demonstration of the component

Why should I use react-file-uploadify?

This library provides a simple and elegant way to add file upload functionality to your React applications. Due to the flexibility and customizability of the component, developers can easily integrate it into their projects and adapt it to their needs. It is recommended to use this library for those who need a convenient and powerful tool for uploading files in their React applications.

Conclusion

I created a react library that has 500+ downloads in 5 days on npm. Using the create-react-library tool has greatly simplified the process of creating a new library, allowing you to focus on implementing the functionality, rather than configuring the project. Developing react-file-uploadify was a pleasant experience that allowed me to apply my knowledge of React and create a useful tool for other developers.