#java array

[watchmorecinema]

Normally I just post about movies but I'm a software engineer by trade so I've got opinions on programming too.

Apparently it's a month of code or something because my dash is filled with people trying to learn Python. And that's great, because Python is a good language with a lot of support and job opportunities. I've just got some scattered thoughts that I thought I'd write down.

Python abstracts a number of useful concepts. It makes it easier to use, but it also means that if you don't understand the concepts then things might go wrong in ways you didn't expect. Memory management and pointer logic is so damn annoying, but you need to understand them. I learned these concepts by learning C++, hopefully there's an easier way these days.

Data structures and algorithms are the bread and butter of any real work (and they're pretty much all that come up in interviews) and they're language agnostic. If you don't know how to traverse a linked list, how to use recursion, what a hash map is for, etc. then you don't really know how to program. You'll pretty much never need to implement any of them from scratch, but you should know when to use them; think of them like building blocks in a Lego set.

Learning a new language is a hell of a lot easier after your first one. Going from Python to Java is mostly just syntax differences. Even "harder" languages like C++ mostly just mean more boilerplate while doing the same things. Learning a new spoken language in is hard, but learning a new programming language is generally closer to learning some new slang or a new accent. Lists in Python are called Vectors in C++, just like how french fries are called chips in London. If you know all the underlying concepts that are common to most programming languages then it's not a huge jump to a new one, at least if you're only doing all the most common stuff. (You will get tripped up by some of the minor differences though. Popping an item off of a stack in Python returns the element, but in Java it returns nothing. You have to read it with Top first. Definitely had a program fail due to that issue).

The above is not true for new paradigms. Python, C++ and Java are all iterative languages. You move to something functional like Haskell and you need a completely different way of thinking. Javascript (not in any way related to Java) has callbacks and I still don't quite have a good handle on them. Hardware languages like VHDL are all synchronous; every line of code in a program runs at the same time! That's a new way of thinking.

Python is stereotyped as a scripting language good only for glue programming or prototypes. It's excellent at those, but I've worked at a number of (successful) startups that all were Python on the backend. Python is robust enough and fast enough to be used for basically anything at this point, except maybe for embedded programming. If you do need the fastest speed possible then you can still drop in some raw C++ for the places you need it (one place I worked at had one very important piece of code in C++ because even milliseconds mattered there, but everything else was Python). The speed differences between Python and C++ are so much smaller these days that you only need them at the scale of the really big companies. It makes sense for Google to use C++ (and they use their own version of it to boot), but any company with less than 100 engineers is probably better off with Python in almost all cases. Honestly thought the best programming language is the one you like, and the one that you're good at.

Design patterns mostly don't matter. They really were only created to make up for language failures of C++; in the original design patterns book 17 of the 23 patterns were just core features of other contemporary languages like LISP. C++ was just really popular while also being kinda bad, so they were necessary. I don't think I've ever once thought about consciously using a design pattern since even before I graduated. Object oriented design is mostly in the same place. You'll use classes because it's a useful way to structure things but multiple inheritance and polymorphism and all the other terms you've learned really don't come into play too often and when they do you use the simplest possible form of them. Code should be simple and easy to understand so make it as simple as possible. As far as inheritance the most I'm willing to do is to have a class with abstract functions (i.e. classes where some functions are empty but are expected to be filled out by the child class) but even then there are usually good alternatives to this.

Related to the above: simple is best. Simple is elegant. If you solve a problem with 4000 lines of code using a bunch of esoteric data structures and language quirks, but someone else did it in 10 then I'll pick the 10. On the other hand a one liner function that requires a lot of unpacking, like a Python function with a bunch of nested lambdas, might be easier to read if you split it up a bit more. Time to read and understand the code is the most important metric, more important than runtime or memory use. You can optimize for the other two later if you have to, but simple has to prevail for the first pass otherwise it's going to be hard for other people to understand. In fact, it'll be hard for you to understand too when you come back to it 3 months later without any context.

Note that I've cut a few things for simplicity. For example: VHDL doesn't quite require every line to run at the same time, but it's still a major paradigm of the language that isn't present in most other languages.

Ok that was a lot to read. I guess I have more to say about programming than I thought. But the core ideas are: Python is pretty good, other languages don't need to be scary, learn your data structures and algorithms and above all keep your code simple and clean.

[arshikasingh]

How to convert List to Array?

Let us see how to convert List to Array:

[tinchicus]

Essta funcion nos permite buscar un valor dentro de un array. Espero les sea de uttilidad y buen dia del trabajador!

[tpointtech1]

Common Mistakes When Initializing Arrays in Java and How to Avoid Them

Learn the common mistakes developers make when initializing arrays in Java and how to avoid them. Master proper array initialization techniques and write cleaner, error-free Java code with this beginner-friendly guide.

[aspectpriority]

spending half the day learning java via making a homestuck typing quirk thing and then getting followed by a homestuck blog is genuinely hysterical. anyway welcome 2 the hole in the ground i call a blog :3

[specbee-c-s]

JavaScript’s native Array and Object methods

Think you know JavaScript? Find out how native features can handle Objects and Arrays that simplify coding. No libraries necessary!

[lord-of-the-noodles]

thinking about her(GreedyStackDestroyer)

[eggsistential-basket]

my brother in fuck I remember how to rotate a min max heap but I forgot what an ARRAY in JAVA is ic kl;dJZS:SACK JDH CNKSLADJA:LJ<HNCKASLJ DHSLFIJ:V vfdjLSjvf; lk

[himejoshibutch]

tech mutuals/followers i need some help...

i almost finished c programming so...

[dosomedev]

Know what Java PriorityQueue is for?

[leathemage]

for (String AAAAA : screaming) {

System.out.println("AHHHHHH " + AAAAA);

}

screaming [us politics, work, family, the world]

[arshikasingh]

Java Array

Let us see the definition of Java Array:

[tinchicus]

Esta funcion nos permite llenar un array con un valor. Espero les sea de utilidad!

[frog707]

Those wise, old Javanese

Yesterday I discovered "Arrays of Wisdom of the Ancients", Aleksey Shipilёv's 2016 quest for the most efficient way to convert Java collections into arrays. It's a fascinating story. Aleksey explains why the conversion API is the way it is, then presents some counter-intuitive measurements.

Next he makes an important point about performance analysis:

At this point, most people make the major mistake: they run with these numbers as if they are the truth. But these numbers are just data, they don’t mean anything unless we extract the insights out of them. To do that, we need to see why the numbers are like that.

To gain such insight, Aleksey uses various profiling tools. After pursuing some related questions (which lure him back into the spiderweb-encrusted days of Java 1.6), he concludes by making another point I adore:

most of the time, the straight-forward code is fast enough, so stop philosophizing about angels on the head of a pin, and get back to work. 99.9% of applications do not need a dedicated team of performance engineers; they need instead for their developers to focus on writing clear, maintainable code, and a little bit of measurement and tuning to file off the rough edges when the code fails to meet the performance requirements.

Here's the URL, in case you want to read the original post:

[fortunatelycoldengineer]

C language MCQ . . . . write your answer in the comment section https://bit.ly/48J8x0O You can check the answer at the above link at Q.no. 1

[duniailkom]

Pengertian ArrayList Bahasa Java beserta Contohnya

Dalam artikel duniailkom kali ini kita akan membahas apa itu ArrayList dan bagaimana contoh kode programnya. Selain itu akan dijelaskan juga perbedaan Array biasa dengan ArrayList di bahasa pemrograman Java. Pengertian ArrayList ArrayList adalah struktur data yang digunakan untuk menyimpan kumpulan data dalam bahasa Java. Berbeda dengan tipe data array biasa, ArrayList memiliki ukuran yang…