#vtpl

Hit And Run Captured in Delhi   Follow Traffic Rules

Veridic Technologies Pvt Ltd

Veridic Technologies Pvt Ltd Reviews

Multiple parent selectors make for cleaner code – here are three ways to use them.

The internet is brimming with web design inspiration and tools to aid your web projects, which is helpful as designing for the web can get tricky. Making life as easy as possible is the key.

Veridic Technologies Pvt Ltd

Multiple parents make stylesheets much more terse, which is always nice. It reduces filesize and maintenance, so it’s something we’re definitely interested in. Here are three ways to use multiple parent selectors.

01. Preprocessors

Currently, the most obvious solution is to use a preprocessor’s in-built nesting functionality to list our multiple parents, then nest our one child in it. This still compiles out to relatively verbose CSS, but it is nice and terse in our source.

Veridic Technologies Pvt Ltd Reviews

02. :matches()

There’s a pseudo-selector in Selectors Level 4 that provides this natively. :matches (or :any , in older specs) allows you to write much more terse selectors, which the browser expands internally.

Veridic Technologies Pvt Ltd Facebook

03. cssnext

To get :matches() working requires a little extra work. It’s actually referred to as :any() in older specs, and requires vendor prefixing. To this end, I’d recommend using cssnext to transpile the new syntax back to better support.

The logo shapes used by big brands aren’t chosen by chance – we offer a primer in the psychology involved.

When it comes to developing a brand, logo design is king. The power of a logo to elicit an emotional response can have a resounding effect on the way customers and potential customers view a particular product, service or company. A powerful logo may look simple but there’s nothing simple about creating effective logo shapes.

Be aware that the logo shapes used to portray the most visible brands in our culture have not been chosen by chance – there are some powerful psychological forces at work. In this article we’ll take a look at how the informed use of shapes can be used to give your logo the desired resonance.

Veridic Technologies Pvt Ltd

How humans view logo shapes

Our subconscious minds respond in different ways to different logo shapes. Straight lines, circles, curves and jagged edges all imply different meanings and so a skilled logo designer can use shape to infer particular qualities about the brand. Think, for example, of the Nike Swoosh: the combination of curves ending in a sharp point offers a strong suggestion of movement.

Particular logo shapes send out particular messages:

Circles, ovals and ellipses tend to project a positive emotional message. Using a circle in a logo can suggest community, friendship, love, relationships and unity. Rings have an implication of marriage and partnership, suggesting stability and endurance. Curves on any sort tend to be viewed as feminine in nature.

Straight edged logo shapes such as squares and trianglessuggest stability in more practical terms and can also be used to imply balance. Straight lines and precise logo shapes also impart strength, professionalism and efficiency. However, and particularly if they are combined with colours like blue and grey, they may also appear cold and uninviting. Subverting them with off-kilter positioning or more dynamic colours can counter this problem and conjure up something more interesting.

It has also been suggested that triangles have a good association with power, science, religion and law. These tend to be viewed as masculine attributes, so it’s no coincidence that triangles feature more prominently in the logos of companies whose products have a masculine bias.

Our subconscious minds associate vertical lines with masculinity, strength and aggression, while horizontal linessuggest community, tranquillity and calm.

The implications of shape also extend to the typeface chosen. Jagged,angular typefaces may appear as aggressive or dynamic; on the other hand, soft, rounded letters give a youthful appeal. Curved typefaces and cursive scripts tend to appeal more to women, while strong, bold lettering has a more masculine edge.

Veridic Technologies Pvt Ltd Reviews

How to apply logo shape psychology

Before you start designing a logo for your client, write down a list of values and attributes that the logo should convey. (This is one of the reasons you need to get to know your client and their business as well as you possibly can.) Ask your client to compile a list of corporate values or take a close look at their mission statement.

Veridic Technologies Pvt Ltd Facebook

Once you have a feel for the message the logo needs to disseminate, you will be able to look at how to match this up with not only logo shapes, but also colours and typefaces as well. Use these three elements in combination to your advantage: for example, if you pick a strong shape but find it too masculine, then introduce a colour or colours that will tone down the male aspect.

