The find command is a pretty basic utility, but it does have loads of options, which
may be intimidating at first, but keep in mind it has about every criteria you would
possibly need when searching for attributes of files or directories.
It is also the standard way to search files/directories by criteria like name,
date created, size, permissions, user, and more.
The syntax and options may seem irregular compared to other commands,
but I’ll show a few examples:
If you want to schedule a program to run on a Unix based OS, there are
a handful of options, but the prominent ones found on Linux are
cron and systemd timers.
Initially released in 1975, cron has stood the test of time when it comes
to running a task on a schedule and it continues to be the standard solution
for all kinds of users.
How does it work
There is a file called crontab which tells the cron daemon what to run
and when to run it.
For non-commercial purposes documentation or on a website) that reference your connection with Microsoft PowerShell.
Things To Know About PowerShell
First and foremost, PowerShell is unlike traditional Unix/Linux shells such as bash or zsh.
It is explicitly object oriented and the most of the benefits come from the
fact that the majority of “builtin” commands (also known as cmdlets) and
everything related to input/output comes in the form of
objects which in turn have members, methods and inheritance.
This way data is more “structured” compared to shells that deal with plain text.
Browsing the web involves lots of different protocols that most people probably don’t consider.
DNS is one of those protocols, so in this post, we’ll briefly go over the basics of DNS, why browsers
are switching to DNS Over HTTPS (DoH), and how to get public DNS Records.
What is DNS
The core function of DNS (Domain Name System) is to associate Domain Names to IP Addresses and vice versa.
The concept is deceivingly simple, and incredibly useful.
Dear Reader:
This post is aimed at beginners so if you are already familiar with how APIs work,
you might not get much from my explanation, but you are welcome to skim.
One of the most common activities a Web Developer will do is fetch data from some API,
parse it, and then do something with that data, like displaying it on the page.
Reading input line by line is something that seems like a basic and banal
operation, but it’s not really as basic as some higher level languages
make it out.
Let’s look at a couple ways we can do this in Bash and other languages like Python and C.
Bash
The syntax of bash always seems a bit awkward.
For this example, assume we have a file called test.txt and we want
to echo every line.
Documenting your code is incredibly important.
Not only does it help your future self understand, but it also helps others find their
way around.
This post will be talking about some of the tools developers can use to generate docs
for their projects.
The Premise Is Simple
There are a plethora of tools out there that allow you to create, organize, and serve documentation,
but they are all more or less based around the same core concept, which is this:
This game can be complicated to explain to people, but I’ll try my best. It would be impossible to say I don’t have mixed feeling about it, due to super divisive gameplay. As a whole though, I think I enjoy it more than I loathe it and despite the numerous flaws, I still come back.
The best way to describe this game to someone is “oddly satisfying”. Planning routes through rough terrain, hauling massive amounts of cargo and fighting mules that try to steal it are highlights for me personally, and are what I found to be the most enjoyable. I wish there was more of it. The tedium is unavoidable though. Once the novelty wears off and you start to go through an area time after time hearing the same lines from the prepper’s it gets super repetitive. Once you get a feel for how the BT’s work, it just becomes a roadblock to slow you down. Also the boss fights are extremely easy, but they are the best the most efficient way to clear an area out of BT’s.
I wanted to make some points on why I think it can be worth it to look at older technology compared to what is more current.
You get to learn from the mistakes/success of the greats.
You can see the limitations of technology from a certain time period compared to now and how it would be different today?
As software and hardware gets more mature, more people and more projects come to depend on it.
The new becomes the old and vice versa. Many ideas are perpetually rehashed and adapted to fit current needs.
I would encourage everyone to think about all the technology they use everyday and base their opinions on it’s merit instead of it’s age or popularity.
