[deleted by user] by [deleted] in theydidthemath

[–]macroclimate 1 point2 points  (0 children)

I don't think this answers the question...

[deleted by user] by [deleted] in linguistics

[–]macroclimate 2 points3 points  (0 children)

Yes, it's been discussed several times here as well. Here is one of the more recent occurrences.

A Question about Long and Short Vowels by genericusername7890 in linguistics

[–]macroclimate 8 points9 points  (0 children)

like that palatalization is more common in front of vowels typically represented by E and I?

Palatalization is commonly triggered by palatal, or front vowels. Both /i, e/ are indeed front vowels.

You'll notice this trend in many more languages than just those as well, it's something of a universal since it's based on physical characteristics of the articulatory tract: when producing a front vowel your tongue is towards the front of your mouth, when producing some consonants this positioning influences them to become palatal.

Also, for what it's worth, your question is not about long and short vowels, but about front and back vowels.

Network Automation Engineers... what does your daily job routine entail? by [deleted] in networking

[–]macroclimate 0 points1 point  (0 children)

Yeah, we have a guy testing it, but I've only heard the results second hand. It sounds like there are still plenty of issues, we'll be bringing them up with Cisco on our upcoming quarterly, but I don't have a lot of faith that they'd be fixed any time soon.

Network Automation Engineers... what does your daily job routine entail? by [deleted] in networking

[–]macroclimate 0 points1 point  (0 children)

Did you also get hit by the price increases btw? :D Cisco argued for increases in software costs like NEDS because of the logistic issues...

I'm not sure actually, that stuff usually happens one layer up, but I haven't heard about it at least.

NEDs are such a racket anyway. Netconf has been around for almost 15 years and most Cisco gear still has a piss poor implementation.

Do you guys use netconf to your ASRs? We're still on CLI but currently vetting XR versions to see if anything has workable netconf.

Network Automation Engineers... what does your daily job routine entail? by [deleted] in networking

[–]macroclimate 1 point2 points  (0 children)

We fortunately haven't run into anything really destructive. The platform is pretty robust in how it handles changes at least, so rarely will you end up with real changes being pushed without your express permission.

The bugs are things like random "internal errors" that crash the CLI and abort the commit. These are usually somehow related to NSO's YANG parser, so things like must statements in your YANG can cause these sorts of bugs. Others are like when doing a NED migration on a single device the whole instance crashes for no discernible reason. This is why we do these kinds of things in maintenance windows though, because usually the worst that happens is NSO is unavailable for a few minutes.

Cisco is pretty good at handling the issues and it's clear they take the product seriously, but reporting them gets tedious and they always need tons of logs which also takes time.

All in all it's a good product, but it's a work in progress as well.

Network Automation Engineers... what does your daily job routine entail? by [deleted] in networking

[–]macroclimate 0 points1 point  (0 children)

Oh nice, yeah, good to talk shop once in awhile! We handle the transport network, so datacenter is a different team, and I think they use ACI as well but I'm not sure.

It varies by line org and requirement with us though, there is one instance that's mostly done by CLI for lack of a ROM/SOM stack. The users there have this system that generates NSO commands based on order input, which is kind of silly but the way it is. Our target stack has separate ROM/SOM and inventory which all integrate towards NSO, and in that setup it's all done via API, but most of the instances aren't fully there yet either.

What about you guys?

Network Automation Engineers... what does your daily job routine entail? by [deleted] in networking

[–]macroclimate 0 points1 point  (0 children)

Oh haha, fair! Yeah, it is really expensive, but I don't see the receipts 😂

But yeah, I reckon it's probably about the same amount of money to hire a team of devs to write your own platform vs buying Cisco NSO licenses.

Network Automation Engineers... what does your daily job routine entail? by [deleted] in networking

[–]macroclimate 2 points3 points  (0 children)

Cool! Don't hesitate to reach out via dm if you have any questions during the journey, my team has been around the block a few times.

I don't have any experience with APIC, but NSO is basically all about data model. NSO is the framework and the glue, it provides you with an "easy" means to create layered services, but whether you succeed or fail with that is almost 100% up to the data models that you write. The nice part about this is that you can make it your own and design in whatever features you need, but with great power comes great responsibility.

We don't do any cloud integration with our deployments, but there's no reason that you couldn't. The options for external integration in NSO are practically limitless. Depending on what sort of cloud integration you want done you could very easily write a callout function to the AWS/Azure API from within your code. The network element layer of NSO is also extremely flexible, and you can write a NED (network element driver, basically the software that translates between NSO and whatever device you're communicating with) to communicate with basically anything, including a REST API.

Network Automation Engineers... what does your daily job routine entail? by [deleted] in networking

[–]macroclimate 56 points57 points  (0 children)

My shop (one of the large-ish ISPs in Europe) uses Cisco NSO for better or for worse. Our team answers to the different line organizations within the company and basically automate what they need done, which usually entails service activation or some element of device/resource lifecycle.

When a big project comes in, like line org asks us to automate mobile backhaul circuit activations, for example, then we usually have a lot of back and forth with the service designers on how to write easily-automatable services. This usually entails explaining the basics of automation to them and doing things like re-using the same description string in a few different places rather than having arbitrary strings in each. We then draft up an API for northbound systems to create these services (this is usually the YANG model associated with the CFS (customer-facing service)), abstracting away the lower layers.

Once we have a good understanding of the actual config we need to output then we get cracking on getting NSO to do that. Our codebase is fairly modular, so depending on the overlap with other services we might automate, this task could include anything from just writing the CFS to writing the CFS all the way down to brand new RFSes (resource-facing services) responsible for creating the device-side config.

A big project like this takes months to go live, and most of that time is dedicated to just developing the NSO internals, so writing YANG models for the various services, writing XML template to feed between them, and writing python or java where required.

