s-kocher

HTML / CSS / JS / OUTPUT
https://codepen.io/
https://jsfiddle.net/
https://liveweave.com/
https://code.sololearn.com
https://jsbin.com

IDE :
https://codesandbox.io
https://repl.it/repls

s-kocher

timber/timber#2103

In code examples, I’ve advocated for using spaces instead of tabs because of inconsistencies that came up when viewing code examples in Markdown files in readme files on GitHub (#1955 (comment) or #1890 (comment)). The downside was that when copying code into your project, you’d have to change it to tabs again.

Recently, I stumbled over an interesting thread about this topic on Reddit: Nobody talks about the real reason to use Tabs over Spaces. The main point is that we should use tabs for accessibility reasons. The are different preferences for the indent size, especially for developer with visual impairment.

In this issue, I want to explore the best option to go forward. Apparently, when you [define the in

s-kocher

Kata :

• https://codingdojo.org/kata/
• https://kata-log.rocks/
• https://gitlab.ippon.fr/twitch/live-coding-fr
• https://github.com/SoftwareCraftsmanshipGrenoble/dojos-au-top
• https://www.programmingwithwolfgang.com/tdd-kata/

Challenge :

• https://www.codingame.com/
• https://www.codewars.com/

s-kocher

IntelliJ settings :

• Version Control > Git > Enable staging area => CHECKED (Available since IntelliJ IDEA 2020.3 released 2020-12-01, long awaited feature since 2010-12 : IDEA-63391, still not the default behavior...)
  /!\ Agressive timeout probably in IDEA caused bad behaviors (staging diff editor compare against nothing) when git is slowed down, for example by an aggressive antivirus like described here with SEP, no problem with the historic git commit of IDEA not using git staging area
• Editor > Code Editing - Quick Documentation - Show quick documentation on hover => CHECKED
• Editor > Code Editing - Editor Tooltips - Tooltip delay => 200ms
• Editor > General > Code Completion - Show the documentation popup => CHECKED + `50m

s-kocher

import org.springframework.beans.BeansException;
import org.springframework.beans.factory.config.BeanPostProcessor;
import org.springframework.boot.autoconfigure.mongo.MongoClientSettingsBuilderCustomizer;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.data.mongodb.core.convert.MappingMongoConverter;


@Configuration(proxyBeanMethods = false)
class MongoConfig {

s-kocher

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>group.dummy-id</groupId>
    <artifactId>artifact-dummy-id</artifactId>
    <version>1.0.0-SNAPSHOT</version>

s-kocher

@echo off
SET SEVEN_ZIP_BIN=C:\Program Files\7-Zip\7z.exe
SET ARCHIVE_TYPE=7z
SET COMPRESSION_LEVEL=5

SET CHOME_VERSION=108.0.5359.125
SET DATE_STR=2022-11-29
SET EXCLUSION_PARAMS=-xr!Cache -xr!"Code Cache" -xr!GPUCache -xr!optimization_guide_hint_cache_store -xr!CacheStorage -xr!ScriptCache
SET CHROME_PROFILE_PATH=C:\Users\Sylvain\Chromium User Data
SET ARCHIVE_TARGET_FOLDERPATH=C:\Users\Sylvain

s-kocher

%PUTTY_HOME%\putty.exe -t -m "%TEMP%\putty.txt" !`cmd.exe /c echo cd '!/' ; /bin/bash -login > "%TEMP%\putty.txt"`

s-kocher

kata-MowItNow

La société MowItNow a décidé de développer une tondeuse à gazon automatique, destinée aux surfaces rectangulaires.

La tondeuse peut être programmée pour parcourir l'intégralité de la surface. La position de la tondeuse est représentée par une combinaison de coordonnées (x,y) et d'une lettre indiquant l'orientation selon la notation cardinale anglaise (N,E,W,S). La pelouse est divisée en grille pour simplifier la navigation.

Par exemple, la position de la tondeuse peut être « 0, 0, N », ce qui signifie qu'elle se situe dans le coin inférieur gauche de la pelouse, et orientée vers le Nord.