#y-shaped

Part of the Y-shaped James Hammett House on the Dorset Estate in Bethnal Green

INGKE 1054338 M12 Circular Connector Y-Shaped 5P/8P(2) Male Pins/Female Sockets(2)

Manufacturer: Ingke Technology

Monthly Output/Yield: 5000k

Product Category:Circular Cable Assembly

Part Numbe:1054338

Connector Style:Distributor Y-Shaped

Convert From (Adapter End):Male Pins

Convert To (Adapter End):Female Sockets (2)

Shell Size - Insert (Convert From):M12

Shell Size - Insert (Convert To):M12

Number of Positions (Convert From):5

Number of Positions (Convert To):8 (2)

Mounting Type:Free Hanging (In-Line)

Fastening Type:Push-Twist

Housing Material:Thermoplastic Polyurethane (TPU)

Housing Color:Black, Silver

Features:Coupling Nut

Ingress Protection:IP65/IP67 - Dust Tight, Water Resistant, Waterproof

Shielding:Unshielded

Current Rating (Amps):2A

Voltage Rating:30VAC/DC

Operating Temperature:-25°C ~ 90°C

Orientation (Convert From):A

Orientation (Convert To):A

Material Flammability Rating:UL94 HB

INGKE also produces substitutes such as: 1422850,1422848,1422847,1411046,1422852,1411066,1543236,1414586,1413991,1553624,1553653,1641785,1543223,1411044,1429143,1554513,1554526,1429130,1421679,1411068...

Welcome to contact me~mail:zita.ingke(at)gamil.com

Arancio Argos Lamborghini Aventador on PUR Wheels by SSsupersports on Flickr.

“Everyone has his own specific vocation or mission in life; everyone must carry out a concrete assignment that demands fulfillment. Therein he cannot be replaced, nor can his life be repeated, thus, everyone's task is unique as his specific opportunity to implement it.” Viktor E. Frankl 

“Why did I spend so much time thinking about the design of their corporate office space, or how the teams could collaborate and communicate better, or researching how unhealthy these products were; when my brief was specifically to design beverage packaging for them?” This is what I asked myself a few years ago to help me discover some common threads that existed in my thinking, and how I approached projects.

It didn’t matter if I was doing branding for consumer goods, or a customer journey for an airline, or furniture design, or fashion, or tech; there were some common themes I always tried to embed in the projects. The ‘what’ (the project) didn’t matter because I had a much stronger interest in ‘why.’ I wasn’t always aware or this, or consciously making these decisions, I think it was just part of my authentic self.

“Efforts and courage are not enough without purpose and direction.” John F. Kennedy

I first heard the term ‘T-Shaped people’ about five years ago when I joined Google. I liked it, I thought it made sense and was a good thing to consider as we worked on growing the team, but it didn’t connect with me on any deep level.

If you haven’t heard the term before, here is an explanation from wikipedia: 

The concept of T-shaped skills, or T-shaped persons is a metaphor used in job recruitment to describe the abilities of persons in the workforce. The vertical bar on the T represents the depth of related skills and expertise in a single field, whereas the horizontal bar is the ability to collaborate across disciplines with experts in other areas and to apply knowledge in areas of expertise other than one’s own.

The T-Shaped term and idea was first used in 1991. I’ve continued to hear and read about T-Shaped people, and how they are the desired type of person for todays work environment. I feel like we are missing something huge though. I think there is another way to look at other people, as well as how we look at ourselves.

To stay on the ‘letter’ theme, I’ve been thinking about the idea of ‘Y-Shaped’ people. A quick search shows I’m not the first to think of using ‘Y,’ but my definition probably differs.

The Y-Shaped person has a ‘why’ or purpose that runs through them, and through everything they work on or take part in. Their values, their over-arching beliefs and philosophies are a part of everything they do.

When I looked back at all my projects a few years ago, I realized I’m like this. I always had some consistent themes running through the projects I worked on. For work I was a designer, but I don’t mean themes that were driven by aesthetics or trends; they were/are themes driven by my interests, values, and ‘big-picture’ goals in life. 

I’m now much more aware of what consistently drives my thinking, and I make a conscious effort to apply them; but even before I was conscious of these themes, I couldn’t help but let the deep feelings and concerns become a part of everything I was doing. 

The Y-Shaped person struggles when they are doing things that go against their core beliefs and values; or when projects simply don’t feel like they are coming from a meaningful place to begin with. It doesn’t really matter how much they are get paid, or how respected they may be; something just doesn't feel right. The Y-Shaped person senses that the only thing we can’t catch up on in life is time, and the Y-Shaped person wants to use that time for things that align with their values.

