As a Partner and Principal Consultant at Amick Brown, Arun is responsible for business development, maintaining trusted relationships with customers and providing solutions and direction. Arun served as a Solution Architect at AT&T and then Accenture with a focus on SAP ERP, Data Analytics and Technology Architecture. Arun joined Amick Brown to lead its first ever project and has since then worked with our partner companies helping to win and execute work for Amick Brown. Arun, along with the other Amick Brown partners, has been successfully working on the expansion of Amick Brown’s business into the public sector and the Cloud domain. He is also responsible for establishing and overseeing Amick Brown’s subsidiary, Amick Brown India.

Arun has all-around experience in the IT industry across functional and technical domains throughout his 24-year career. He has experience in functional areas such as Finance, Supply Chain, Human Resources and Real Estate providing support in Architecture, Strategy, Vendor Selection and ERP and Analytics Solutions. He has performed various roles covering the entire software development lifecycle and numerous technologies from the development and management of complex technology landscapes to the nitty gritty troubleshooting of technical issues.

Arun has been an avid hiker since his college days and continues even now with many hiking and backpacking trips. In 2019 he has done several hikes in the California Sierras including the feat of climbing Mount Whitney in one day. He has a keen interest in history, economics and the financial markets. He also likes to spend time on sports, cooking, winemaking and music. He is a hobby guitarist and enjoys playing rock, blues and jam music.

Arun lives in San Ramon, California, with his wife of 18 years and two children who are also budding musicians.

Follow Amick Brown at: https://www.linkedin.com/company/amick-brown-llc

Connect to Arun through  Arun’s LinkedIn Profile.  We hope to hear from you.

The post Get to Know Amick Brown! Meet Arun Sullia appeared first on Amick Brown.

Amick Brown has been certified by the US Small Business Administration (SBA) as an 8(a) Certified Small Business.  Entrance into the SBA’s 8(a) business development program was granted after Amick Brown successfully completed a rigorous application process to ensure that we met the SBA 8(a) program standards.

The 8(a) certification with its associated business development opportunities has a nine-year contract period and will allow Amick Brown to pursue sole source federal and state government contracts as well as set-aside contracts allocated to 8(a) certified companies.  We look forward to new opportunities to serve our customers in the government sector.

Anitha Brown, Managing Partner and Co-Founder commented saying “This is an exciting opportunity for Amick Brown.  Our company has had steady growth since its establishment in 2010.  Achieving 8(a) certification at this point in our history offers the potential for significant growth over the next few years.”

Amick Brown also offers the following technology services under GSA Schedule 70: SIN 132 51 – Information Technology Professional Services (NAICS 541511, 541512, 541513, 541519)

Amick Brown, LLC is an Information Technology consulting company providing IT consulting and staffing services with a focus on Cloud & Network Technologies, SAP and Business Intelligence.  We are also an SBA Woman-Owned Small Business (WOSB) and are certified by the Women Business National Council (WBENC) as a Woman-Owned Business Enterprise (WBE). We are an SAP Services Silver Partner and are IS0 9001-2015 certified.

The company was formed in 2010 by a team of experienced IT professionals. We are headquartered in San Ramon, CA and have an additional office in Sacramento, CA. Our experienced IT professionals support customers nationwide in the commercial and public sectors. Our team has mature processes, established infrastructure and the ability to scale which enables us to quickly provide resources matching our customer’s requirements.

The post Amick Brown, LLC Awarded SBA 8(a) Small Business Certification appeared first on Amick Brown.

Our decision to pursue ISO 9001 accreditation supports our commitment to providing high-quality services to our clients and to our goals of continual improvement.  We have developed our quality management system in order to improve overall performance, to maintain a high-level of quality with regard to our services and to focus on customer satisfaction.

To become ISO 9001 compliant, Amick Brown developed key process plans and documentation, a quality manual, measurement, communication and purchasing plans, as well as processes to track non-conformances and corrective actions.  We would like to acknowledge The Core Solution.com – ISO Experts for Small Businesses (www.thecoresolution.com) for helping us to understand the standard, providing training to our team and guidance as we built processes to ensure our compliance.

Amick Brown underwent two comprehensive audits by Perry Johnson Registrars, Inc. (www.pjr.com) in order to achieve the certification.  We are proud to say that there were no non-conformances noted.

We look forward to providing high quality services to our clients and to continual improvement.

The post Amick Brown Receives ISO 9001 Certification appeared first on Amick Brown.

The post 4 Best Practices to make your Storyboards more Dynamic and Appealing appeared first on Amick Brown.

The post Brainteaser: Storyboard or Dashboard…Self-Service or Managed…you choose appeared first on Amick Brown.

When you talk to someone who dabbles with OOP, you hear polymorphism, method-overloading, dynamic-dispatch, public and private methods. But these are not what set OOP apart from its predecessors. I am in no way implying that these are not significant additions that came out of OOP. These concepts are just derivatives of the bigger idea of OOP.

Encapsulation is the primary idea behind OOP. Encapsulation simply means bundling of data and associated methods.

Let me explain: Before OOP, computer programming was a series of instructions written one below the other. This is like a two-way communication. You, the developer, is telling the computer what to do in a series of instruction. The idea goes back to the 8th century Arabic mathematician al-Khwarizmi (which is where we purportedly get the word algorithm). This is all good if you’re writing a program to determine the greated common divisor of two numbers. But over time computers have gone on to solve bigger problems, and procedural programming just doesn’t cut it.

So let’s say you’re writing a computer simulated solar system. In a purely procedural language set up, you would write a big program called “solar_system”, which controls all the planets and the sun, with a main function ‘run_solar_system()’. On the other hand, if you write a program, one that is influenced by object-oriented paradigm, it would contain encapsulations of the class of planets, with particular instates of each of the planets.

Compare the two very simplistic example codes of how each one of them looks:

Procedural paradigm:

currentPosition = getCurrentPosition('jupiter')
gravitationalField = getGravitationalField('sun')
jupiterNewPosition = 
  getNewPosition(currentPosition, gravitationalField)

Object-oriented paradigm

jupiter.calculateNextPosition(sun.gravitationalField())

Notice that in the first case, solar_system is doing the calculations for all the planets – a one way communication. In the second case, the communication is between the planet and the sun – direct communication. This code, if well written can be extended between any two (or three of four) objects within the solar system.

It is true that the expressive measure of both the paradigms is identical. What you can write in the OO paradigm could just as well be written in the procedural one. What makes the OO stand out, is its readability.

The line of code in the OO paradigm can be read as “Let Jupiter calculate its next position based on the gravitational field of the sun). Compare that to the lines of code in procedural paradigm would read something like this: “Take Jupiter’s current position, and take the gravitational field of the Sun, and using both, do some calculations and determine the next position Jupiter ought to take.”

By extension of it being readable, OO lends itself to thinking in terms of how we perceive the real world. And all this is achieved primarily by a single concept – encapsulation. By making a class called Planets, and instantiating Earth and Jupiter as Planets, the programmer has enabled the individual objects to communicate with each other, rather than letting an overarching program do all the dirty work. A clean readable code, implemented by a clean and organized underlying objects.

The post Object oriented programming – by Ashith Bolar appeared first on Amick Brown.