This is a deeper discussion on the concept of intelligence, and what can we infer from it. And this leads to what we can define as artificial from the concept of intelligence that we have. Maybe this is something that you may want to read about it, I hope you enjoy the read.
Hey 👋 DSCI author here. If someone love to check out dsci please let me know. It’s in beta stage, but some essential features are here. Extremely fast and lightweight git server and cicd. Fast ci engine on Rakupp. Ability to port existing remote git repos . CI SDK supports many languages including Python, Ruby, Raku. CI jobs run on podman / docker or localhost . Authentication for git push over https. The memory and CPU footprint is comparable to forgejo. You don’t need to install extra ci runner as the one comes included . Thus is extremely simple install. Minimal operations efforts. Suites the best to small dev teams hosting things on single VPS. Works in any Linux / Mac box. Hardware requirements - 4-8 GB RAM, 50 GB hard drive. No extra dependencies like pgsql , redis etc. Backend and front end written on golang . CI engine is on Raku, but runs on Rakupp - efficient Raku implementation that gives one a minimal start up time, speed and small cpu/memory consumption - check yourself. Everything is installed as binaries …
“Workslop” is when your colleagues or bosses communicate with you by pasting big chunks of AI-generated text. The core problem with workslop is that the effort involved is asymmetrical, like a denial-of-service attack: it takes almost no effort to produce text with AI, but it still costs effort to read.
D.eSystem 6.1.1 fixed some bugs from D.eSystem 6.1.0 and it removed the Legacy BIOS fallback because future features will require the UEFI firmware.
D.eSystem 6.1.1: https://github.com/D-electronics-scratch/all_D.eSystem_versions/releases/tag/v.6.1.1
Say I make a game that uses SDL for graphics and compile a linux version of it. Instead of going through the hassle of using Android SDK/NDK to make it a proper installable apk, would it be viable to have it be run as a program off termux?
Ka-Ping constructs a model voting machine, and decides to see how hard it would be to verify that we know it behaves correctly. To push that exploration to its furthest, Ka-Ping Yee and David Wagner try an interesting experiment:
Since yesterday a lot of users in Europe found their workflows failing due to Github seemingly randomly throwing HTTP/401 on git clone/git pull when interacting with public repos without authentication.
Everyone I’ve worked with agrees that naming matters. Almost nobody spends any time on it. The name gets picked while the code is half written and then it sticks, because renaming feels like fuss once the thing works.
I think it’s more useful to look at the tasks models haven’t gotten better at over time, and the tasks that are hard for them get better at in principle. The two best examples of these are:
Started with Laravel 4. Back then it was a lightweight framework — routes, Eloquent, Blade, done. Now the box ships with queues, broadcasting, events, policies, gates, notifications, API resources, Sanctum, Pennant, Folio, Volt, Prompts, Reverb, Pulse… The list grows every year.
I am curently developing a file system for my OS (D.eSystem) with the version 6.1.0.5. The file system is now not working,but it is in development, you can find D.eSystem 6.1.0.5 here: https://github.com/D-electronics-scratch/all_D.eSystem_versions/releases/tag/v.6.1.0.5
Recently I gave my first ever presentation at iO. It was about what it actually feels like to be a junior developer in a world where AI is just always there. This is a write-up of that talk, including what the room said back.
If you routinely “get heated” at work, the best-case scenario is that you’re part of a tight-knit team of confident people who aren’t put off by it. No harm, no foul. But the second someone comes onto your team who’s not so confident, or you have to communicate outside of your team, it becomes a big problem. It’s a bad way to treat your colleagues — even undirected or casual anger intimidates and alienates the people around you — and it makes you a less effective engineer.
Been running a screenshot pipeline for visual regression testing and hit something annoying — the same page renders slightly differently depending on the host OS. CentOS 7 vs Ubuntu 22.04 vs Alpine in Docker all produce different pixel outputs for identical URLs with identical Chrome versions.
Key takeaway: High-throughput organizations are highly sensitive to long cycle times, potentially indicating that bottlenecks like review wait times are particularly acute for these orgs. For lower-throughput teams, there is no meaningful relationship between cycle time and throughput, suggesting bottlenecks exist elsewhere.
Say I have a system that I want to enable or disable, what do you think is best: to write two separate functions EnableSystem() and DisableSystem() OR have a singular function with the parameter to indicate the desired state, SystemState(bool state)?
The last three months have not looked good for Bun. It started as one of the most impressive individual engineering projects I have seen, but has now turned into this weird AI-powered creature with continuous false promises and an increasingly frustrated community.
You can ignore it, tie it to unrelated company initiatives, or feign ignorance and simply not offer solutions that add to it. Or… you can adopt more above-board techniques such as Crawl/Walk/Run and the Reverse Farmer’s Rule, which reframe projects so that confronting tech debt is an upfront part of the plan.
PeachPie 🍑
yuurei
codeinabox
Kissaki
mattwebb.dev
CodyIT
Raffaella Papaccioli
D_elec_dev
I Cast Fist
ruffsl
EuAndreh
orhtej2
Pudutr0n
bruh
sanitation
inari