Gestalt theory

To extend your use of psychology to a deeper level, brush up on the Gestalt theories of German psychologists from the 1920s. They hold that the human brain unifies the visual elements it sees to form a whole that carries significantly more meaning. People form patterns out of similarly shaped objects, while objects that differ from the group become a focal point of the image.

Another Gestalt principle, closure, is often used in logo design; this is when an object is incomplete but there is enough detail for the human eye to make the whole picture. A good example of this is the panda logo used by the WWF, shown above.

The logo shapes you incorporate into your designs become an intrinsic element in the message they will convey to the company’s customers and the wider public. Once you understand the psychology behind logo shapes you will be able to use this knowledge to create powerful brands for your clients.

Disappointment occurs when expectations don’t match reality. And our expectations for software quality are profoundly unrealistic. Thus, lots of people are continuously disappointed — even enraged — by software bugs. They shouldn’t be.

The only reliable, widely used way to ensure impeccable software quality is to write less software that does less stuff, and then spend eons honing that tiny lot. Such an approach, however, is very rarely compatible with commercial success or even programmer motivations (despite what many may claim).

How do you think the market would receive the iPhone 7, if its headline improvement was cutting 1/3 of the features to shrink the code base so it’d have fewer bugs? Yeah, I thought so. While people may get excited in concept by “stop the train, we need to fix the tracks” directives for software development, it’s not what they would buy.

Well, but then there’s the argument: Apple is so rich, can’t they just hire more developers and testers to fix all the bugs? To paraphrase Frederick Brooks: No. Software development doesn’t work like that. Throwing ever bigger teams at problems usually just makes the problems bigger still.

Bugs are an inevitable byproduct of writing software. Sure, there are all sorts of techniques and potions that promise to decrease how many of the damn critters run about, but only the comically hyperbole pretends that complete eradication is possible.

Once we accept that simple fact that software = bugs, we can progress to understand why fixing them may not even be that important a lot of the time. The absence of bugs is simply one parameter of success in software, but not even close to the most important one (with some exception for life critical systems).

Useless software can be entirely bug free, yet remain entirely useless. Useful software can be ridden with bugs, yet remain highly valuable. Or, the value of software depends far more upon the problem it solves than the quality by which it does so.

Veridic Technologies Pvt Ltd Facebook

Sometimes the dichotomy isn’t that black and white, of course. You could have two pieces of software that solve the same problem, and it’s reasonable to think that the one with fewer bugs would do better. Though even that simple statement is often laughably disproven by the market. Factors such as existing adoption, integrations, brand, and fun often trump quality as well.

Given that there are so many factors more important to the future prospects of a software package and its makers, is it really that surprising not every bug gets “drop everything, we gotta fix this” priority? Of course not. But we, as users who hit a bug, still constantly pretend that it is.

It’s really the pinnacle of myopia when we as users demand and demean software makers to fix our pet bug, just because we hit it, and just because it may have caused anything from a slight annoyance to loss of some time.

The value of a any given bug can be rated by the number of users affected times the criticality of the issue. Lots of users are losing all their data due to this bug? Okay, then, Very Damn Important! Fix it NOW! Lots of users are a little annoyed or confused by this? Probably should fix it some time soon. A few users have to spend another 30 seconds on a work around? Unlikely to get fixed any time soon!

Software organizations that stay in business triage their backlog of bugs like that. They do not drop everything to deal with any damn bug. As the economies of scale kick in, so does the magnitude of consequences from such triaging. Large software packages and organizations will have hundreds if not thousands if not TENS OF THOUSANDS of open bugs of various criticality. THIS IS NORMAL. THIS IS EXPECTED.Veridic Technologies Pvt Ltd Reviews

This is not a call to give up on software quality, quite the contrary. This is a call to remove the highly charged emotional responses of encountering the world as it should be expected to spin. Demeaning developers, questioning their professionalism (whatever that means!), or feigning outrage at that which ails all software makes everyone, including users, worse off.

So next time you hit an annoying bug, give it five minutes before you fire off that indignant tweet. Marvel at the miracle it is that anything as complex as a modern piece of software works at all! Consider the billions of instructions our work-horse CPUs have to get just right for you to enjoy the splendors of computing. Have some sympathy for man and machine.