The interesting thing is that unlike T-Shaped people, everyone is a Y-Shaped person; but many, maybe even most, aren’t paying enough attention to their values, and seeing how valuable it is to bring them to life in everything they do. 

At times it feels like the world is changing and starting to value this more, but there is still a deep rooted ‘system’ that seems to keep the ‘Y’ and the ‘why’ out of us. The education system, systemized tests, emphasis on memorizing and grades vs. learning and applying, resumes, job descriptions with 30 bullet points of ‘must haves,’ GPA, SAT, IQ over EQ, and on and on. It’s not surprising how few people bring their ‘Y’ to the foreground. But no one is a victim, we can all take steps to re-discovering our ‘why.’

There are many people moving us in the right direction. Simon Sinek’s book and TED Talk on ‘Start With Why,’ investment funds like Collaborative Fund focusing on mission driven companies, platforms like Skillshare who are facilitating education that starts with individual interest, Google admitting their focus on GPA for reviewing and hiring people had no benefits, the B-Corp business structure which only accepts mission driven companies solving social and environmental problems, and there are many other examples.

When the end goal is creating the highest quality of user experience possible on a mobile device, there's no debating the fact that native application development is the only way to go. But with at least four major platforms to target in a Bring-your-own-device world, each with its own platform-specific development kits and APIs, how can an organization effectively deliver mobile applications that are specifically targeted to each of the mobile platforms without completely blowing the entire IT budget?

The wrong approach to mobile development The wrong thing to do is to go all in and dedicate a team for each platform, but sadly, that's exactly what many organizations are doing. The end result is an inevitable duplication of efforts as separate teams independently develop essentially the same services and features as everything gets developed in parallel.

"Many organizations approach mobile by setting up independent teams," said Giles Alexander, lead developer and consultant who specializes in mobile application architecture and strategy at ThoughtWorks. "You'll have an Android team outsourced, your iOS team in-house, and then you'll contract to an entirely external team for BlackBerry or Windows Phone development. These teams are basically delivering the same features, but they're doing it entirely in parallel."

Anyone who has worked in the IT field knows that there's always a strong probability that any one application development project will fail. With four projects going on at the same time, your chances of any one project failing quadruples. Furthermore, with four different projects supporting four different platforms, fixing bugs and enhancing features become increasingly untenable as time goes on. Fortunately, though, there is a better approach, and more organizations are adopting it.

A new trend in mobile development In what is becoming a successful trend, forward-thinking organizations are moving away from a fragmented-by-platform mobile development process and are instead adopting a feature-based approach that stresses commonality. Divergences and differences between platforms only end up coming into play as UI development issues come into focus.

This evolving approach is known as the Y-shaped development method because the development stream looks more like the letter Y than it does a bunch of independent columns or silos that stand alone independently. "The Y-shaped delivery method aligns your teams along features rather than along platforms," said ThoughtWorks' Giles Alexander. "You don't restrict your teams to just working on the mobile front end, but you also allow the team to be aligned across a feature throughout the organization."

The end result is that one team efficiently develops a feature from end to end rather than four teams duplicating efforts. It certainly sounds more like common sense than it does a revolutionary idea, but sometimes common sense gets pushed aside in the frenzy of rushing mobile products to market.

Getting started with the Y methodology Given the sensibility of this methodology, how does an organization that's interested in getting its feet wet in the mobile development space adopt this particular approach? "You're probably going to have to pick some boundary at the back end to start," said Giles. "Say you have a set of services that expose the data that is critical to your product, and you want to deliver a new mobile feature around this. You should be able to put together a team that can work on those services and work on exposing those services in a way that is suitable for mobile. You then have that same team work on the UI and the actual delivery of those features into your Android, iOS, Blackberry or mobile web -- whichever you feel is most suitable to support." 

Of course, you can't completely ignore the reality that there are unique differences between the three or four most popular mobile platforms on the market. Furthermore, it's inevitable that certain members of a given team will have skills that align more strongly with either Android, iOS or Windows Phone. Any good development strategy needs to embrace this reality. This is where the linear-based, feature-driven development approach branches out a bit, giving us the idea of a Y-based development methodology. "There may be some division at the front end of the team. Some people may  prefer to be Android developers as opposed to iOS developers, so you may  end up with some slight division at the top -- hence the Y," explains Giles.