#computer sicence

[musicforprogramming]

ECHTZEIT by Sensorama

from the album Welcome Insel (1995) on Ladomat 2000.

[attitudetallyacademy]

The Foundations of Object-Oriented Analysis: What Every CS Student Should Know

Introduction:

Object-Oriented Analysis and Design is a methodology used in software engineering to design and model complex systems. It's a structured approach that breaks down a problem into manageable components and uses objects, classes, and relationships to represent and solve real-world issues in a digital context. To put it simply, OOAD is the blueprint for building software that performs effectively, is easy to maintain, and can adapt to changing requirements. If you're a computer science student in Yamuna Vihar, you're likely well aware of the rigorous demands and ever-evolving nature of your field. Computer science is an exciting, constantly changing discipline, and one of its fundamental pillars is Object-Oriented Analysis and Design (OOAD).

At the heart of OOAD lie several key concepts, and let's discuss them briefly.

Objects

Objects are the building blocks of OOAD. They represent real-world entities in your software. For instance, if you're designing software for a library, objects could include books, patrons, and librarians. Objects encapsulate both data (attributes) and behaviour (methods) related to their respective entities, making them self-contained and modular.

Classes

Classes are the blueprints for objects. In the library software example, you might have a 'Book' class that defines the structure and behavior of all books in the system. Classes provide a template for creating objects, specifying their attributes and methods.

Inheritance

Inheritance is a powerful mechanism in OOAD, allowing you to create new classes based on existing ones. It promotes code reusability and the organization of related classes into a hierarchy. For our library software, you might have a 'Fiction Book' class that inherits from the 'Book' class, inheriting its attributes and methods while adding specific features unique to fiction books.

Encapsulation

Encapsulation involves bundling data (attributes) and methods into a single unit, i.e., the object. This concept ensures that data remains private and can only be accessed through defined interfaces, promoting data security and reducing unintended interference in the code.

Polymorphism

Polymorphism allows objects of different classes to be treated as objects of a common superclass. In our library system, this would mean that different types of books (e.g., Fiction Book and Non Fiction Book) can be managed in a uniform way.

Relationships

Understanding relationships between objects is vital in OOAD. These can be associations, aggregations, or compositions, and they define how objects interact and collaborate. In our library system, the relationship between a 'Patron' and 'Book' objects can be an association, as patrons borrow books.

Keywords in Context

In your computer science course in Yamuna Vihar, you'll encounter these fundamental OOAD concepts. This knowledge is critical for designing robust, efficient, and maintainable software systems.

Conclusion

Object-Oriented Analysis and Design forms the backbone of software engineering. Gaining proficiency in OOAD is essential for a successful career in software development. These foundational concepts will help you navigate the complexities of software design, creating robust solutions that meet the needs of your clients and users.

So, as you continue your studies and pursue your computer science classes in Yamuna Vihar, remember that mastering OOAD is a significant step toward becoming a skilled and sought-after software engineer. With this knowledge, you'll be well-prepared to tackle the challenges and opportunities that lie ahead in your exciting journey through the world of computer science.

[thoughtbuble]

READ CODE & WRITE CODE; DON’T WATCH CODE

I always preferred watching video tutorials because they just showed you how everything worked and where to find what you want, And for any thing I wanted to learn I always searched for video tutorials. I did what they taught after watching videos or practice with them with multiple screens side by side (SOMETIMES PAUSING THE VIDEOS) and it always feels like you are learning because at the end of video you were able to do what tutors were able to in tutorials. For a long time this felt right but after a short thought about why I was not able to code whatever I wanted to code with a clear understanding? This question gave birth to a thoughtbuble that the videos I watch may be the reasons because in videos you never see tutors making mistakes, obliviously you wont see them making mistakes for they edit the videos and most disturbing thing is that you don’t actually learn by watching videos it is like you close your eyes and tutors catch hand and take you somewhere you have no idea. To prove this I tried by reading documentations of many frameworks and programming languages and felt the difference of learning by trial and error that profound developers speak about. I was able to understand what I was doing and the connection between each part of the code. 

[luneabun-blog]

school / thoughts

I’m strongly considering taking up computer science again when I go back to school instead of biology. Better job opportunities, pay, and job security. The first time around I didn’t like it but I also didn’t try (like at all) so I’m teaching myself python on code academy to see how I like it now that I’m focused and motivated. So far it’s really fun. I actually really enjoy programming, and I think the types of jobs I would get as a comp sci major would work better with my personality considering how introverted I am. But still... can’t decide between bio and comp sci. I’m going to keep taking these free online classes on coursera until I go back to school in august and I guess I’ll see which I end up liking more. So far I’m surprised I’m actually leaning more towards computer science than biology... Let me take that discrete math course again and then see how I feel about it lol.

At the end of the day, any valuable degree is going to be difficult to achieve. So the difficulty doesn’t matter to me, so long as it’s worth the struggle. With bio, I’m afraid I would work my ass off just as much but not get as much out of it. Computer science would still be the safest bet as far as finding a job after school is concerned. I guess I’m just afraid of making the same mistakes twice... but the same thing could happen with biology. I mean, to be honest, my major was never the problem, I was the problem. And I’d like to think that I’ve fixed all of those issues I had that kept me from being successful the first time around. I’m more mature, responsible, and motivated now. I needed to have this experience in order to get where I’m at now. Now the hard part is having a game plan and getting started.

“Focus on your failures, mistakes and defeats. Study them. Obsess over them. Learn from them. Every one is an opportunity to better yourself.”

[musicforprogramming]

14:31 by Global Communication

from the album 76:14 (1994) on Dedicated Records.

[vladteppi-blog]

Very minimal sleep this week

coding