For local development you could also use Nginx with PHP as an replacement for XAMPP.
c:\nginxc:/nginx/config/nginx.conf and replace the server { ... } section with this configuration:
| // Copyright (c) 2015-2021, bacondither | |
| // All rights reserved. | |
| // | |
| // Redistribution and use in source and binary forms, with or without | |
| // modification, are permitted provided that the following conditions | |
| // are met: | |
| // 1. Redistributions of source code must retain the above copyright | |
| // notice, this list of conditions and the following disclaimer | |
| // in this position and unchanged. | |
| // 2. Redistributions in binary form must reproduce the above copyright |
| #!/bin/bash | |
| # Assigns a keyboard shortcut to the Export Unmodified Originals | |
| # menu command in Photos.app on macOS. | |
| # @ = Command | |
| # ^ = Control | |
| # ~ = Option | |
| # $ = Shift | |
| shortcut='@~^e' |
| 1 | fonts.googleapis.com | 10 | |
|---|---|---|---|
| 2 | facebook.com | 10 | |
| 3 | twitter.com | 10 | |
| 4 | google.com | 10 | |
| 5 | youtube.com | 10 | |
| 6 | s.w.org | 10 | |
| 7 | instagram.com | 10 | |
| 8 | googletagmanager.com | 10 | |
| 9 | linkedin.com | 10 | |
| 10 | ajax.googleapis.com | 10 |
*update: TBC, but this new might affect how easy it is to use this technique past August 2024: Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August
This gist, based in part on a gist by Brian Hartvigsen, allows you to export from Authy your TOTP tokens you have stored there.
Those can be "standard" 6-digits / 30 secs tokens, or Authy's own version, the 7-digits / 10 secs tokens.
Normally you would use Visual Studio 2019 with UE4, but VS 2019 is somewhat "heavy",
where Visual Studio Code is a decent alternative. However some fixes are needed before you can use it.
First, you need to change Editor to VS Code in Unreal Engine Setting,
after that you press generate VS Code project in UE4 menu.
| Framework (starter video) | Internal & External Factors Analysis | Competitive Environment Analysis | Product/Market Growth Strategy | Performance Measurement | Decision Path Analysis | Financial Evaluation | Risk Identification & Management | Organizational Alignment |
|---|---|---|---|---|---|---|---|---|
| SWOT Analysis | ✔ | |||||||
| PESTLE Analysis | ✔ |
This is a compiled list of falsehoods programmers tend to believe about working with time.
Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.
Apologies for the snarky title, but there has been a huge amount of discussion around so called "Prompt Engineering" these past few months on all kinds of platforms. Much of it is coming from individuals who are peddling around an awful lot of "Prompting" and very little "Engineering".
Most of these discussions are little more than users finding that writing more creative and complicated prompts can help them solve a task that a more simple prompt was unable to help with. I claim this is not Prompt Engineering. This is not to say that crafting good prompts is not a difficult task, but it does not involve doing any kind of sophisticated modifications to general "template" of a prompt.
Others, who I think do deserve to call themselves "Prompt Engineers" (and an awful lot more than that), have been writing about and utilizing the rich new eco-system