Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
Can you please tell me what these lines of code do?
$sub_category = 0;
if (!empty($_POST['sub_category_id'])) {
$is_found = $db->where('type',PT_Secure($_POST['category_id']))->where('lang_key',PT_Secure($_POST['sub_category_id']))->getValue(T_LANGS,'COUNT(*)');
if ($is_found > 0) {
$sub_category = PT_Secure($_POST['sub_category_id']);
}
}I look forward to any assistance
In the article, I would like to describe a way to easily implement a simple heat map in an Angular application. For that, I will use two external libraries, which are going to be Leaflet.js and Heatmaps.js. Before the implementation of the heat map, I prefer to begin with a brief introduction to the libraries I mentioned above.
It is one of the most popular JavaScript libraries for interactive maps. It has over 30k stars on GitHub. There is an alternative to it such as OpenLayers. But in my example, I picked a leaflet.
At a recent Linaro Connect event that took place this past fall, Alexander Sack (@asacasa), CTO of Pantacor, delivered a talk on the Linux Distro and how it is relevant in today's embedded world of the Internet of Things (IoT). Alexander gives us insightful context on the birth of Linux and the embedded world, and where it is going today. He spoke on the history of the Linux Distro and drew parallels with how the embedded development ecosystem is changing. Much like the early days of Linux, the embedded Linux world also needs to embrace automation and take advantage of containerization in order to make infrastructure frictionless and invisible.
Alexander started us off with an overview of how Linux started and how it has progressed from a hobbyists/tinkerers platform to a reliable and secure OS that today basically runs the Cloud. From the early aughts (the 00s) and onward, there were many different distributions like RedHat, Debian, Suse, and others whose goal was to make Linux reliable, easy to use, and secure. These distributions were created by large, vibrant communities of developers who donated their free time to contribute to open source Linux projects. Even though Linux gained a lot of traction in those early days, it still took quite a bit of effort and technical ability to integrate a distribution before you could deploy it and use it on a server to run your applications.
Embedded developers haven't always followed the same path as traditional software developers. However, the introduction of cloud and cloud-native technologies like containerization is bringing these two groups together. Embedded developers seek the benefits of Linux and containers, and the proliferation of IoT devices means we need to expand talent in both directions.
In a recent interview with Mitch Ashley (@techstrongGroup) of TechStrong TV, Ricardo Mendoza (@ricmm), CEO of Pantacor, discussed his vision of bridging the embedded and cloud developer worlds together through an open-source platform with containers and DevOps for IoT developers.
Otomi, an open-source project from Red Kubes, offers developer self-service on top of any Kubernetes cluster. With Otomi, developers can deploy and manage applications, create Kubernetes jobs and cron jobs, create and manage secrets, and publicly expose services with only a couple of clicks. And all of this without writing any Kubernetes YAML manifests.
The ultimate goal of developer self-service is to have less friction in the development process and ensure that developers can deliver customer value faster. This can be achieved by enabling the separation of concerns for both dev and ops teams. The ops team manages the stack and enforces governance and compliance to security policies and best practices. Dev teams can create new environments on-demand, create and expose services using best practices, use ready-made templatized options, and get direct access to all the tools they need for visibility. Think of it as paving the road towards fast delivery and minimizing risks by providing safeguards and standards. Developers can do what they need to do and do it when they like to. And yes, sometimes not always how they would like to do it. The only challenge here is, building a platform like this takes a lot of time and not all organizations have the resources to do so.
Some modern object-oriented languages have the concept of indexers, which are properties that allow you to index instances of a class just like arrays by using the [] notation. In this article, I would like to show you how to do it in modern JavaScript.
Here’s an example in C#:
In the video below, we take a closer look at RESTful Web Services and how to create a context path for Spring Boot application or Web Service. Let's get started!
Many enterprises have IBM Integration Bus environments running hundreds of integration flows in production. You have likely read about the benefits of moving to containers, perhaps even more generally of agile integration, and you’d like to explore that. You’d also like to move to a more recent version of the product (now named IBM App Connect Enterprise). However, it is likely you have no, or at least a very limited background in container technology. How do you take the first steps to explore these new platforms and product versions?
In this series, we are going to describe how you move to containers running IBM App Connect Enterprise. We’ll build up to more complex examples, but for this first one we’ll take the simplest possible flow, and we’ll use a Docker container environment that can easily be run on a laptop.
In our last article, we introduced how TiDB Operator orchestrates control loop events to manage the lifecycles of TiDB components. The TidbCluster controller manages TiDB components' lifecycles, and the member manager of each TiDB component encapsulates that component's specific management logic.
In this post, I'll explain in detail how we implement a component control loop by taking PD as an example. You'll learn about the PD member manager and its lifecycle management operations. I'll also compare other components with PD and show their differences.
Recently, I read an article outlining how to create CSS pixel art with box shadows. I thought it was a really cool idea - and thought it'd be interesting to make a generator to let you create exportable pixel art from the browser using this effect. In the Codepen demo below, you can draw your pixel creations, and then click "Generate CSS" to get your pixel art in CSS, which you can copy into your web pages. Works better in full screen!
As described in the article, we use scaled-up box shadows to act as pixels on the screen. We can scale these up and down to make our pixel art bigger or smaller.
SLIs, or service level indicators, are powerful metrics of service health. They’re often built up from simpler metrics that are monitored from the system. SLIs transform lower-level machine data into something that captures user happiness.
Your organization might already have processes with this same goal. Techniques like real-time telemetry and using synthetic data also build metrics that meaningfully represent service health. In this article, we’ll break down how these techniques vary, and the unique benefits of adopting SLIs.
A team retrospective is a meeting at the end of a sprint, project, or milestone where the team reflects on the past work cycle and identifies improvements. It involves celebrating achievements to raise the team spirit, gathering feedback on challenges, and planning how to execute better in upcoming sprints or projects. Retrospectives are essential for continuous improvement and team growth.
Retrospective meetings are structured to facilitate team discussions and beneficial outcomes. They usually start with an introduction, then input from each team member is gathered, presented, and discussed, and finally, the next steps are determined. Gathering input usually happens in parallel. Guided by the questions of a retrospective format, each team member writes up their thoughts on sticky notes and puts them on a whiteboard (or the digital equivalent in remote meetings).
I have worked with two different kinds of leaders and managers over the years. The one who believes in fixed abilities and promotes a fixed mindset “those who don’t perform well can never do better” and the other who believes in growing those abilities thereby promoting a growth mindset “people can be coached into improving their skills.”
The first kind engages with the workplace to boost their self-esteem, establish their superiority and prove their smartness. They focus on their employees' weaknesses, refuse to coach them, blame others for failure, do not seek feedback, divide people into competent or incompetent and hire for natural talent instead of looking for ways to grow talent within their organization. They praise people for their intelligence while failing to take notice of those who show improvement through effort and hard work. After all, their fixed mindset leads them with the belief that people can’t get any better, and that makes them stick with their initial impression about them.
Outages on the Internet always catch you by surprise, whether you are the end user or the Head of Site Reliability trying to keep a clear mind while you execute your incident playbook.
As people in charge of ensuring reliable services for our customers, our normal experience of outages involves surfing a deluge of fire alarms and crisis calls as we work to solve the problem as quickly as we can. We often forget, therefore, what an outage means to the end user.
Every day, the ProgrammableWeb team is busy, updating its three primary directories for APIs, clients (language-specific libraries or SDKs for consuming or providing APIs), and source code samples.