Veridic Technologies Pvt ltd Facebook

This is a walk-through of the steps I personally took in a single year, to begin learning JavaScript. My goal was to be able to get a job in a position where Javascript would be at the forefront of what I do on a daily basis.

I should make it clear that my journey wasn’t as smooth as what I’m about to present to you, this should give you a much smoother ride. The inspiration for writing this article is that I’ve been asked how I’ve gotten to the level I’m at in JavaScript in just under a year. (Currently working full time as a javaScript developer at BSkyB.)

When I started it would have been great to have a pointer toward relevant information and resources to get me on my way. The hardest part for me was the middle ground. There are plenty of resources for beginners and for advanced but the intermediate content was a harder to come by, so I will make sure to include what I did there.

Veridic Technologies Pvt Ltd Facebook

One last point before I start is a massive disclaimer, I’m by no means at an expert level and I’m still learning lots but I also don’t foresee that learning progression about to stop anytime soon. When it comes to coding no one is the best and if you really enjoy it you’ll always keep progressing.

1.

Enter this journey with an open mind and no preconceptions on how you can utilise what you already know about coding from another language.

I say this because I don’t have a massive coding background. I was a freelancer for quite some years and like a lot of freelancers I just knocked out websites using WordPress. So I had very basic knowledge of PHP, lots of CSS, and HTML5. That is my background but a lot of people come from a strong coding background and when they come to JavaScript they try to implement the patterns they have learnt and incorporate them into JavaScript. Doing this I feel is not utilising the true power and nature of JavaScript.

2.

Now lets learn some basics, first port of call is to do something interactive. You could jump into a book like JavaScript: The Good Partsby Douglas Crockford (which I did!) but to me the book was a little too intense as a starting point. There are a couple of good online interactive courses and the one I chose wasCodecademy.

Once you start, you are faced with an application that looks a little like a code editor. Tasks need to be completed to proceed to the next level.

You get a good amount of basics learnt here, but more importantly you are actually coding and see results. This is key factor because actually coding is paramount to learning and far more effective than just reading books.(reading books/tutorials is a must but try typing out what you are learning)

3.

“You don’t know JS” book series by Kyle Simpson were a big part into actually learning relevant information about JavaScript. All the books are on Githuband free to view! Making the series open source and allowing the community to get involved in the outcome prior to being printed is a key part to the credibility of these books. Currently having 102 contributors, 253 closed issues, the level of scrutiny the content went under gives the series strong trustworthiness.

Since reading them heavily and regularly going back I’ve gone and bought the books I most used as hardcopies. Doing this means I have them for offline reading and more importantly I hope I was able to support Kyle with his continued good work.

Up & Going is a superb introduction and where you should begin reading this series. What I’ve found great about the book series is the way everything is explained. You don’t just get told how something should be done and nothing more. You get told why and an in-depth background into the subject. When going through the literature you get a confident feeling that what you are learning has been thoroughly thought out due to its open source nature.

You are going to get a nice introduction into the language with subjects such as: Values & Types, Objects, Arrays, Functions, Built-In Type Methods, Coercion, Truthy & Falsy, Variables etc…

This You Don’t Know JavaScriptbook series offers a contrary challenge: learn and deeply understand all of JavaScript, even and especially “The Tough Parts”.

4.

Next back to YDKJS book series and getting an understanding into Scope & Closures.

When going through the book, as mentioned before it is a good idea to test what you are learning and you are given plenty of opportunities to do so by the author. For this I went towards JsBin. You get 5 panels, HTML, CSS, JavaScript, Console and Output. The link I’ve given you will bring you to a page with JS + Console panels open. This way you can test code straight away and see the output, look at screen shot bellow for an example.

5.

So you’re learning more and more, testing code out. What I did next was to try and be a part of the JavaScript community. I joined Twitter andGithub.

Twitter was to start following influential JavaScripters + blogs + news sites here are a few to get you started: @getify, @_ericelliott,@BrendanEich,@holtbt, @jhusain, @andrestaltz, @drboolean and my self if you feel the urge! @_cmdv_

