Recent comments on posts in the blog:

RSS Atom
Games
If you’re selecting a platform for casual games, consistency matters more than design or promotions. Chicken Road Slot is typically associated with fast-paced gameplay and simple mechanics that don’t require a long learning curve. Many players enjoy this type of game because it’s easy to jump in and play without preparation. Still, the key factor is how reliable the platform is—especially when it comes to payments and support—so always approach new sites carefully.
Comment by jafey —
comment 3
One of the clearest signs of a trustworthy platform is transparency in payments and rules. When I checked Fezbet Casino, I made sure to review withdrawal conditions and processing times, and everything seemed straightforward. That’s always reassuring. In Canada, players commonly advise avoiding platforms that hide important details, since openness usually reflects overall reliability.
Comment by jafey —
IT company
You’re right, full-cycle development is often used as a broad marketing term. It can mean anything from basic project management to truly handling complex product lifecycles. The key is to ask very specific questions: how they manage each stage, what tools they use, and how they measure success. I came across a company where the general info on https://sharkscode.com/ sounded promising, but the real value was in detailed discussions about their workflows and team structure. So yes, be cautious but not overly skeptical — just dig deeper.
Comment by jafey —
comment 2
Creative people often fall into emotional burnout and depression can not do anything about it, which is why it is worth understanding that you need to rest in time. The only thing I can advise is to look at Slot Machines Based on Comics Marvel and DC, there you can find unique slots with a very interesting storyline from famous companies Marvel and DC, unique games for the United States.
Comment by veltavekna —
comment 1
Interesting article on the work, but I personally think that the most difficult to do it now, when it is just summer, it is better to relax and play something
Comment by kafyurugne —
More obscure paths

Some things to add:

  • On MacOS 9 the path component separator was :. Falsehood: The path component separator is always / or .

  • You should add a list of all the reserved characters on Windows, as well as the COM*, etc. already listed. From https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx#:

    < (less than)
    > (greater than)
    (colon) " (double quote) / (forward slash) \ (backslash) | (vertical bar or pipe) ? (question mark)
    • (asterisk)

  • Falsehood: Windows UNC paths \FOO refer to a network server. Counterpoint: \.\COM1.

  • Falsehood: Absolute Windows paths always begin with DRIVELETTER:. Counterpoint: \?\C:\Foo. This is the long path support, the \?\ prefix is used to indicate the application can support long paths.
  • Falsehood: Windows UNC paths begin with \SERVERNAME. Counterpoint: \?\UNC\SERVERNAME. \?\UNC\ is the long path UNC prefix.
  • Falsehood: A subdirectory of a directory is on the same physical storage on Windows. Counterpoint: Drives can be mounted at arbitrary directories, not just at drive letters.
  • Falsehood: Barring symlinks and hardlinks, a file has only one path which can access it. Counterpoint: File paths can contain redundancies like /./, leading to an arbitrary number of strings accessing the same file.
  • Falsehood: Barring symlinks and hardlinks and with paths normalised to remove redundancies, a file has only one path which can access it. Counterpoint: The same filesystem can appear at different mountpoints on *nix using bind mounts. On Windows, junctions can be used, which function similarly to directory symlinks, but which are not symlinks and which are substantially more transparent.
  • Falsehood: If a Windows path has a drive letter, it must be an absolute path. Counterpoint: C:foo.txt (or C:bar\foo.txt or C:..\bar\foo.txt) is relative to the current working directory which was last set for C:, which may be different to the current working directory for the current drive letter.
  • Falsehood: Barring symlinks or hardlinks, a file has only one name. Counterpoint: Short names on Windows. C:\LongFilename.txt is reduced to C:\LongFi~1.txt for legacy access.
  • Falsehood: A short name will always end in ~1.EXT. Counterpoint: If C:\LongFilenameX.txt and C:\LongFilenameY.txt both exist, one will be C:\LongFi~1.txt and one will be C:\LongFi~2.txt. Which is which is indeterminate.
  • Falsehood: Opening a path successfully means you've opened a file. Counterpoint: Directories (and sockets, and so on) can be opened on *nix. On Windows, alternate file streams are addressed with the colon, which are subcomponents of files.
  • Falsehood: A file only has one stream of data associated with it. Counterpoint: Windows has alternate file streams. MacOS has resource forks.
  • Falsehood: A filesystem supports filenames longer than 8+3 characters. Counterpoint: DOS is limited to 8 characters before the file extension and 3 after.
  • Falsehood: If you write to a file with provided normalised path X and then delete normalised path Y, where Y != X, X will still exist. Counterpoint: On Windows, if X is an alternate file stream path (C:\Foo.txt:sub1), and Y is the file path (C:\Foo.txt), deleting Y will delete X. Also if Y != X is a case sensitive comparison and the filesystem is case insensitive.
  • Falsehood: The types of objects which can appear on a filesystem is limited to files and directories. Counterpoint: Windows has files (including hardlinks), directories, symlinks, junctions. *nix has files (including hardlinks), directories, symlinks, sockets, FIFOs, character devices, block devices. Some *nixes may have other object types, like Solaris doors.
  • Falsehood: A platform provides or doesn't provide mandatory locking. Counterpoint: Windows does and it is used by default. Linux doesn't provide mandatory file locking.
  • Falsehood: A filesystem mounted on *nix is always case sensitive. Counterpoint: Linux can mount FAT32, NTFS, etc.
  • Falsehood: A filesystem mounted on Windows is always case insensitive. Counterpoint: Windows can be configured to make its filesystems case sensitive.
  • Falsehood: The separators between multiple directory components are the same as that used to separate the directory components and the filename. Counterpoint: OpenVMS paths look like this: SYS$SYSDEVICE:[DIR1.DIR2.DIR3]FILENAME.EXT;FILEVER.

Feel free to use the above.

Comment by hlandau —
I don't use Windows
I wouldn't modify these tips for Windows, since I don't ever use Windows, and haven't ever used Windows for professional software development. I am completely ignorant of how anything works in Windows. Sorry.
Comment by liw.fi —
for a windows user
How would you modify these tips for someone using Git on Windows? You make several mentions of Debian here. Thanks much!
Comment by dave —
screen -D -m $SOMETHING

Your example starts screen with a script containing screen -t irssi irssi.

This script is not really a config file like the ones you would use via screen's -c configfilename option.

script's "real" config files can contain commands which would be not recognised by your way of doing it.

Your way is starting screen -t ... in an already running outer screen what makes the inner screen recognise running in screen and therefore delegating its commands to the outer screen.

Comment by yeti —