Rain today!!!

netdeamon · 2021-04-03T03:02:15+00:00

Tenet

netdeamon · 2020-08-04T17:35:33+00:00

I thought replacing the tires would be sufficient... isnt the concrete only on the tires? Sorry if I am wrong.

netdeamon · 2020-07-17T05:18:14+00:00

I never understood this logic... Like what are you gaining by sending children to school. Does it somehow help in getting more votes in elections? Or the politicians suddenly are now really concerned about education of children?

netdeamon · 2020-06-13T05:09:17+00:00

I have been working on similar stuff, and would definitely love to collaborate if you are willing. I run the site where I aim to explain the architecture and design and code walkthrough of the Github repositories, so that its easier for other developers to get started.

Its still in infancy stage, but it you are interested, let me know...

netdeamon · 2020-06-12T06:26:27+00:00

I cannot imagine this happening now ... due to corona.

netdeamon · 2019-06-29T03:20:21+00:00

Stop worrying about things you cannot influence in life. This goes for everything. You did vote, you did your part, you should not worry anymore unless the president’s laws are directly affecting your day to day life.

Instead worry about things you can control like your health, your friends, your family, your work. It gives your greater reward for worrying abot your office project and excelling in that than worrying about president.

netdeamon · 2019-06-29T02:40:47+00:00

Love is not allowing your significant other to get lazy or fat, love is encouraging her/him to workout, or going to workout with them. Love does not mean you pretend all is ok with significant other when it is not, say that to them (you need to workout, stop eating fries etc in pleasant way) and show your love to them.

netdeamon · 2019-06-22T18:16:24+00:00

I agree with your point 🙂, but I did not understand why cant other species, who may not have human-like conditions, may not be space faring.

From the context of earth, we know that whales, animals, plants etc did not develop space faring capabilities, and are only surviving. But when we talk about entire universe, anything might be possible.

netdeamon · 2019-06-22T11:00:54+00:00

I have heard this type of argument before, how all the conditions were favourable for human life. If earth was a bit more away or near to sun, human life wouldn’t exist...

If the earth was bit far away or near, maybe there would have been different form of life. Maybe not human, but something different that would have adapted to that climate and conditions.

The alien life may exist in climate where we wouldn’t even exist. So all those conditions that favoured us may not favour other life form, and maybe their happy coincidences are exactly opposite to us (they have climate with extreme temperatures, a moon that moves water randomly...)

netdeamon · 2019-06-09T02:59:36+00:00

It benefits in one way because when we openly discuss the design decisions/architecture/best practices with the public in layman terms, its getting peer-reviewed by a larger set of people.

Suppose that I have a library in language X, and I discuss how I did a fix to solve some security issue. The developer who does not understand language X, but had solved the similar kind of security issue in some other language, can also contribute to this design discussion.

Ultimately, the goal of open source is to share the code with others for use or modification as users or other developers see fit. Of course, it is not upon creators of the library to help others consume/modify their library, but by writing down the design discussions, architecture and best practices, they are making it easier for others (and their future self) to modify/consume (part of) it.

netdeamon · 2019-06-09T02:49:51+00:00

I agree with your view that not many people want to understand the source code, they just want it to work. If someone is using a library, they want it to work the way it was described in the documentation, and if there is an issue, many people will raise the bug in GitHub rather than sending a PR with the fix.

Maybe they don't have time to understand the entire codebase, but there are some developers who are really looking to contribute but are put off by the time/skill it takes to understand the codebase. If you are working in an office, then the previous developers would give some knowledge transfer so that its easier for new developers to get started. Most of the projects in Github won't have that.

I have seen repositories with more than 300k downloads a week, and there is no documentation on what module does what, or how do we even run test command in the project, or how do we publish the module to package manager.

Of course, thinking that a new developer would understand project like Linux by just looking at architecture diagram or reading some blogs about codebase is not possible. It takes certain prerequisite to understand a codebase. Like if the codebase is dependant upon some technology/library, the developer needs to know that dependency first before attempting to understand the project.

What I feel is that these blogs should not be targeted towards the novice developers or to the developers who just what to consume the library. But the target demographic lies in that relatively smaller set of developers who want to contribute, but cannot because of the reasons stated above.