Github is a superb place to look for examples of code, to see how others are doing it and numerous other tools/frameworks/libraries that talented people make. It’s also a good way to start sharing what you do or even collaborate with others. Open source I feel is marvellous for the whole ecosystem, in what ever language you are doing. Some still feel it is a bad idea but I’m all for sharing my knowledge and using or contributing with others.

6.

Around now I was reaching the dreaded intermediate stage I briefly mentioned at the beginning of this article. I felt I was learning the basics but was just unable to think of how I could progress from here.

This is when frameworks came into light, lots of hype, talk of how easy they are to use and all the great things they can do. At the time Angular seemed like a good choice, it had a strong community. I’d be able to get a lot out of the box and actually start making things, I also dabbled in Ampersand.js.

Taking this choice for me was a slight time waster, not because the Frameworks are bad ones but I’ve come to realise that Frameworks come and go so often in JavaScript that picking one might not be the right direction to take. I then realigned my goals and felt that I wanted to learn how these Frameworks work under the hood! Optimistic I know, but in my eyes if you learn vanilla JavaScript then your skills/knowledge will stretch much furthers and for a longer duration than putting all your eggs inside a Framework.

I felt as if I was failing and finding it difficult to reach where I wanted to be, in reality I was being impatient. I did watch this magnificent video by Milton Glaser on the whole subject of failing and if I’m honest I still do. When dealing with a flexible language like JavaScript be ready to see endless options and opinions! So try not to get disheartened and try to think of the bigger picture. (Easy to say I know!)

7.

You have to remember at this stage, you actually have some great tools under your belt due to reading the two YDKJS books and playing around with the code. What next? For me it was video tutorials.

It came apparent that Kyle Simpson was also a teacher and he gave talks as well as various courses. In comes Frontendmasters.com, I know the name might make you think that it will all be front-end related but trust me it really isn’t. The course in particular I’m talking about is Kyle’sAdvanced JavaScriptif you are a Pluralsight member it can also be foundhere.

There are free alternatives like continuing to read the YDKJS book series, but for me watching someone talk about a subject and have them walking you through the code is fantastic for knowledge retention. What’s great about the Frontendmasters video courses is they have a running theme to encourage you to follow along coding at the same time! But what is even better is you have the advantage of pausing and rewinding if you get stuck.

You have to remember the people giving these courses are knowledgable/experts and for me paying to access that felt right. Because of all the expenses it cost to actually get the video content out there, it’s only fair that there is a fee.

The course I pointed you to goes hand in hand with the first two YDKJS and the third This & Object Prototypes. Watch the course and work your way through the books too. I’m still going back to This & Object Prototypes book because the content is so useful. Look out for OLOO (objects linking to other objects). This will explain my early mention of how keeping an open mind will allow you to use JavaScript to its full potential rather than implementing patterns from other languages like the use of “class”. Here is an article that covers the issues with ES6 class.

But keep in mind that these are opinions and people also make great arguments towards the use of Class, it will ultimately be a personal choice.

8.

Eric Elliott has put together a vast list of Essential JavaScript Links. I advise you take a good look through this list as its content is really great. There is also lists of great news sites, people on twitter, videos etc… I’ll pick out a few articles that will be more relevant at this stage of your journey.

The Two Pillars of JavaScript Part 1: Prototypal OO

The Two Pillars of JavaScript Part 2: Functional Programming

Now we’re starting to delve into deeper subjects combined with online videos this was how I got through this intermediary section of our trip.

Eric Elliott always give endless great content, with either his own or pointing to great content from others, he also has a course in the makinghere which might be of interest.

Right about now I took a shine to functional programming but I wasn’t aware at the time that functional programming was what I was actually learning. This may seem a little too in-depth but with your openness the more you look into the subject the more it will become clear why it is very useful. If you don’t feel this is the right direction for you then not to worry as I also took an offshoot.

Asynchronous Programming: The End of The Loop by Jafar Husain on egghead.io is a low level introduction into functional programming and there’s more to come on that subject but firstly lets take that offshoot.