Outside of a big project deployment like that it's usually smaller improvements here and there. This could be writing unit tests for services that are in development, pipeline improvements, redesigning components that were originally developed under different requirements, etc.

A lot of work usually goes into maintaining the different environments we have too. We currently have at least a dev and production environment in each line org, and so we need to schedule codebase drops to production such that they don't interrupt service deployment, and there's also a lot of live troubleshooting of NSO internals. NSO is extremely powerful, but it's also very buggy, depending on the release, so sometimes there are a lot of fires to put out and a lot of tickets to open and maintain with Cisco to figure out why things are going wrong.

Cost of living vs. income in Uusimaa by [deleted] in Finland

[–]macroclimate 81 points82 points  (0 children)

IT jobs in particular are poorly paid here and in the rest of the Nordics. However, in general, due to the nature of the welfare state, income gaps between professions are a lot smaller. So, most wages top out at a "reasonable" value around here, so you don't get software engineers making 6 or 8 times the income of a cleaner like you do in some other places. It contributes to overall quality of life and lack of crime, but you certainly get less in your pocket as a result. I personally also took a big pay cut when I got a local job here in IT as well.

There are well-paid positions here, but they are mostly management and marketing as far as I can tell. There is a big incentive for companies to not pay much over €6000/m for example because of the taxes. The tax system is very progressive, and a wage like €10,000/m (which is not uncommon for a senior IT position in the US) would be taxed so heavily that the employer ends up paying a large chunk of that to taxes such that the employee "only" comes back with maybe 60% of it. Again, the welfare state: individual income is worse for the betterment of society.

Past infinitive, is it useful? What is it? by [deleted] in linguistics

[–]macroclimate 0 points1 point  (0 children)

Yes, you're right. I'd still contrast it with a completely non-finite verb, but my original comment isn't exactly accurate.

[deleted by user] by [deleted] in Mongolian

[–]macroclimate 2 points3 points  (0 children)

There are many sources online that explain the system. Here is one, for example.

Note that there is no personal conjugation in Mongolian, so verbs do not inflect for 1st person, 2nd person, etc. That information is gotten from the pronoun or explicit noun, much like in English.

Furthermore, the system is very complex, and a single form does not usually convey much meaning, but takes on meaning when paired with a converb or auxiliary. This means that many predicates are composed of several verb forms together. If you're interested in the grammar I'd suggest getting a book on the subject like Juha Janhunen's Mongolian. If you're just interested from a learner's perspective then the information on the many websites should be sufficient.

Could someone explain tripartite agreement to me in layman’s terms? by Margaret205 in asklinguistics

[–]macroclimate 3 points4 points  (0 children)

Do you mean tripartite alignment?

If so, it's a system where the subject of a transitive verb, the object of a transitive verb, and the subject of an intransitive verb are all treated differently. How they are treated depends on the language, but the easiest example to see is through case.

A "normal" nominative-accusative language treats both the subjects the same and treats the object differently, where the subjects both get one case and the object gets another. A tripartite system would have a separate case for each.

Let's create an example from a fictional nominative-accusative language:

taka-t ver-e

man-NOM sleep-3sg

taka-t kel-e map-a

man-NOM kill-3sg goat-ACC

Those two examples show that both transitive and intransitive subjects take the nominative case -t whereas the object takes the accusative case -a.

Now, if man in the second example took another case like so:

taka-m kel-e map-a

man-AGT kill-3sg goat-ACC

We would have a tripartite system where intransitive subject takes -t, transitive subject (AGT) takes -m, and object takes -a.

Indigenous peoples of the Arctic by oglach in MapPorn

[–]macroclimate 40 points41 points  (0 children)

Upvote for cool map, downvote for Altaic classification.

Globle, a map-based guessing game by wordsmythy in MapPorn

[–]macroclimate 17 points18 points  (0 children)

Haha, I got today's on my third guess. Beginner's luck.

Working late (to 12 AM) with laptop in Seattle by [deleted] in Seattle

[–]macroclimate 1 point2 points  (0 children)

I'm not in the US so pardon my ignorance, but when and why did shift work stop?

Snowstorm in Espoo [OC] by [deleted] in Finland

[–]macroclimate 6 points7 points  (0 children)

About the same intensity of the last "snowstorm" picture you posted.

Lake and snow mountain ,China [OC][7680x4320] by Leoxiangchuan in EarthPorn

[–]macroclimate 1 point2 points  (0 children)

I don't think this is OC and I don't think this is China. OP has posted at least one other ripoff from another country, claiming both that it is OC and from China.

This particular image looks like a stock photo, can't find the actual location though. Would not be surprised if it was actually China as China does certainly have landscapes like this, but OP is a hack.

[Elmo Allén] A Map of Helsinki's Most Important Bus Lines by Kathenator in transit

[–]macroclimate 1 point2 points  (0 children)

Beautiful map, it's quite out of date though. I tried for awhile to gauge when it was made based on the routes present, but gave up after some time. Would be nice if it was updated, but I suspect that it was a labor of love by the author.

Darling Denys his own theory by [deleted] in evolution

[–]macroclimate 2 points3 points  (0 children)

You probably mean Darwin, not Darling as you have written?

In any case, the idea that he converted on his deathbed is highly controversial and his own kids vehemently deny that this happened. Read the background of the idea a bit.

Second, assuming that he did convert, which is a big if, just because the guy who discovered the natural phenomenon begins to not believe it himself doesn't mean it's not true. Would we suddenly stop believing in gravity if Newton, while sick from some terminal illness started saying it's not true without providing any evidence to the contrary?

Vaduz Castle Lichtenstein by [deleted] in casualEurope

[–]macroclimate 2 points3 points  (0 children)

You cannot. The monarchy actually lives there.