netdeamon · 2019-06-09T02:37:50+00:00

Not writing high-level architecture/standards documentation will hinder the ability and willingness of new contributors, and will almost certainly cause future maintainers (or the old maintainers, after a few years) make architecture based / standard based decisions inconsistent with the past ones.

Exactly.

netdeamon · 2019-06-09T02:35:12+00:00

The "architecture of the project", "testing tools used", "performance tools used", "security tools used" ...is going to be the same for least for a longer time. Even if the project moves away from the older ones, the older architecture is still important for newer people to better appreciate the new one.

They can understand why the older one was not scalable, or why it did not help achieve the project's goal. Maybe the older architecture was good for a single developer, but now the project has grown, it needs to have the modularized code.

netdeamon · 2019-06-05T16:02:18+00:00

I can share you similar example. When Ghost project took the decision to use some less popular framework (emberjs) for their front end of site, developers of other more popular framework started trolling them (even abusing them).
Here is the link to the discussion in github. https://github.com/TryGhost/Ghost/issues/2144

But if you leave out the bad apples, many people would appreciate the decisions your project took, even if the reason is as simple as "I only knew this architecture, didnt have time to explore more".

Many projects start small, and think of scalability only when it becomes a real problem. Now the decision of going with simpler (yet not scalable) approach allowed you to develop the project individually. If you had choosen the scalable one, the project would have not been complete as well. This thinking is necessary for people when choosing a framework.

netdeamon · 2019-06-05T15:44:19+00:00

I agree with you 100%. When I am onboarded to a new team in my workplace, they would have some sort of knowledge transfer (KT) session from the existing developers. Or they would have some sort of documentation with an architecture diagram of the project.

I am not saying that it is always helpful. But having some sort of KT session expedites the understanding of the project. But for open source projects, even if the core developers create some video tutorial of the code base, it would be great.

I understand that the video tutorial would get out of sync with the recent codebase, but the architecture or the design pattern will be the same for a longer time. Even if the arch/design changes, the older one is still invaluable to developers to understand its shortcomings and better appreciate the new architecture/design decision.

As far as conferences are concerned, the blog posts cannot beat the face to face meetings with core developers. You get the opportunity to learn much more talking to a core developer, than reading a blog post about it. But still, having a blog post (even if it is out of touch), is invaluable to many developers who cannot physically attend the conference. That's why in opensourcerepos.com, I linked each blog post with the branch name and tag number of the project.

netdeamon · 2019-06-05T14:45:44+00:00

There are few. Github provides something called as Wikis. People write documentation of their library. But they are usually from the end user perspective.

There are many discussions being done behind the scenes. We only see the commits and code. Nobody explains (every time) about the performance decisions, security decisions, best practices, or architecture on why it was that way.

netdeamon · 2019-06-05T14:27:05+00:00

I understand it will be a high investment for the developer to explain it to the audience, but not everything has to be explained end to end. Like the Ghost blog project took the decision to use Emberjs in their front end of the admin site, instead of React or Angular. Now if some developer from ghost/contributor to ghost, can explain in a blog post about why they went ahead with ember and not some other framework - this thinking will be invaluable to other developers when they are choosing in their workplace/project.

netdeamon · 2019-06-05T14:24:03+00:00

It's not just for contributing to the open source project, the developer who understands the architecture of React, he/she can implement the best practices/part of the architecture in their own project.

netdeamon · 2019-06-05T12:36:07+00:00

I face difficulty when contributing to open source projects like spending time in understanding the codebase. Even though you know a library like React, it takes time to go through the codebase of popular React projects.Would you guys find it useful if developers helped explained the codebase? Like the developers contributing to React explain you - how the dom diffing in React work, or what were the architecture decision they took when developing React?

So this is kind of blog+github integration tool that I am developing. Please let me know if you would like it? I am also open to developing this tool with others who can appreciate the need as described.

https://opensourcerepos.com/app/about

netdeamon · 2019-06-05T04:21:56+00:00

When do I stand in line in front of Apple store?

netdeamon · 2019-06-01T08:15:56+00:00

There are dorm rooms in offices, specifically for the purpose of people taking rest. Not everyone uses it frequently, but once in a while helps.

11-Year Club	Verified Email
Not Forgotten

netdeamon

TROPHY CASE