9.

You might have noticed but incase you haven’t already come across it. Most current JavaScript libraries, plugins and frameworks are on a package manager called NPM, Ruby has Gems, PHP has Composer. To get full use of NPM you will need to have NODE.js installed here is a quote from the node site.

Node.js® is a JavaScript runtime built on Chrome’s V8 JavaScript engine. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient. Node.js’ package ecosystem, npm, is the largest ecosystem of open source libraries in the world.

The lowdown is that Node allows you to run JavaScript on the server and this opens up endless options to the JavaScript world.

If you want to go a little more in depth then you can look at a paid course on both Plurasight + Frontendmasters.

10.

If you’ve reached this point you’ll be in a good place to start experimenting with vanilla JavaScript in an application environment. As I said previously I kept away from Frameworks but that’s not to say they are outright a bad thing, so I put my investigative boots on and went hunting for a potential option!

My findings were that React ticked all of my boxes, firstly it isn’t what I deem a full Framework because in reality it will only deal with the view layer and the rest of the app implementation is left to you.

It teaches great implementations, like modular components how to deal with state (generally pointing towards a global state passed through the app in props). You’re not restricted to using all things React. You can use what ever to deal with your data layer, backend, api etc… And more importantly if you know JavaScript you are in a really good place with React. Again back to some great video courses when it came to learning React.

Ryan Florence is a strong speaker and funny too so that makes it a little more entertaining. Initially I took the course on ReactWeek which was a 5 day course. I discovered and took the course once it had already completed as it was recorded. Though it is a very good course I’ve had trouble with playback of the videos and after trying to get help, a couple of email exchanges down the line I was just ignored because in their eyes my internet connection was the problem! But fear not they told me I was apparently the only one to suffer this issue! Ryan did a similar course though shorter on FrontendMasters. You will be surprised at how easy it is to get up and going when you know JavaScript with React.

11.

Now you could choose to continue reinforcing what you have already learnt or find new things to learn. I personally took a shine to Functional programming along with a library called RxJS by author and SourcererMatt Podwysocki.

This all happened from taking a course presented by Jafar Husain, he is a very genuinely enthusiastic teacher. That to me is when I learn the best, if you are watching/interacting with a person who loves what he is doing it shows and you naturally become more interested. I know it sounds like I was paid for this testimony but trust me this all came out of my own pocket!

Unfortunately the course I’m talking about is due for release on FrontendMasters as I took it live a couple of months ago and it takes that time to get up onto the site. (It’s now been release and available to watchhere!) Not to be a an awful tease here is another great video about the exact subject though not as in depth from Jafar.

For more knowledge on RxJS Ben Lesh’s tutorials on Egghead.io are an insightful way to get your teeth into RxJS, there a couple of new ones fromAndré Staltz.

I should mention that RxJs have a great gitter channel too, you’ll need Github to join but they are a really helpful bunch.

12.

I’ll make this the last step as this is really just going in the direction I have taken when really at this point you will be able to choose which direction you’d like to take.

The last video by Jafar gives you a good introduction of some functional programming concepts but you can dive in much deeper and this is what I’m doing right now. Here is a great book Mostly Adequate Guide byBrian Lonsdorf, he also did a course on the subject here

Functional programming is such an interesting subject and I’m sure I’ve unearthed something that will keep me busy for quite some time but like all things programming don’t ever expect to be completed!

André Staltz has also been working on a very interesting project calledCycle.js which combines functional programming and RxJS! I’ve not fully investigated it yet but so far it was a blast to use and if you like React then this will be right up your street.

Finally we’ve reached the position I’m now in, maybe my passion helped me a lot when it came to learning so much in so little time but please don’t think all this information is set in stone, I regularly keep going back to subject I hit near the beginning of the course and I try to do more and more github repos. But I’ve only just recently come into an actual working environment so this is where my knowledge is really getting tested and I’m sure I will trip up a load but I’m prepared to learn from my failures as well as my peers and continue on my mission.

“It has been mentioned that I failed to mention testing and TDD

