@ GoCon 2019 Spring https://github.com/juntaki/techbook-qrcode https://www.m3tech.blog/entry/m3techbook-01/qrcode
APIã¨APIãçµã¿åããã¦ããã·ã¥ã¢ãããµã¼ãã¹ãä½ããã¨æã£ãå ´åãã¾ãèªåã欲ãããã¼ã¿ãæä¾ãã¦ããAPIãæ¢ãå¿ è¦ãããã¾ããä»åã¯ãããªAPIã®ãã£ã¬ã¯ããªãæä¾ãã¦ãããµã¼ãã¹ãã¾ã¨ãã¦ç´¹ä»ãã¾ãã PublicAPIs å·çæç¹ã§5,330ã®APIããæ¤ç´¢ãã§ããAPIã¤ã³ããã¯ã¹ãµã¼ãã¹ã«ãªã£ã¦ãã¾ããååãAPIåãªã©ãå ¥ãããã¨ã§ãæ°ããAPIã®ç»é²ç³è«ãã§ããããã«ãªã£ã¦ãã¾ãã PublicAPIs | Directory of public APIs for web and mobile API For That æ¤ç´¢ãã½ã¼ã·ã£ã«ããã¡ã¤ãã³ã¹ãªã©ç´20ã®ã«ãã´ãªã«åããã¦ç»é²ããã¦ãã¾ããç´300種é¡ãããã®APIãç»é²ããã¦ãã¾ãã API For That | An API Directory Zapier IFTTTã®ãã¸ãã¹çã¨è¨ã£ãé°å²æ°ã®ãµã¼ãã¹ã«
APIs are everywhere today and can be a great building block of modern applications. But all too often APIs are not truly great. Rather than love your API, developers curse it. How can you avoid that fate? In this session we'll look at the most common mistakes API providers make and you can avoid making them too. Do you offer a bad developer experience (DX)? Poor, inconsistent API design? Unreliabl
æ°æ¥ãçµéããåèµ·åããå¿ è¦ãçºçããã®ã§SDK+DDKãå ¥ãã¦ã¿ãã ä¾ã®ãWindowsNTã»2000ãã¤ãã£ãAPIãªãã¡ã¬ã³ã¹ãã®æ¥æ¬èªå ¬å¼ãµã¤ãï¼ãããã¦ã³ãã¼ããã ã½ã¼ã¹ã³ã¼ãã®ç°¡åãªãã¤ãã³ã³ãã¤ã«ãã¦ã¿ããã³ã³ãã¤ã«ã§ããªãã大éã«ã¨ã©ã¼ã¡ãã»ã¼ã¸ãåºããorz SDKãDDKãã³ã³ãã¤ã©ã®ãã¼ã¸ã§ã³ï¼ã¡ãªã¿ã«VC6ï¼ãåããªãã®ãã¨ããããæ¢ãã¦ããããªãã¦ãã¨ã¯ç¡ãã ã³ã³ãã¤ã«ã§ããªãã®ã¯åéããåºã¦ããã¨ã©ã¼ã¡ãã»ã¼ã¸ã C:\NTDDK\INC\ntdef.h(80) : ï¾ï¾ C6311: C:\NTDDK\INC\winnt.h(50) : 'MAX_NATURAL_ALIGNMENT' ã®åã®å®ç¾©ã確èªãã¦ãã ãã C:\NTDDK\INC\ntdef.h(100) : ï¾ï¾ C6311: C:\NTDDK\INC\winnt.h(70) : 'PROBE
ã©ã³ãã³ã°
ã©ã³ãã³ã°
ã©ã³ãã³ã°
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}