Testing is really important part when you start to code bigger applications or join a team. I was lacking in this area and since having joined a team I’ve spent a lot of time trying to learn testing/tdd/bdd in JavaScript. I really want to get into TDD but it is going to have to be a long term thing as you only get to reap the benefits when used constantly. Hopefully soon!

5 questions every unit test must answer

Why I use tape instead of Mocha and so should you

TDD React resources

Testing React Suite

Thank you for getting this far and to @deadlyhifi for the proof reading.

Good luck on your journey and I hope this has been an aid.

Working on very different projects, in different teams and with different people can sometimes be a challenge. But one thing that works out remarkably well is doing retrospectives with your team.

In retrospectives, you talk about how a certain project went, and the whole team shares what problems/challenges they faced, what was good and what was annoying people, why people were unhappy. And after each person has written this down on a wall (you can use Post-Its), you try to find useful solutions, small improvements that avoid conflicts, that avoid people feeling bad in a project, and that avoid unnecessary stress situations. Ideally, you do this often — like every two weeks. In every team so far, talking about issues and addressing them has helped to bind the team together and improve future work. Let’s work more together in our teams instead of on our own. Veridic Technologies Pvt Ltd Reviews

Concepts & Design

Link

We often complain about infinite lazy-loading of elements on a page but what do actual users think about such features in comparison to an old-school pagination? Christian Holst researched it for online shops and wrote up the effectiveness of modern UX elements.

Tools

Link

Zach Holman summarized “basically everything he knows about deployments,” with the goal of making the deploys of your project as boring, straightforward, and stress-free as possible.

Security

Link

Maybe not surprising but still as bad as it sounds: Many ad networks allow code execution and are vulnerable to XSS attacks, as this research by Randy Westergren shows. I really hope that ad networks will spend more effort on finally fixing their data leaks, security and privacy issues.

If you’ve been thinking to just connect to a SSL VPN to be more secure or anonymous, I have bad news for you. A recent survey showed that about 90% of all SSL VPNs out there are hopelessly insecure, and are feigning security to its users that isn’t there. So double-check the VPN before using it and if you’re in a company VPN, let them check the network for the security problems mentioned in the article.

Web Performance

Link

Yoav Weiss clarifies Preload, a relatively new specification to define custom loading logic without suffering the performance penalty that script-based resource loaders incur.

Bruce Lawson explains why he personally thinks ad blockers are important. While that is just another opinion, it also reveals some lesser known problems of advertising these days. The major point here being the cost of large JavaScript files, graphics and banners that matters way more in developing countries than in our cheap-data-plan countries. Notably, he also mentions that we finally need to find alternatives to displaying ads to gain money from publishing content on the web.

HTML/SVG

Link

There’s a lot of confusion about whether you should includewidth/height attributes for responsive SVG files. Sara Soueidan shares why it’s still a good idea to use sizing attributes for SVG elements in a clever way and then enhance the responsiveness via CSS later on.

Accessibility

Link

Georgie Luhur shares the basic concepts of how to use ARIA with your existing markup without spending much time on it but bringing great benefit to your users.

Do you know what it feels like to read a text if you have dyslexia? Dyslexic people can read text, but it takes them a lot of concentration, and the letters seem to “jump around”. Here’s a demonstration that simulates Dyslexia. And now imagine how difficult this must be if there’s not enough contrast or a movie playing in the background.

Veridic Technologies Pvt Ltd Facebook

JavaScript

Link

What’s new in jQuery’s version 3 that will be released soon? for … ofloops, requestAnimationFrame for animations, and many more cool changes. Check out the most important innovations of jQuery 3 here.

Work & Life

Link

Estimating a web development job is very hard, especially in front-end where you have so many variables. But with some clever tricks you canachieve a better estimation and cost proposal by splitting things into small tasks and by creating user stories.

It’s not a new finding but still so many start-ups and companies think that people are more effective if they work longer. The opposite is the case, and it’s hurting creativity, productivity and the work-life balance of employees.

And with that, I’ll close for this week. If you like what I write each week, please support me with a donation or share this resource with other people. You can learn more about the costs of the project here. It’s available via email, RSS and online.

Thanks and all the best, Anselm